Migrating from Catalogic DPX OSS to Catalogic vStor Server

Migrate your storage solution from Catalogic DPX Open Storage Server (OSS) to Catalogic vStor. You can use the ossvstor script in the Catalogic DPX Master Server.

Prerequisites for migrating OSS jobs to Catalogic vStor Server

Ensure that there are jobs that are associated with the Catalogic OSS storage as a backup destination in the Catalogic DPX environment.

Ensure that at least one Catalogic vStor Server is registered with Catalogic DPX for its backup destination.

Migrating from Catalogic DPX Open Storage Server (OSS) to Catalogic vStor Server

The steps in this section illustrate the oss2vstor, block.cmd, and agentless.cmd scripts as examples. Variables in your environment will differ and should be updated appropriately.

Here is an example of the oss2vstor script. In this, the variables , <Master Server IP address> , and must be updated to reflect your environment.

sep ,
   connect start,<Master Server IP address>
   db login,<username>,<password>
   job2 list,-fblock.cmd,-Rdest, , ,BACKUP_SNAPVAULT, , , , , , , , , , , , , , , , , ,onlyxrs,
   job2 list,-fagentless.cmd,-Rdest, , ,BACKUP_VIRTUALIZATION, , , , , , , , , , , , , , , , , ,onlyxrs,

  1. Log in to the Catalogic DPX Master Server shell, typically, by using an SSH client. The user name is dpxadmin and the default password is dpxadmin.

  2. Copy the oss2vstor script to the /opt/DPX/tools directory.

$ sudo cp oss2vstor /opt/DPX/tools

Remote Seeding with Catalogic DPX OSS 106

$ sudo chmod +x /opt/DPX/tools/oss2vstor

  1. Edit the oss2vstor script file so that it properly reflects the environment settings using vi. Change the variables <Master Server IP address>, <user name>, and <password> to match the environment Catalogic DPX Master Server OVA appliance IP address and the associated credentials.

$ sudo vi /opt/DPX/tools/oss2vstor

  1. Run bexenv to set up the environment.

$ sudo . ./opt/DPX/bin/bexenv

  1. Run the updated oss2vstor script from syncui in the /opt/DPX/tools directory. This will create the block.cmd and agentless.cmd files in the /opt/DPX/tools directory.

$ sudo /opt/DPX/bin/syncui < /opt/DPX/tools/oss2vstor

  1. Edit the block.cmd and agentless.cmd files to point to the target Catalogic vStor server and so that they contain the connect start and db login syncui commands from the oss2vstor script. In the example below, the red text has been updated.

sep ,
   connect start, <Master Server IP address>
   db login, <username>, <password>
   job2 repdest,hCluster-4,SS_DEFAULT,BACKUP_SNAPVAULT,hCluster-4, , BEX_ 4nodeclstr2 * NULL vstor1 vol1 ;, , , , , , , , , , , , , , ,includeall/vstor,
   job2 repdest,hEMS-5,SS_DEFAULT,BACKUP_SNAPVAULT,hEMS-5, , HARDWAREMS * NULL vstor2 vol1 ;, , , , , , , , , , , , , , ,includeall/vstor,

  1. Run syncui for block.cmd and agentless.cmd to update the job destination.

$ sudo /opt/DPX/bin/syncui < /opt/DPX/tools/block.cmd

$ sudo /opt/DPX/bin/syncui < /opt/DPX/tools/agentless.cmd

  1. Finally, perform a catalog condense job.

Ensure that all Catalogic DPX jobs that are using Catalogic OSS for the backup destination are now using Catalogic vStor.

Last updated