Rmsql portconfig – HP 3PAR Recovery Manager Software for Microsoft SQL Server Licenses User Manual
Page 54
EXAMPLE
The following command sets the maximum number of virtual copies to 5 at all times for the default
SQL instance:
RMSql policy –n 5 -s <SQL server>
The following command sets the expiration time of virtual copies to 30 days for the default SQL
instance:
RMSql policy -exp 30d -s <SQL server>
NOTE:
By default, the Recovery Manager for SQL policy is set to a maximum of 10 virtual copies
each for the instance level and the database level. In addition, the option to delete the oldest virtual
copy is by default set to ‘No’; therefore, when the virtual copy limit is reached, Recovery Manager
for SQL retains the oldest virtual copy.
You can use the above example command either to expand the policy limit (by specifying a larger
value for the -n option) or to enable removal of the oldest virtual copy if the limit has already been
reached (by not using the -r option).
RMSql portconfig
SYNTAX
RMSql portconfig [-n <number>] [-s <WindowsHost>]
DESCRIPTION
After Recovery Manager for SQL is installed, by default the port used for communication between
the backup server and production server is 9932. If necessary, you can specify an alternate port.
PARAMETERS
The following options are supported:
-n <number>
Optional. The port number. If not specified, 9932 is used as the default.
-s <WindowsHost>
Optional. Name of the Windows host on which to change the port. If
not specified, the current host name is used as the default.
EXAMPLES
The following command changes the local port to 9999.
RMSql portconfig -n 9999
The following command changes the port on the specified SQL server to 9999.
RMSql portconfig -n 9999 -s <WindowsHost>
NOTE:
After you execute the portconfig command, you must restart Recovery Manager
Services.
NOTE:
If you change the port value on one server, you must update the port value for every
Recovery Manager for SQL system (including the Recovery Manager backup server) managed by
the same Recovery Manager backup server.
54
Using the Recovery Manager CLI