Importing IBM Spectrum Protect Data

Using the Data Import app, you can migrate filesystem and VMware backup jobs to Commvault. The backup jobs are restored as files from an IBM Spectrum Protect client and staged on a data access node to initiate backups to Commvault storage.

Procedure

1. Import the Data Import app to the Command Center. For more information, see Importing an App.

2. From the navigation pane, go to Protect > Data Import.

3. In the Server Configuration tab, under Data Access Nodes section, click Add/Update.

   The ThirdPartyMigration_EditStagingClient_FS window appears.

4. In the Operation Type list, select Add to add a new data access node, and then click OK.
   To edit an existing data access node, select the data access node name, and then click OK.
   The Data Access Node window appears.

5. In the Client list, select the data access node name.

6. In the Restore Path box, type the location where you want to restore the IBM Spectrum Protect data on the data access node.

   To restore VM data, type the NFS mount path that you created for datastore export. Example, /cvstorage.

7. In the Third Party Install Path box, type the base path for IBM Spectrum Protect installation. Example, C:\Program Files\Tivoli\TSM.

8. Click OK.
   The data access node is listed under the Data Access Nodes section.

9. In the Server Configuration tab, under Backup Server Configuration section, click Add Server.

   The Select Backup Product window appears.

10. In the Select Product box, select TSM, and then click Next.

    The Enter Migration Settings window appears.

11. Provide the following inputs, and then click Next.

    • Unique Alias Name - The unique alias name of the TSM backup server.

    • TSM Server - The name of the TSM backup server.

    • TSM User - The admin user account for the TSM backup server. (This does not apply if you do not have administrative access to the IBM Spectrum Protect backup server.)

    • TSM User Password - Password for the admin user account. (This does not apply if you do not have administrative access to the IBM Spectrum Protect backup server.)

    • Select TSM Command Client - The name of the server where you run the TSM admin commands (dsmadmc). (This does not apply if you do not have administrative access to the IBM Spectrum Protect backup server.)

    • TSM Install Path on Command Server - The path where you installed the TSM software on the Command Server. For example, C:\Program Files\Tivoli\TSM. (This does not apply if you do not have administrative access to the IBM Spectrum Protect backup server.)

    • Migration WorkSpace on WorkFlowEngine (Commserve, where the WorkflowEngine package is installed) - This is disabled as workflow will identify the exact path of the JobResults directory on the CommServe. Under this directory, Workflow creates the TSMMigrationWorkSpace directory. This directory stores the TSM restore file list (.txt file) which is passed as -filelist to the dsmc restore command, the TSM client sqliteDB files (.db-shm, .db-wal and .db files) and tsmclient_contents.csv file.. This folder stores the TSM restore file list (.txt file), which is passed to the dsmc restore command and the TSM client sqliteDB files (.db-shm, .db-wal and .db files/tsmclient_contents.csv).

    • Data Access Node - Name of the Data Access Nodes that you configured. Only the configured Data Access Nodes are listed in the Enter Migration Settings page.

    • Backup Plan – Name of the backup plan that you configured for the data import operation.

    • Number of Versions to Restore - Select the number of versions to restore. For example, if you select the number of versions as 2, only the two TSM file versions will be restored. If you enter "*", then all the TSM file versions are restored.

    • Max Parallel Jobs - Select the maximum number of backup jobs that you can run in parallel and then click Finish.

    • Collect Clients and Policy Details - Enable to collect the TSM server details. This is required when you add the TSM server for the first time. (This does not apply if you do not have administrative access to the IBM Spectrum Protect backup server.)

    • VM Migration - Toggle to enter configurations required for VM data import.

    • ESX NFS Datastore - Applies to VM data import only. Name of the NFS datastore that you created. Example: cvstorage.

    • vCenter Migration Datacenter - Applies to VM data import only. Name of the datacenter that you created in vCenter. The datacenter name is required to perform out-of-place recovery operations.

    The TSM backup server is listed under Backup Server Configuration.

12. Click Load Jobs for the TSM backup server.

13. In the Select client box, select one or more TSM clients for which you want to load the backup jobs, and then click OK.

14. Click the Job Details tab.

    You can view a list of backup jobs for the selected clients.

15. To change the client , in the Select Client box, select a different TSM client, and then click Apply.

16. To start data import, select the backup jobs, and then click Start Migration.

    The status column for the selected backup jobs, will display the status as In Progress. You can also view the import progress for the backup jobs in the Migration Queue tab.

17. Optional:To stop the running the data import operation, in the Migration Queue tab, click Stop.

    The Commvault file system license is released on the data access node when the import is complete.

What to Do Next

To delete any orphaned VMs created during the data import process, complete the following steps. These steps will delete all orphaned VMs and not specific to only imported VMs.

1. Verify that ssh is enabled on the ESXi host.
2. Create the delete_orphaned_vms.sh script file with the following code:

# List all VMs and their IDs..
vm_list=$(vim-cmd vmsvc/getallvms | tail -n +2 | awk  
'{print $1}')  
for vmid in $vm_list; do  
# Check if the VM is orphaned  
power_state=$(vim-cmd vmsvc/power.getstate $vmid)  
if [[ $power_state == *"Invalid"* ]]; then  
echo "Deleting orphaned VM with ID: $vmid"  
fi  
done

3. Copy the script to the ESXi host.

scp delete_orphaned_vms.sh root@esxi_host_ip:/<DataStorePath>
chmod +x /vmfs/volumes/<DataStorePath>/delete_orphaned_vms.sh

4. Run the script to delete the orphaned VMs.

Optionally, to schedule the pruning job, run crontab -e to edit the crontab file, and then add the following line:

0 0 * * * /vmfs/volumes/datastore1/delete_orphaned_vms.sh