Review the following requirements to import Netbackup 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 NetBackup, use a separate backup plan with a one-day retention period on the storage policy.
-
Set up a Command Server
The Command Server is the server where you run the required NetBackup Commands (including bprestore command) to get the NetBackup client/job details and to restore the NetBackup client data to the data access nodes. Also, the Command Server must have NetBackup and the Commvault Filesystem Agent installed.
Note
-
The Command Server must be a NetBackup Media server or Master server where the “admincmd” folder is available. If you plan to import third-party data from multiple Master servers, and if you use the Media server as the Command Server, then use a separate Media server for each Master server when you configure the data import operation.
If the NetBackup Master server is an appliance (NetBackup appliance), then use the NetBackup Media server as the Command Server.
-
For Netbackup (NBU), Command Server configuration is not required for the customers who do not have administrative access to the NBU Master server.
To enable data import for the supported agents, contact your Sales or Customer Success team for assistance with purchasing the feature.
-
-
Install Python 3.x on the data acess node and the Command Server, and then set the path in the environment variable Path. If you installed the Commvault software on the data acess node and the Command Server before installing python, recycle CVD services.
-
To expedite the 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 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 NetBackup (NBU) data, rather than using the default NBU retention settings.
-
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 NetBackup 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 NetBackup Non-Windows restored data before importing into Commvault.
You must specify this folder path when you add data access nodes under Server Configuration in the report.
-
Create the credentials to be used for the NetBackup 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.