Preventive Service Planning
This document details the Hypervisor (Microsoft Hyper-V or VMware) backup and restore requirements for IBM® Spectrum Protect™ Plus V10.1.2
This document is divided into linked sections for ease of navigation. You may use the links below to jump to the section of the document you need.
Microsoft Hyper-V Server 2016
150 GB+ of drive space if Disk Type is set to Fixed Size during the installation procedure
16 GB memory
Backup and restore operations are only supported for virtual hard disks (VHDX), see also Known Issues and Limitations: IBM Spectrum Protect Plus V10.1.2.x
Note as per APAR IT30988 (1/10/20): indicated that shared virtual hard disks (shared VHDX) are not supported. However, beside shared VHDX, also virtual hard disks (VHD) are not supported.
All Hyper-V servers, including cluster nodes, must have the Microsoft iSCSI initiator Service running in their Services list. Set the service to Automatic so that it is available when the machine boots.
Hyper-V servers can be registered using a DNS name or IP address. DNS names must be resolvable by IBM Spectrum Protect Plus. If the Hyper-V server is part of a cluster, all nodes in the cluster must be resolvable via DNS. If DNS is not available, the server must be added to the /etc/hosts file on the IBM Spectrum Protect Plus appliance via command line. If more than one Hyper-V server is set up in a cluster environment, all of the servers must be added to /etc/hosts. When registering the cluster in IBM Spectrum Protect Plus, register the Failover Cluster Manager.
vSphere 5.5 and later
vSphere 6.0 and later
vSphere 6.5 and later
vSphere 6.7 and later
Ensure the latest version of VMware Tools is installed in your environment. IBM Spectrum Protect Plus was tested against VMware Tools 9.10.0.
Physical RDM (pRDM) LUNs are not supported for virtual machine backup and restore operations that involve VMWare snapshot technology.
In some cases, VMware Backup jobs fail with "failed to mount" errors. To resolve, increase the maximum number of NFS mounts to at least 64 through the NFS.MaxVolumes (vSphere 5.5 and later) and NFS41.MaxVolumes (vSphere 6.0 and later) values, as described in the following procedure: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2239.
10 January 2020