1-Touch for Windows: System Requirements

The following are the requirements for 1-Touch on Windows:

Client

Operating System
Microsoft Windows Server 2019 (Standard, Datacenter) (64-bit only)
Microsoft Windows Server 2019 Editions
Windows 2016
Microsoft Windows Server 2016 Editions Nano Servers are not supported. For more information, see Considerations for Microsoft Windows Server 2016.
Windows 10
Microsoft Windows Client 10 Editions
Windows 8
Microsoft Windows Client 8.1 For more information, see Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.
Microsoft Windows Client 8
Windows 2012
Microsoft Windows Server 2012 Editions
Microsoft Windows Server 2012 R2 Editions For more information, see Considerations for Microsoft Windows Server 2012, 2012 R2, and Windows 8.x.
Windows 7
Microsoft Windows 7 Editions
Windows Server 2008
Microsoft Windows Server 2008 Editions with a minimum of Service Pack 1 Server Core installations are not supported.
Microsoft Windows Server 2008 R2 Editions Server Core installations are not supported.
Windows Vista
Microsoft Windows Vista Editions *1-Touch recovery is not supported on Windows Vista client computers that operate in a language other than English.
Windows Server 2003
Microsoft Windows Server 2003 Editions [Extended Support] *1-Touch recovery is not supported on Windows 2003 client computers that operate in a language other than English.
Windows XP
Microsoft Windows XP Editions with a minimum of Service Pack 3 [Extended Support] *1-Touch recovery is not supported on Windows XP computers in the following cases: Computers that operate in a language other than English. Computers that use SCSI disks on Hyper-V. Computers upgraded from Windows 2000 to Windows XP operating system.

Hard Drive

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.

Processor

All Windows-compatible processors are supported.

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 (1014508).

As a general rule of thumb, each version of the VDDK supports vCenter Server for the two previous major versions and for the next minor version. For example, VDDK 6.0.0 can be used with vCenter Server 5.5, 5.1, or 6.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 Version	Commvault Support	Notes
4.1 (all updates)	V11 GA and later V10 GA and later	If VMs are part of ESX 4.1, then streaming and IntelliSnap backups are supported only through the vCenter. You cannot use a standalone ESX 4.1 server.
5.0 (all updates)	V11 GA and later V10 GA and later
5.1 (all updates)	V11 GA and later V10 GA and later
5.5 GA (all minor updates)	V11 GA and later V10 SP5 and later
5.5 Update 1 (all minor updates)	V11 GA and later V10 SP9 and later
5.5 Update 2 (all minor updates)	V11 GA and later V10 SP9 and later
5.5 Update 3 (all minor updates)	V11 GA and later V10 SP9 and later
6.0 GA (all minor updates)	V11 GA and later V10 SP 10 with HotFixes 20 and 21, or later service packs
6.0 Update 1 (all minor updates)	V11 GA and later V10 SP12 and later
6.0 Update 2 (all minor updates)	V11 SP4 and later V10 SP13 and later
6.0 Update 3 (all minor updates)	V11 SP7 and later V10 SP15 and later
6.5 GA (all minor updates)	V11 SP7 and later
6.5 Update 1 (all minor updates)	V11 SP9 and later

Supported Hypervisors

All Windows-compatible hypervisors are supported for 1-Touch Recovery.

Support for Azure

You can use the Virtualize Me feature to convert any physical computer to a Microsoft Azure Resource Manager virtual machine.

For more information, see Virtualize Me for Azure: System Requirements.

Notes

Recovery Considerations

Obtain the valid Microsoft license key for the Windows operating system to perform Virtualize Me 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 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 and Virtualize Me is not supported for system drive on GPT dynamic disk.
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 the1-Touch recovery.
You must use a wired internet connection to recover a laptop.
You cannot restore mount points using 1-Touch Recovery or Virtualize Me operations.

Recovery Support

1-Touch supports 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 is supported for systems which boot from SAN or the recovery of SAN attached disks.
1-Touch Recovery and Virtualize Me support virtual machines created using Microsoft Hyper-V and VMWare.
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 Virtualize Me operations are not supported on Windows 2000 client computers.
Client is a MediaAgent feature is not supported for Virtualize Me. You can use 1-Touch interactive and non-interactive restores to restore a MediaAgent computer.

Partitions

Ensure that the client does not have multiple active partitions. You cannot perform 1-Touch recovery if the client has multiple active partitions.
1-Touch recovery using Hyper-V is not supported if the Windows operating system is installed on a Disk 2 partition.
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 and Virtualize Me is not supported for VLAN (Virtual Local Area Network) configurations where the NIC (Network Interface Control) is configured with VLAN tagging.

DISCLAIMER

Third-party maintenance (minor) releases or service packs that are supported by the Commvault software may not be listed in our System Requirements. When possible, Commvault provides information on any known issues related to these minor releases or service packs. In some cases, these minor releases or service packs affect how the Commvault software works. Commvault software may experience changes in functionality as the result of the third-party minor release or service pack. These changes are beyond the control of Commvault. Platforms that are supported in the current version of Commvault software may not be supported in earlier versions of the software. Contact your software provider to ensure that third-party minor releases or service packs are compatible with the Commvault software. Additional considerations regarding minimum requirements and End-of-Life policies from third-party vendors also apply.