> CommCell Console > Solutions and Use Cases > Import Backup Vendor Archives to Commvault > NetBackup Data Import

Importing NetBackup Data

Using the Data Import app, you can import backup jobs that can be restored as files from a NetBackup client into the Commvault storage. The app restores the NetBackup backup jobs to the Data Access Nodes (staging client) and initiates the backup for the data import operation.

Note

The Data Import app is accessible only for the Commvault professional services team. To use the app, contact your account representative and discuss a Professional Services engagement. To enable data import for supported agents, contact your sales or customer success team for assistance with purchasing the app.

The app imports third-party backups as files (file system data) from Veritas Netbackup. You can import only file system data to the Commvault storage. You cannot import data of other agents or applications such as Oracle, Microsoft SQL Server and NDMP.

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 Edit Staging Client 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 Netbackup 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 Veritas Netbackup installation. Example, /usr/openv/netbackup.

  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 NetBackup, and then click Next.

    The Enter Migration Settings window appears.

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

    • Unique Alias Name - Customized name to save the configuration in the app for the NetBackup data import operation.

    • NetBackup Master Server - NetBackup Master server hostname that is reachable to run commands to fetch client and job details from the Command Server.

    • Master Server Time Zone – The time zone of the Master server. Set the correct timezone for importing the jobs to Commvault storage.

    • Select Command Server - Name of the server that has NetBackup software and the Commvault software installed. The server will run the required NetBackup commands (including bprestore command) to get the NetBackup clients or job details and to restore the NetBackup client data into the data access node (LandingZone Server). The Command Server and the data access node can be on the same server or on separate servers. This does not apply if you do not have administrative access to the NetBackup (NBU) master server.

    • NetBackup Installation Path on Command Server - The path where you installed NetBackup on the Command Server. For example, C:/Program Files/Veritas/NetBackup on Windows server and /usr/openv/netbackup on Linux server. This does not apply if you do not have administrative access to the NetBackup (NBU) master server.

    • Data Access Node - Select the data access node that you configured. Only the configured Data Access Nodes are listed in the Enter Migration Settings page. NetBackup VMware Data is restored to the data access node through the NFS datastore.

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

    • Netbackup Workspace Path on Command Server – The path where the app creates temporary input files required for the data import. For example, /tmp/cvnbumigration. These input files are sent to the bprestore command for each backup job that you select for the data import operation.

    • Max Parallel Jobs - Select the maximum number of backup jobs that you can run in parallel. By default, the number is set to 5 for optimal usage. You can change this value based on the NBU and Commvault infrastructure load capability and scale aspects.

    • NBU ESX Server - Applies to VM data import only. The name of the ESXi server required to stage the temporary VM recovery destination.

    • 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.

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

    The NetBackup Master server is listed under Backup Server Configuration.

  12. Click Load Jobs for the NetBackup Master server. This does not apply if you do not have administrative access to the NetBackup (NBU) master server.

  13. In the Select Client box, select the NetBackup clients for which you want to view the backup jobs.

  14. In the From and To boxes, enter the start and end time range of the backup jobs that you want to view, and then click OK.

    You can view a list of backup jobs for the selected client and date range.

  15. Click the Client Details tab.

    You can view the details for the selected clients.

  16. Click the Job Details tab.

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

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

  18. To start the data import operation, 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.

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

  20. Optional: To view details of the media that was used for each backup job, click Show Media.

Note

If the NetBackup command line operations do not work during the data import, the import job will fail or moves to a pending state. To troubleshoot issues with the NetBackup command line operations, contact Veritas support.

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

×

Loading...