System Requirements for 1-Touch for Windows

1-Touch for Windows is only available for clients being protected as File Servers. This is not available for clients being protected as Endpoints.

Recover Windows laptops using 1-Touch.

7 GB minimum of hard disk space for installing the software.

500 MB of free disk space is required for job result directory.

500 MB of free disk space is required for log directory.

The RAM size of the client must be two times the size of the Live CD. The size of the Live CD can vary depending on the processor type and drivers added to the image. The default size is approximately 1 GB. You can verify the size at the Software Store.

To perform an offline restore, make sure that you have an additional 30 GB of free disk space that includes the Job Results and Log files directory.

7 GB minimum of hard disk space for installing the software.

500 MB of free disk space is required for job result directory.

500 MB of free disk space is required for log directory.

The RAM size of the client must be two times the size of the Live CD. The size of the Live CD can vary depending on the processor type and drivers added to the image. The default size is approximately 1 GB. You can verify the size. The 1-Touch ISO image is located at:

SystemRecovery\Images\Windows 32-bit\BOOT_IMAGE\ISO\sources

SystemRecovery\Images\Windows x64\BOOT_IMAGE\ISO\sources

To perform an offline restore, make sure that you have an additional 30 GB of free disk space that includes the Job Results and Log files directory.

Recovery Considerations

• Obtain the valid Microsoft license key for the Windows operating system to perform 1-Touch recovery operations.

• Ensure that Windows is not installed on the drive other than C:\. The unattended installation of Windows on a drive other than C:\ is not supported. You cannot perform the Online or Offline Restore when Windows is installed on a drive other than C:\.

• 1-Touch does not support recovery for multiboot systems.

• 1-Touch does not support recovery of disks managed by Veritas Volume Manager due to inconsistent results with VDS.

• 1-Touch recovery operations are not supported for system drive on GPT dynamic disk.

• 1-Touch recovery operations are not supported on a client with multiple instances.

• Restores are not supported for Resilient File Systems (Refs) and Storage Pools that operate on Microsoft Windows 2012 or Windows 8.0.

• You must use a wired internet connection to recover a laptop.

• You cannot restore mount points using 1-Touch recovery operations.

• During a 1-Touch recovery operation, a dynamic disk is converted to a basic disk and is recovered as a basic disk. You must manually bring the dynamic disk back online after the operation completes.

Recovery Support

• 1-Touch recovery operations are not supported for USB disks. By default, system state backups do not back up the content in USB disks.

• 1-Touch recovery operations are supported for NVMe (non-volatile memory express) disks.

• 1-Touch support recovery of BitLocker Encryption enabled volumes with lock opened during backup; post restore this option is disabled and you need to manually enable the BitLocker Encryption option on the volumes.

• 1-Touch recovery operations are supported for systems which boot from SAN or the recovery of SAN attached disks.

• If the client computer has more than 100 disks attached, then the system drive is restored initially, and then the other drives and data are restored later.

• Use 1-Touch interactive recovery to restore a MediaAgent computer. You cannot use 1-Touch non-interactive restore operations to restore a MediaAgent computer.

Partitions

• Ensure that the client does not have multiple active partitions. You cannot perform 1-Touch recovery operations if the client has multiple active partitions.

• If you have a recovery partition, make sure that it is removed prior to a backup operation.

Network and Protocols

• Ensure that the TCP/IP Services are configured on the computer before performing the backup.

• IPv6 is not supported for 1-Touch recovery of clients.

• NIC teaming is retained only if the restore operation is performed to the same computer. After a 1-Touch recovery operation to a dissimilar computer, the NIC teaming configuration will not be maintained.

• 1-Touch recovery operations are not supported for VLAN (Virtual Local Area Network) configurations where the NIC (Network Interface Control) is configured with VLAN tagging.

CommServe

To enable 1-Touch recovery, the Force per-client certificate authentication on CommServe option has to be turned off on the CommServe at least for the duration of the recovery. This option can be accessed from the CommServe Control Panel by clicking on Certificate Administration.

Recovery Considerations

• Obtain the valid Microsoft license key for the Windows operating system to perform VirtualizeMe and 1-Touch recovery operations.

• Ensure that Windows is not installed on the drive other than C:\. The unattended installation of Windows on a drive other than C:\ is not supported. You cannot perform the Online or Offline Restore when Windows is installed on a drive other than C:\.

• 1-Touch and VirtualizeMe do not support recovery for multiboot systems.

• 1-Touch and VirtualizeMe do not support recovery of disks managed by Veritas Volume Manager due to inconsistent results with VDS.

• VirtualizeMe and 1-Touch Recovery operations are not supported for system drive on GPT dynamic disk.

• VirtualizeMe and 1-Touch Recovery operations are not supported on a client with multiple instances.

