# Requirements for Avamar FileSystem Data

Review the following requirements to import Avamar file system data to Commvault storage:

1. 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 setting on the CommServe.

   Note

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

2. Configure the EMC Avamar Management Console Command Line Interface (MCCLI) package on a Linux computer that points to the Avamar server. Also, install the Commvault File System Agent on the Linux computer.

3. 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 multiplied by the number of parallel restores. For example, 30 GB * 5 = 150 GB.

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

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

6. 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 is used as a staging directory to store Avamar Windows restored data before importing it to Commvault. On non-Windows data access nodes (Linux data access node), create a folder under any file system (for example, /tmp). This folder is used as a staging directory to store Avamar non-Windows restored data before importing it to Commvault. You must specify this folder path when you add data access nodes under Server Configuration in the report.

7. Create multiple backup plans with different retention settings to allow importing groups of clients based on 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.

8. Create the credentials to be used for 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.

×

Loading...