Views:

Summary

 


This article facilitates migration to the DPX Master server virtual appliance from an old Master server deployment

 

 

 

Step By Step

 

 

 

 

In order to migrate to the new DPX Virtual Appliance Master Server, the following prerequisites must be met:

 

 

  • The new DPX Virtual Appliance Master server must be installed in your environment. The OVA appliance can be downloaded from Catalogic MySupport
  • Download the migration scripts from Catalogic MySupport migrationscripts.zip. Extract and copy them to your old master server.
  • The new Master Server must have sufficient space to hold your current catalog and DPX information in the /catalogic mount point, to expand this see article: 
  • A compression utility like 7zip or WinZip must be installed on the old Master Server before starting the migration script.
  • You need to have a temporary staging area on the new Master Server to hold the migrated catalog (this can be removed once the migration is completed).

 


Pre-migration steps:

 

  • Please note not all options set on the old Master server will be migrated; however, a copy will be made during the migration.  
  • If you are changing the DPX Master server host name, you will require a new license key for your Master server.
To request a new license please send a screenshot of the following command on  the Master server virtual appliance and send this screenshot to dplicense@catalogicsoftware.com  
$ uname -a

 

Migration Steps 

To migrate the Master Server and catalog please follow these steps:

  • Shutdown the Catalogic DPX services in the following order on the current Master Server (Windows / Linux) when no jobs are running:

           Windows:

1. Catalogic DPX Advanced Protection Manager
2. Catalogic DPX Autoupdate Master Agent
3. Catalogic DPX Controller Service
4. Catalogic DPX Web Server
5. Catalogic DPX CMAgent Service

 

           Linux:

Use the following commands to terminate these three Catalogic services in order: 

                1. Advanced Protection Manager

$ sudo /opt/DPX/misc/bexads stop
 

                2. Autoupdate Master Agent 

$ sudo /opt/DPX/misc/sscmagent stop autoupdate
 

                3. CMAgent service

$ sudo /opt/DPX/misc/sscmagent stop

 

  • Create a catalog backup directory on the current Master server where the catalog backup will be stored.
  • Create catalog backup - use the Catalogic assist script (BackupCatalog.[bat|sh]):
Windows: 
BackupCatalog.bat <DPX_install_dir> <backup_dir>

Linux:
$ sudo ./BackupCatalog.sh <DPX_install_dir> <backup_dir>

 

  • Login to the OVA console using the default credentials (dpxadmin/DPXvStor - change on first login)
  • Create upload location on Master Server:
$ sudo mkdir /catalogic/backupcatalog 
$ sudo chmod +777 /catalogic/backupcatalog
  • Upload backup archive to OVA  and the provided Catalogic restore script (RestoreCatalog.sh) using winscp to the /catalogic/backupcatalog directory. 
  • Restore the catalog backup using the Catalogic restore script:
$ cd /catalogic/backupcatalog
$ sudo chmod +x RestoreCatalog.sh
$ sudo ./RestoreCatalog.sh catalogBackup.zip

 

Post Migration steps:

Note: DPX will not allow deleting a system from the enterprise while it is a device server.  This section needs to be done before the current master can be deleted in Options 1 and 2. Preserving the device information by assigning them to a different node must be done if you are planning to continue to use the former master server as device server.  Otherwise, the devices can be removed from the DPX Enterprise.

  • Generate and save a Device Report and a Tape Library Report using the management Console Reports tab.  Note the Device ID of Disk Directory devices served by the old Master server.
  • For Disk Directory devices, delete the devices served by the old master server.  The Disk Directory Device Cluster doesn't need to be deleted.
  • For GENERIC and Tape devices use the Logical Node Name drop-down menu to select a node that isn't the master server. This is a temporary reassignment to allow the master server to be deleted.
  • For Tape Libraries use the Controller Node drop-down menu to select a node that isn't the master server.

The above steps will allow the old master server to be deleted so that the Options 1 and 2 can be completed if the old Master server was a device server. 

  • Option 1 Old Server is just a Master Server. (no Device Server or OSS Server).

    • Remove old master server (if decommissioning) in Configure | Enterprise 
    • Add new Master Server to DPX Master Virtual Appliance in Configure | Enterprise 
    • Uninstall the DPX Software from old Master server.
      • Windows from the Start Menu: All Programs | DPX | Uninstall DPX 
      • Linux <DPX_INSTALL_LOCATION>/uninstall/uninstall_DPX (default install location is in /opt/DPX)
    • Reboot the old Master Server
    • Reinstall  as a normal DPX client( with Agentless proxy support) if you want to use the old Master Server as a proxy as before.
    • Reboot 
    • Patch the old Master Server to the latest patch level if using an older installer current shipping DPX version 

  • Option 2 Old Server is a Master Server and OSS server 

    • Make sure no current Instant Availability mappings are currently active on the old Master Server
    • Remove old Master Server (if decommissioning) in Configure | Enterprise 
    • Add new Master Server to DPX Master Virtual Appliance in Configure | Enterprise 
    • Make a copy of the DPX/XRSDB directory on the old Master server installation directory to a non DPX location 
    • Uninstall the DPX Software from old Master server.
      • Windows from the Start Menu: All Programs | DPX | Uninstall DPX 
      • Linux <DPX_INSTALL_LOCATION>/uninstall/uninstall_DPX (default install location is in /opt/DPX)
    • Reboot the old Master Server
    • Reinstall as an OSS Server with Agentless proxy support if you want to use the old Master Server as an OSS server and proxy as before until the old OSS backups expire.
    • Reboot 
    • Patch the old Master Server to the latest patch level if using an older installer current shipping DPX version 
    • Copy the DPX/XRSDB directory back to the old Master , now OSS server so that any ongoing snapshot consolidation actions are not lost.

  • Option 3 Reconfigure the old Master server as a device server.

Note: If the IP address or host name are preserved on the new master server, the device server will need a new IP address or host name respectively.
  • Uninstall DPX from the old master server.
  • If the IP address or host name was preserved for the new master server, the device server will need its IP address or host name changed before the DPX reinstallation.
  • Reinstall as a normal client
  • Scan device server into enterprise 
  • If the device server is Windows, reboot
  • Patch the device server to the latest patch level
  • Re-add desired devices and tape library to the enterprise (change names preserved in former section) 
    • If Disk Directory devices were deleted in the earlier section the process, add those devices back, using the Device ID noted from the Device Report.
    • If the Logical Node Name of GENERIC or Tape devices were changed in the earlier section, change it to use the device server.
    • If the Logical Node Name of a Tape Library was changed in the earlier section, change it to use the device server
  • Recreate the new device files in the DPX directory, These steps will recreate the sync_sa configuration files, if needed.
-start a DPX Command Prompt with (Right click "Run as Administrator"
-change directory to ..\bin\JB
-run "detect -i".