# Importing Avamar Data

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

The app uses Avamar Management Console commands to fetch the clients, policies, and backup jobs from Avamar 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 staging clients. The recovered data is then backed up on to Commvault storage using configured backup plans and data access nodes.

The overall performance of the data import operation depends on multiple environmental factors, like restore throughput from Avamar, backup performance, attached storage, and resources. After the backup job is complete, the staging area is cleaned so that you can redo or import the same Avamar backup job if the earlier backup job did not complete successfully.

Note

The Data Import app can be accessed only by the Commvault professional services team. To use the app, contact your account representative and discuss a Professional Services engagement. To enable third-party 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 Avamar. 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 VMware.

## Before You Begin

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

- Create a backup plan with proper retention rules for migration. The backup plan should not be associated with any schedules.

  By default, the app applies the retention settings from the storage policy of the assigned backup plan. To switch to the retention settings of the third-party product, add the TPMHonourThirdPartyRetention additional settings on the CommServe.

  Note

  To allow the migrated data to use the minimal retention settings from Avamar, use a separate backup plan with a one-day retention period on the storage policy.

- Configure the EMC Avamar Management Console Command Line Interface (MCCLI) package on a Linux computer pointing to the Avamar Server. Also, install the Commvault File System Agent on the Linux computer.

- Verify that the data access node has enough disk space to restore the largest backup image from Avamar. 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.

- Verify that the data access node (staging client) has Avamar and Commvault File System Agent installed. You can choose either a Windows or a Linux client as the data access node for the data import operation. For example, if you are importing data from Linux client, use a data access node on Linux.

- To expedite the data import process, you can configure multiple data access nodes. You can configure the data access nodes from the Server Configuration tab of the Data Import Report. Only the configured data access nodes are listed in the Enter Migration Settings page in the report.

- Create multiple staging directories on the data access nodes:

  - On Windows data access nodes, create a folder under any one of the drives (for example, D:). The folder will be used as a staging directory to store the Avamar Windows restored data before importing to Commvault. On non-Windows data access nodes (Linux data access node), create a folder under any one of the file systems (for example, /tmp) folder. The folder will be used as a staging directory to store the Avamar Non-Windows restored data before importing to Commvault. You must specify this folder path when you add data access nodes under Server Configuration in the report.

- Create multiple backup plans with different retention settings to allow importing groups of client based on the storage plans. This approach is intended for customers who prefer to define custom retention policies for their migrated Avamar data, rather than using the default Avamar retention settings.

- Create the credentials to be used for the Avamar 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 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 Avamar data on the data access node.

7. Optional: In the Third Party Install Path box, type the base path for Avamar 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 Avamar, 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.

      Using the Unique Alias Name, you can configure multiple drives for staging data on each data access node.

    - Avamar Server Name - Name of Avamar backup server.

    - Select credential - Select the appropriate credential from the list.

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

    - Destination Domain - The domain name of the Avamar client. For example, /clients.

    - Management Console Command Server - The name of the Linux client where you installed the Avamar management console for command line interface (MCCLI).

    - Avamar Install Path on Command Server - The path where you installed the Avamar software on the MCCLI client. For example, /usr/local/avamar/.

    - 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 Avamar and Commvault infrastructure load capability and scale aspects.

    - Collect Avamar Server Details - Enable to collect the Avamar server details.

    - Server Plan – Name of the backup plan that you configured for this migration.

    - NDMP Migration - Toggle to enter configurations required for NDMP data import.

    - NDMP Filer - the file server used as the `--fileraddr` parameter in the `avndmp` command line.

    - NDMP Restore Path - the restore path used as the `--restoretarget` parameter in the command line.

    - avndmp sysdir path - the path used as the `--sysdir` parameter in the command line and is appended with the file server name.

    - avndmp vardir path - the path used as the `--vardir` parameter in the command line and is appended with the file server name.

    - NDMP Command client - The client where the “avndmp” command is executed to start Avamar NDMP restore.

    - AVNDMP Restore Command Credential - Required to pass the avndmp user ID and password in the “avndmp” command line to restore Avamar data. This can be configured in the Credential Manager and then selected from the drop-down option.

    - Exported CIFS mount path - The path from which the NDMP restored contents are used as input for the Commvault backup.

    - CIFS Credential - Required if credentials are needed to access this path.

    The Avamar Master server is listed under Backup Server Configuration.

12. Click Load Jobs for the Avamar Master server.

13. In the DomainName box, select the Avamar domain name.

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 Next. Optional: To list the backup jobs of all the clients in the specified Avamar domain, move the Get Jobs For All Clients toggle to the right.

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 and date range.

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

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

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

Note

If the Avamar 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 Avamar command line operations, contact Dell EMC support.

×

Loading...