> CommCell Console > Solutions and Use Cases > Import Backup Vendor Archives to Commvault > IBM Spectrum Protect Data Import

Requirements for Importing IBM Spectrum Protect FileSystem Data

Review the following requirements to import IBM Spectrum Protect filesystem data to Commvault storage.

  • Create a backup plan with proper retention rules for the data import operation. 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 imported data to use the minimal retention settings from IBM Spectrum Protect, use a separate backup plan with a one-day retention period on the storage policy.

  • Install the File System Agent on the TSM Command Server, which is the server where you will run the TSM admin (dsmadmc) command and where the baclient folder exists.

  • Choose one or more Data Access Nodes that has the TSM and Commvault File system agent installed where you will run the TSM (dsmc) command. You can choose either Windows (to import Windows data) or Linux clients (to import Linux data) as data access nodes for the data import operation. For example, if you are importing data from a Linux client, use a data access node on Linux. You can use either TSM Windows Command Server (or) TSM Linux Command Server to import both the TSM Windows and Linux data to Commvault.

  • 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 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 IBM Spectrum Protect (previously TSM) data, rather than using the default TSM retention settings.

  • Based on the OS type of the TSM Command Server, use one of the following scenarios to import Windows and Linux TSM data:

    Windows TSM Command Server

    • Scenario 1: The TSM Windows Command Server and the TSM Windows data access node are on the same server, and the Commserve server with the Workflow engine package is on a different server.
    • Scenario 2: The TSM Windows Command Server, the TSM Linux data access node, and the CommServe server are on different servers.
    • Scenario 3: The TSM Windows Command Server, the TSM Windows data access node, and the Windows CommServe server with the Workflow engine package are all on the same server.

    Linux TSM Command Server

    • Scenario 1: The TSM Linux Command Server and the TSM Linux data access node are on the same server. and the Commserve server with the Workflow engine package is on a different server.
    • Scenario 2: The TSM Linux Command Server, the TSM Linux data access node, and the Linux CommServe server with the Workflow engine package are on different servers.

    Note

    TSM Command Server configuration is not required for the customers who do not have administrative access to the IBM Spectrum Protect (TSM) backup server.

  • Copy the sqlite-jdbc-3.25.2.jar file to the following locations on the CommServe where the Workflow engine package is installed. The jar file is used to create the TSM client sqliteDB files (.db-shm, .db-wal and .db files) for the TSM restore/import process in the workflows.

    • < Install_Path >\Commvault\ContentStore\WFEngine
    • < Install_Path >\Commvault\ContentStore\WFEngine\classpath

    You can download the sqlite-jdbc-3.25.2.jar file from the following location: https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/3.25.2/

  • Create multiple staging directories on the TSM 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 TSM Windows restored data before importing to Commvault.
    • On non-Windows data access nodes, create a folder under any one of the file systems folders (such as the /tmp folder). The folder will be used as a staging directory to store the TSM Non-Windows restored data before importing the data into Commvault.

    You must specify this folder path when you add Data Access Nodes under Server Configuration in the report.

  • Grant proxy authority to the data access nodes.

    For example, assume that Node A is the TSM client node which stores the data and Node B is the data access node which restores or retrieves the data. To grant proxy authority to Node B, run the following command on the Tivoli Storage Manager Server administrative command line: 

    grant proxynode target=TSMclient agent=dataaccess node

  • Install Python 3.x on the CommServe system where the Workflow Engine package is deployed. After the installation, update the system’s Path environment variable to include the Python installation directory and recycle the CVD services to apply the changes.

×

Loading...