Professional Documents
Culture Documents
To perform the upgrade procedure, you must download and launch the Deployment Manager. First complete Upgrade RPAs Wizard Prepare for Upgrade, then complete Upgrade RPAs Wizard Apply Upgrade. Note: The procedure may take over an hour to complete, depending on the FTP server, network speed, and size of environment being upgraded.
Figure 1
3. [ ] On the Deployment Manager wizard selection screen, select option Upgrade RPAs Wizards Prepare for Upgrade (the "Deployment Manager wizard selection screen" illustration). Note: The Prepare for Upgrade wizard must be run and completed before running the Apply Upgrade wizard.
Figure 2
IMPORTANT: Ensure you have read and followed the "Prerequisites" section before continuing with the "1. Prepare for upgrade" section.
Figure 3
2. Login credentials
Enter login credentials (the "Login credentials screen" illustration):
IP credentials
Enter a site management or an RPA IP address.
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
5. System diagnostics
System diagnostics are performed for the site(s) and the RPAs. By doing so, the system attempts to validate that the current configuration is appropriate and that RecoverPoint can successfully operate in the current environment (the "System diagnostics screen" illustration). The site system diagnostics will present the following results: Level, Site, and Description. The RPA system diagnostics will present the following results: Level, RPA, Site, and Description. The system will confirm that all components are OK and that no errors or warnings exist. If errors are detected, you must correct them to be able to continue. If warnings are detected, it is recommended to fix them, if relevant, before you continue, even though the system allows you to ignore them and continue the upgrade. Once errors and warnings are resolved, click Refresh to rerun the system diagnostics process.
Figure 9
IMPORTANT: Apply upgrade now only if you have verified that you have no system modifications (only relevant to upgrades from 3.1 or 3.1 SP1), or, if you did verify the existence of a system modifications file or files, that you submitted the file or files to Customer Service and received a response about how to proceed in the upgrade. If you leave the Apply upgrade now checkbox clear and click Finish, the Upgrade RPAs Wizard will close.
If Customer Service instructed you to not import a file, or if no system modifications were found, you can continue without importing a modifications file by clearing the Modifications file checkbox. Click Yes when the No system modifications file imported window appears. To verify if you need to import a modifications file, see the "Verify and collect system modifications files" section. IMPORTANT: The system modifications file is important for the upgrade to complete successfully. Continue only if you are sure that you do not need to import a file.
Environment diagnostics
The results of the environment diagnostics test are displayed on this screen (the "Apply upgrade configuration screen" illustration). If warnings or errors are found, they will be displayed in the table. If no warnings or errors are found, Environment diagnostics completed successfully will be displayed. IMPORTANT: It is strongly recommended to resolve these warnings and error before proceeding. Failure to do so may lead to disruption in replication or production downtime during a disaster, and other possible issues during normal operation. To apply the upgrade, click Next.
Note: If the Wizard is unable to apply the upgrade to an RPA (or pair of RPAs, in the event of a two-site configuration), a Collect system information dialog box appears (the "Collect system information screen" illustration). In this screen, you should enter FTP server information, to which the system information (logs) gathered from the RPA (or RPA pair) will automatically be saved. The system information is saved to a RAR file (or two RAR files for a two-site configuration). The file name will automatically be appended with the IP address of the RPA (or RPAs) from which the system information is collected (example filename: RPA1Site1_10.10.10.10_rar). The file(s) should be submitted to Customer Service, to allow them to analyze the file(s), the content, and assist you in successfully completing the To improve Customer Service response time, it is highly recommended to collect and Deployment Manager logs (found in <Deployment Manager unzip location>/logs) to server. research upgrade. save the the FTP
Updating license
After performing a major upgrade to RecoverPoint release 3.2 or later, it is recommended to obtain a new license key (for no extra cost) from EMC for the release. Until a new license is set in the RecoverPoint environment, licensed features for the release will remain disabled.
Recovery policy
The Upgrade RPAs Wizard supports auto-recovery. Therefore, if a step fails anywhere in the procedure, running the Wizard again will automatically continue the procedure from where the step failed. Some failures (such as an RPA that goes down) may require manual intervention (such as starting up an RPA) before rerunning the Wizard.
RollBack Plan
There is no rollback plan , Vendor will escalate it to next Level and complete the upgrade .