Importing DPM Data

Using the Data Import app, you can import backup jobs that can be restored as files from a System Center Data Protection Manager (DPM) client into the Commvault storage. The backup jobs are restored as files from the DPM client and staged on a data access node to initiate backups to Commvault storage.

The app uses DPM commands(using Powershell script) to fetch the clients, policies, and backup jobs from DPM and populates the configuration database. Then, from the Command Center, you can select the jobs that you want to import to Commvault storage. The app recovers the selected backup jobs based on parameters, such as parallel jobs and data access nodes. The recovered data is then backed up on to Commvault storage using configured backup plans and data access nodes.

The overall performance of the import depends on multiple environmental factors, like restore throughput from DPM, backup performance, attached storage, and resources. After the backup job is complete, the staging area is cleaned on data access node so that you continue importing DPM backup jobs.

Before You Begin

Review the following requirements to import DPM filesystem data to Commvault storage:

• Create a Backup plan with proper retention rules for data import. The backup plan should not be associated with any schedules.

• Configure the DPM Command Server (DPM Backup Server). Also, install the Commvault File System Agent on the DPM Command Server.

• Verify that that data access node has DPM and Commvault File System Agent installed.

• Verify that the data access node has enough disk space to restore the largest backup image from DPM. If you plan to restore multiple backup images in parallel, you must have disk space equal to the largest backup image * the number of parallel restores. For example, 30 GB *5 = 150 GB.

• Create the credentials to be used for the DPM migration in the Credential vault. For more information, see Store Account Information with Credential Vault.

  Note

  For existing Data Import customers, password migrations will occur seamlessly, and data import operations will continue to function using the existing credentials. However, when editing configurations, customers may need to add credentials through the Credential Manager in order to view them directly in the report.

Procedure

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

2. From the Command Center 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 DPM data on the data access node.

7. Optional: In the Third Party Install Path box, type the base path for DPM installation.

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 DPM, 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 data import operation.

    • DPM Server Name - Name of the DPM backup server.

    • DPM Command Server - The name of the server where you run the DPM Commands (DPM Backup Server). Verify that you have the Commvault File System Agent installed on this server.

    • Data Access Node - Name of the Data Access Nodes that you configured. The Data access node must be the DPM client or the DPM server where you can restore the DPM backed up data for the import.

    • Data Access Node Host User - The admin user account to access the Data Access Node.

    • Data Access Node Host Password - Password for the admin user account.

    • Install Path on Data Access Node - The path where you installed the DPM software. For example, C:/Program Files/Microsoft System Center 2012 R2/DPM

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

    • Collect DPM Server Details - Enable to collect the DPM server details.

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

12. Click Load Jobs for the DPM server.

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

14. Click the Client Details tab.

    You can view the details for the selected clients.

15. Click the Job Details tab. You can view a list of backup jobs for the selected clients and date range.

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

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

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

What to Do Next

You can access and manage the files from the Command Center.

1. From the Command Center navigation pane, go to Protect > Files.

2. On the Files tab, select the DPM_clientname, and then go to Protocols > CIFS / NFS.

3. Click the Subclients tab, and then choose HPDP_files backupset.

   You can now restore the imported data from the list of subclients.