• Non-interactive restores are not supported on computers that have operating system disks connected using an iSCSI controller.

• Restores are not supported for Resilient File Systems (Refs) and Storage Pools that operate on Microsoft Windows 2012 or Windows 8.0.

• Use Disaster Recovery to recover a CommServe. You cannot recover a CommServe using the 1-Touch recovery.

• You must use a wired internet connection to recover a laptop.

• You cannot restore mount points using 1-Touch Recovery or VirtualizeMe operations.

• During a VirtualizeMe or a 1-Touch recovery operation, a dynamic disk is converted to a basic disk and is recovered as a basic disk. You must manually bring the dynamic disk back online after the 1-Touch recovery operation completes.

• You must enable the Remote Desktop Protocol (RDP) on the source computer so that you can access the restored Azure virtual machine.

• A Windows access node hosted on the Amazon Web Services account is required with the Virtual Server Agent installed.

Recovery Support

• VirtualizeMe and 1-Touch Recovery operations are not supported for USB disks. By default, system state backups do not back up the content in USB disks.

• VirtualizeMe and 1-Touch Recovery operations are supported for NVMe (non-volatile memory express) disks.

• VirtualizeMe and 1-Touch support recovery of BitLocker Encryption enabled volumes with lock opened during backup; post restore this option is disabled and you need to manually enable the BitLocker Encryption option on the volumes.

• VirtualizeMe and 1-Touch Recovery operations are supported for systems which boot from SAN or the recovery of SAN attached disks.

• If the client computer has more than 100 disks attached, then the system drive is restored initially, and then the other drives and data are restored later.

• You can recover a Windows 2000 client computer by performing an online system state restore. Non-interactive and VirtualizeMe operations are not supported on Windows 2000 client computers.

• Use 1-Touch interactive recovery to restore a MediaAgent computer. You cannot use 1-Touch non-interactive restore or VirtualizeMe operations to restore a MediaAgent computer.

• On Azure, only Azure Resource Manager deployments are supported.

• Microsoft Azure Stack does not support Unified Extensible Firmware Interface (UEFI) firmware, so VirtualizeMe of source machines in UEFI firmware mode is not supported.

• You cannot use VirtualizeMe for Azure to restore iSCSI volumes.

Partitions

• Ensure that the client does not have multiple active partitions. You cannot perform VirtualizeMe and 1-Touch Recovery operations if the client has multiple active partitions.

• If you have a recovery partition, make sure that it is removed prior to a backup operation.

Network and Protocols

• Ensure that the TCP/IP Services are configured on the computer before performing the backup.

• IPv6 is not supported for VirtualizeMe and 1-Touch recovery of clients.

• NIC teaming is retained only if the restore operation is performed to the same computer. After a VirtualizeMe or 1-Touch recovery operation to a dissimilar computer, the NIC teaming configuration will not be maintained.

• VirtualizeMe and 1-Touch Recovery operations are not supported for VLAN (Virtual Local Area Network) configurations where the NIC (Network Interface Control) is configured with VLAN tagging.

Supported Hypervisors

1-Touch Recovery is supported for Microsoft Azure, Hyper-V, VMWare, and AWS hypervisors.

VMware vCenter Server Support

The following versions are supported for vCenter Server and vCenter Server Appliance. vCenter Server support includes support for vSphere, Virtual Disk Development Kit (VDDK), ESX or ESXi, and file system versions as provided by the vCenter version.

For more information, see Correlating build numbers and versions of VMware products.

Generally, each version of the VDDK supports vCenter Server for the two previous major versions and for the next minor version. For example, VDDK 8.0.1 can be used with vCenter Server 7.x, or 8.0 Update 1.

When VMware issues new versions or updates, Commvault tests against the current service pack before announcing support. For new VMware versions or updates released between Commvault service packs, and for earlier supported versions or service packs, Commvault provides continuing support, including Hot Fixes as needed to address VMware changes to functions that affect backup and recovery.

vCenter Server Versions

• 8.x (all minor updates)

• 7.x (all minor updates)

Support for Azure and AWS

You can VirtualizeMe to convert any physical computer to a Microsoft Azure Resource Manager virtual machine or an Amazon EC2 instance.

In addition to the Client system requirements, review the following Proxy Client Computer requirements for Azure and AWS hypervisors:

Operating system	Processor architecture
Microsoft Windows Server 2022	All Windows-compatible processors are supported
Microsoft Windows Server 2019 (Standard, Datacenter) (64-bit only)	All Windows-compatible processors are supported
Windows 2016	All Windows-compatible processors are supported
Microsoft Windows Server 2016 Editions Nano Servers are not supported. For more information, see Considerations for Microsoft Windows Server 2016.	All Windows-compatible processors are supported