Migrating SVC with static target allocation to SVCDTA (dynamic target allocation)

Edit online

Change an existing configuration of IBM® Storage Protect Snapshot for UNIX™ and Linux™ to use SVC dynamic target allocation (DTA) without losing older backups. Change the value of COPYSERVICES_HARDWARE_TYPE: SVC to SVCDTA to update the profile and complete the migration.

About this task

Use the following information to modify an existing IBM Storage Protect Snapshot profile and reconfigure the product to SVCDTA.

Procedure

Log on as the database instance owner from the production database instance on the production server. From the instance directory, start the Configuration Wizard by running this command.

./setup_ora.sh
Choose Manage protected databases and modify the profile by changing the value of COPYSERVICES_HARDWARE_TYPE from SVC to SVCDTA.

Tip: Pressing Ctrl+A displays additional parameters in advanced mode.
If MAX_VERSIONS is set to ADAPTIVE, you must return to the CLIENT section, and change the MAX_VERSIONS parameter from ADAPTIVE to a fixed number.
Enter the existing server information for the storage system host name COPYSERVICES_SERVERNAME<TCP/IP host name>.
Enter the user name for the primary storage device COPYSERVICES_USERNAME.
The default value is superuser.
Enter the path and the file name of the private SSH key file in parameter SVC_SSHKEY_FULLPATH.
For example,
```
SVC_SSHKEY_FULLPATH    $HOME/.ssh/svc_sshkey
```
Accept the defaults for the remaining parameters, or change the values where required.

Note: Do not change the FlashCopy® type.

Results

The updated profile is saved, and if required you can specify a backup system or quit the configuration.IBM Storage Protect Snapshot for UNIX and Linux is configured to use the SAN Volume Controller storage adapter with dynamic target allocation.

After reconfiguring the profile for SVCDTA, all backups are managed by the new dynamic target allocation adapter, including all backups that were taken with the CIM adapter. Continue to mount, restore, delete, and expire backups as usual. When FLASHCOPY_TYPE is set to INCR, you can also refresh backups as required.