HP 7450 Application Software Suite Microsoft SQL Media LTU manual Configuring Recovery Manager

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

Image 19

Contents User’s Guide Documentation Contents Using the Recovery Manager GUI Configuring Backup SoftwareTroubleshooting Event Messages Using the Recovery Manager CLIRecovery for Microsoft SQL Server Remote Copy for Recovery ManagerRelated Documents IntroductionTypographical Conventions Advisories Additional System Requirements Overview of Recovery ManagerSystem Requirements Windows Server RequirementsRunning Recovery Manager on a Japanese OS Recovery Manager RequirementsFeatures Supported Microsoft Volume Shadow Copy Service Features Not SupportedHow HP 3PAR VSS Software Works with Microsoft SQL Server Supported VSS ComponentsRecovery Manager Layout Overview of Recovery Manager Upgrading to Recovery Manager 4.2.0 for SQL Installation and DeinstallationPre-Installation Steps Installing Recovery Manager Understanding the Registry Verifying the InstallationDeinstalling Recovery Manager Configuring the SQL Database Configuring Recovery ManagerConfiguring Recovery Manager Configuring Mount Functionality Configuring Recovery Manager PoliciesGrouping Volumes into Autonomic Groups Volume Sets Testing SQL ConnectivityTroubleshooting SQL Connectivity Configuring the Host Computer and the HP 3PAR Storage SystemWindows Server Formatting Partitions on a New HP 3PAR VlunBefore You Begin Configuring Backup SoftwareSetting Up Symantec NetBackup OverviewRequirements Configuring HP Data ProtectorSetting Up the HP Data Protector Backup Specification Setting Up HP Data Protector Cell Manager AccessRM installation location\log\nbulog\databasetimestamp.log Using Your Backup SoftwareUsing Symantec NetBackup Using HP Data ProtectorClosing the Recovery Manager GUI Using the Recovery Manager GUIOverview of the Recovery Manager GUI Opening the Recovery Manager GUIUpdating Registration after Server Modification How Recovery Manager Policies Work Setting the Recovery Manager PolicyUnregistering a SQL Server Instance Retention Time Restrictions Setting Recovery Manager PoliciesModifying the Policy for a Virtual Copy Configuring Email NotificationsManually Creating a Virtual Copy Deleting Email ConfigurationsCreating Virtual Copies How Virtual Copy Creation WorksScheduling Automatic Virtual Copies Creating Remote Virtual CopiesScheduling Automated Tasks with Task Scheduler Automating TasksManaging Automated Tasks with Task Manager Mounting a Virtual CopyUnmounting a Virtual Copy Manually Creating Backups at the Instance or Database LevelBacking Up a Virtual Copy Scheduling Automatic Backups of an Instance or Database Restoring Instances, Databases, and Volumes Removing a Backup from the RepositoryCreating a Backup of a Virtual Copy Restoring an Instance or Database with File Copy Restore Restoring an Instance or Database with Volume RestoreAnalyzing and Synchronizing the Repository Restoring an Instance or Database from a BackupViewing Event Message Descriptions Removing a Virtual CopyRecovery Manager for SQL Server Command Line Interface CLI Using the Recovery Manager CLIRecovery Manager Commands Sync RMSql analyzeRMSql analyze -s SQL server -sync -f SQL ServerRMSql backup Example RMSql create RMSql create -s SQLVirtualServer -d test RMSql create -s SQLServer -d testUsing the Recovery Manager CLI RMSql deletebackup -s server1 -d db1 -t RMSql deletebackupRMSql display -s server1 RMSql displayRMSql listbackup RMSql mount Database virtual copy limit RMSql policyInstance virtual copy limit RMSql policy -n 5 -s SQL server Retain timehHdDRMSql policy -exp 30d -s SQL server Recovery Manager Commands RMSql portconfig -n 9999 -s WindowsHost RMSql portconfigRMSql portconfig -n number -s WindowsHost RMSql portconfig -nRMSql remove -s SQL server -t timestamp RMSql removeRMSql report -s Grampus -output c\MyReport RMSql reportRMSql report -s WindowsHost -output OutputDirectory WindowsHostRMSql repository -a alter location -r RMSql repositoryRMSql repository -a d\3parvv SystemDrive\3parSnapshot by default RMSql restoreAltLocation Snap NorecoveryRMSql restore -s server1 -d testdb -t RMSql restore -snap -s server1 -d testdb -tUsing the Recovery Manager CLI RMSql setvc RMSql setvc -s server1 -t 020409162103 -exp 30d RMSql setvc -s server1 -t 020409162103 -exp 2hRMSql timeconfig -bkt RMSql timeconfigRMSql timeconfig RMSql timeconfig -prtRMSql unmount -s SQL server -t timestamp Running Recovery Manager as a Scheduled JobScheduling an Automated Task in Windows RMSql unmountFor example Preparing for the Recovery Process Recovery for Microsoft SQL ServerMicrosoft SQL Server Recovery Models Recovering Data with HP 3PAR Recovery ManagerRecovering All Data with Point-of-Failure Recovery Performing a Point-of-Failure Recovery Recovering All Data with Point-of-Failure Recovery How Remote Copy Works Remote Copy for Recovery ManagerSetting Up Remote Copy Support for GeoCluster for Microsoft Windows Setting Up Remote Copy Volume GroupsSetting Up a Remote Copy Volume Group for Databases Support for Remote Copy Modes and PoliciesSetting Up a Remote Copy Volume Group for Instances Recovering a SQL Database from a Remote Copy Backup ServerVMWare and Egenera Server Virtualization EnvironmentsTroubleshooting Installpath\NetBackup\db\altnames\No.Restrictions Installpath\NetBackup\db\Event Messages Event ID Event ID Event ID Event ID Provcfg conn -syncrc Yes