HP 10400 Application Software Suite for Microsoft SQL Media LTU Installation and Deinstallation

Page 15

3 Installation and Deinstallation

Upgrading to Recovery Manager 4.2.0 for SQL

You can upgrade to HP 3PAR Recovery Manager 4.2.0 Software for Microsoft SQL Server from Recovery Manager 3.0.2 for SQL or Recovery Manager 4.1.0 for SQL.

Upgrading the Production Server

1.Deinstall 3PAR Recovery Manager for SQL. For more information, see “Deinstalling Recovery Manager” (page 18).

2.Install HP 3PAR Recovery Manager 4.2.0 for SQL. For more information, see “Installing Recovery Manager” (page 16).

Upgrading the Backup Server

The upgrade steps for the Recovery Manager backup server also apply to the Remote Copy backup server(s), if applicable to your setup.

1.If you plan to use a different installation folder for the new version of Recovery Manager for SQL and not the same folder as the previous version, make a copy of the repository. The repository is located in:

•Recovery Manager 4.1.0 for SQL: <Install Directory>\RM\SQL\Data

•Recovery Manager 3.0.2 for SQL: <Install Directory>\VCDBA\SQL\Data

If you plan to use the same installation folder for the new version as the folder that was used for the previous version, skip this step.

2.Deinstall the previous version of 3PAR Recovery Manager for SQL. For more information, see “Deinstalling Recovery Manager” (page 18).

3.Install HP 3PAR Recovery Manager 4.2.0 for SQL. For more information, see “Installing Recovery Manager” (page 16).

4.If you used a different installation folder for Recovery Manager 4.2.0 for SQL, copy the repository data from the previous version of Recovery Manager for SQL to:

<Install Directory>\RM\SQL\Data

If you used the same installation folder for both the new and previous version, skip this step. Recovery Manager for SQL automatically imports all the repository data.

Verifying the Upgrade

1.Verify that Recovery Manager for SQL is listed as a service that is currently running.

2.Check whether you can see the previously created virtual copies in the GUI. Re-register the SQL servers if necessary.

3.If you used the Recovery Manager Backup or All of above option to install Recovery Manager, verify that the 3PAR Recovery Manager for SQL Server icon appears on the desktop.

4.Verify the registry key. For more information, see “Understanding the Registry” (page 17).

Pre-Installation Steps

Before installing HP 3PAR Recovery Manager Software, install the following:

•HP 3PAR InForm OS Command Line Interface (CLI) for remote clients. For more information, see the HP 3PAR InForm OS CLI Administrator’s Manual.

•HP 3PAR VSS Provider Software for Microsoft Windows. For more information, see the HP 3PAR VSS Provider User's Guide.

Upgrading to Recovery Manager 4.2.0 for SQL 15

Image 15
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 ManagerIntroduction Related DocumentsTypographical 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 Installation and Deinstallation Upgrading to Recovery Manager 4.2.0 for SQLPre-Installation Steps Installing Recovery Manager Understanding the Registry Verifying the InstallationDeinstalling Recovery Manager Configuring Recovery Manager Configuring the SQL DatabaseConfiguring Recovery Manager Configuring Recovery Manager Policies Configuring Mount FunctionalityGrouping 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 Setting the Recovery Manager Policy How Recovery Manager Policies WorkUnregistering 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 CopyManually Creating Backups at the Instance or Database Level Unmounting a Virtual CopyBacking Up a Virtual Copy Scheduling Automatic Backups of an Instance or Database Removing a Backup from the Repository Restoring Instances, Databases, and VolumesCreating 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 CopyUsing the Recovery Manager CLI Recovery Manager for SQL Server Command Line Interface 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 RMSql policy Database virtual copy limitInstance virtual copy limit Retain timehHdD RMSql policy -n 5 -s SQL serverRMSql 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 RMSql repository -a alter location -rRMSql repository -a d\3parvv RMSql restore SystemDrive\3parSnapshot by defaultAltLocation 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