# Requirements for Importing IBM Spectrum Protect VMware Data

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

- Verify that you have an existing IBM Spectrum Protect environment where VMware backups are configured and a new or existing CommCell environment with basic backup infrastructure, like CommServe, MediaAgents, and backup plans.

- Review the requirements for data access node / Command Server

  - Verify that you have both the Commvault file system package and IBM Spectrum Protect server installed on these servers.
  - You need a minimum of 16 GB RAM with 8 vCPUs and 1 TB hard disk space. The hard disk drive space requirement depends on the parallel jobs factor and the size of the source VMs. The disk space can be calculated based on VM size * 5. After the import is complete, the staging area is pruned immediately.
  - The IBM Spectrum Protect components must be able to run specific admin commands to fetch the client and job information.
  - Verify that you have the following software installed on these servers:
    - RHEL 8.0 and above with latest updates
    - Commvault Platform Release 2024E File System and MediaAgent Package
    - IBM Spectrum Protect Server Package

- Create a separate mount for datastore export and staging area. For example, /cvstorage with a minimum of 100 GB storage disk space. Expose this drive as NFS to the ESXi host below to use as NFS datastore.

- Create a VMWare ESXi Server in the IBM Spectrum Protect configuration for temporary recovery

- Create a NFS v4 datastore using the storage mounted on the data access node

  The IBM Spectrum Protect VMs are recovered on the NFS datastore created on the ESXi host. For example, the app populates the /cvstorage/year/subclientid path on the data access node with the restored VM backup data, which is then backed up as regular file system data on Commvault storage.

- Create a new datacenter inside vCenter and add the ESXi host

- For IBM Spectrum Protect VM workloads, select the Data Mover client (TSM proxy node) that was originally used for the VM backups. During the load job, the workflow uses this client to run dsmc commands and retrieve the list of backed-up virtual machines.

×

Loading...