HP 3PAR Application Software Suite for Microsoft SQL Licenses - Manual (Page 19)

4 Configuring Recovery Manager
Configuring the SQL Database
When you configure the SQL database:
•
Be sure to use database files and transaction logs created on basic disks using the NTFS file
system.
Recovery Manger for SQL Server does not support other types of disks.
•
Maintain a 1:1 relationship between databases and volumes:
Do not add more than one database plus its transaction log files to a volume. ◦
◦ Do not add files from one database (including its transaction log files) to multiple volumes.
CAUTION: Be sure to maintain a one database:one volume relationship.
If you add multiple databases to one volume, backup and disaster recovery operations on one
database can result in conflicts between the databases in the volume.
Configuring Recovery Manager
Installation Location
By default, Recovery Manager installs in:
C:\Program Files\3PAR\RM\SQL
Search Path
After installation, you can instantly issue Recovery Manager CLI commands from any directory.
Although the Recovery Manager executables are installed in a fixed location that is specified during
installation, the location is automatically added to the Windows PATH environment variable.
Changing the Recovery Manager TCP/IP Port
By default, Recovery Manager for SQL uses port 9932 for cross-server communication. As long
as port 9932 is available, no extra port configuration is necessary.
If port 9932 is not available or is occupied by another system process, you must change the
Recovery Manager TCP/IP port.
1.
Select an available port. The valid TCP/IP port range is 1024 to 65535.
2. To set your desired port number, run the Recovery Manager CLI RMSql portconfig
command.
For example, to change the port number to 9999, use: RMSql portconfig -n 9999
CAUTION: If you are changing ports from the backup server, be sure to change the Recovery
Manager ports on the production servers first. If you change the backup server port first, you
cannot then access the production servers in order to change their ports.
3. From the Windows Service console, restart the Recovery Manager for SQL service.
4. Repeat these steps for all production servers and the backup server.
Configuring the SQL Database 19