# Import backup vendor archives to Commvault

Commvault provides a Data Import solution that you can use to import historical long-term data protected by a third-party backup vendor software to Commvault repository. The third-party backup jobs are restored as files, and then backed up using the Commvault File System agent. The Data Import solution allows importing file data along with attributes such as ACL, modified time, and creation time, as long as the source third-party application supports restoring these attributes.

After you import the data, users can access and manage the files from the Command Center.

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.

## Key Features

- Fast and efficient mechanism to import large number of files to the Commvault storage.

- Protect the data by scheduling backups to Commvault storage.

- Search the files based on custom properties from the Command Center.

## Supported Workloads

Data import supports the import of File system and Virtual Machine data from the third-party backup vendor. Refer to individual vendor data import documentation for more information.

## Licensing

Data Import supports both capacity-based and instance-based licensing models. Depending on the licensing model in use, either the volume of imported data will count against the capacity, or the number of imported clients will count against the instance-based limit. Customers must have an appropriate amount of licensing based on the size of the data or the number of client records being migrated. However, after importing data, customers can deconfigure the client to ensure it no longer consumes a license.

## Security Enhancement

All newly installed clients will block the execution of any executables or binaries located outside the installation folder, unless valid credentials are provided with the command. To disable this security feature, configure the nLimitedAdminAccess additional setting on admin computers.

To whitelist certain folders to execute the binaries, configure the sAdminWhiteListPaths additional setting on the target computer.

To whitelist certain executables for CVD to execute, configure the sAdminWhiteListBinaries additional setting on the target computer.

## Third-Party Migration Parallel Job Limitation

During any third-party migration, parallel migration behavior is constrained at the client and backup-year level. This is expected system behavior and must be considered during migration planning. Data Import allows only one active migration per third-party client per backup year. Recommendation / Best Practices

Run parallel migrations only when they are from different backup years or different third-party clients (for example, different NBU clients). Do not select parallel migrations for the same third-party client (for example, an NBU client) from the same backup year. In such cases, only one migration job will run, and the remaining jobs will remain in a Pending state. Pending jobs will automatically proceed once the active migration completes; no manual intervention is required.

×

Loading...