Veritas System Recovery 21 no longer supports upgrade from Symantec System Recovery 2013 R2.

Before you install Veritas System Recovery 21 on Windows 7 SP1, Windows 2008 SP2, Windows 2008 R2 SP1, or Small Business Server 2011 SP1 operating systems, ensure that the latest Windows updates are installed.

With Veritas System Recovery 21, when you install Veritas System Recovery, the Veritas System Recovery Disk creation package is deployed by default.

If your computer shares RAM with another device, such as your graphics card, then your computer may not meet the minimum RAM requirements for using the features of Veritas System Recovery 21. You should avoid sharing RAM if your computer only meets the minimum amount of RAM required by Veritas System Recovery 21.

For example, the minimum RAM requirement for Veritas System Recovery Disk is 512 MB. The entire RAM amount must be unshared and dedicated exclusively to Veritas System Recovery Disk. If it is not dedicated and unshared, you may run out of memory when you restore recovery points or perform other tasks using Veritas System Recovery Disk.

Refer to the Veritas System Recovery User's Guide for minimum system requirements.

If you use Microsoft BitLocker to secure the data on a drive, consider the following points:

Veritas System Recovery 21 does not support the computers that use the GRUB boot loader.

Veritas System Recovery 21 does not support the computers that use Fedora Core3 Ext2/Ext3 or Grub 2 boot managers.

Approximately to 1 GB is required for a full install of Veritas System Recovery 21, depending on the language of the product you select. If your system drive (typically, C) is low on disk space and you select an alternate drive to install Veritas System Recovery 21, approximately 30 MB of disk space is still required on your system drive. If your system drive is dangerously low on disk space (less than 100 MB), you should first free up more space before installing Veritas System Recovery 21.

After installing Veritas System Recovery 21, you are prompted to restart your computer. Restarting your computer is necessary to install and activate the system drivers, vtrack.sys, SSRFsF.sys, and genericmount.sys.

When you uninstall Veritas System Recovery 21, LiveUpdate remains installed on your computer. If you want to uninstall LiveUpdate, refer to your operating system's documentation for information about how to remove applications.

If you uninstall Veritas System Recovery 21, the capicom.dll file might still appear in the system directory. Capicom is a shared .dll file that is used to perform LiveUpdate for all Veritas products. If you have multiple Veritas products on your computer, or if it is unclear whether the file is needed, you can leave it there. Or if you are certain that the file is not longer needed, you can delete it.

If you uninstall any earlier version of this product, you might encounter a problem with the virtual volume driver. Uninstall and reinstall Veritas System Recovery 21. If uninstalling and reinstalling Veritas System Recovery 21 does not correct the issue, you may need to call Veritas Technical Support for assistance in correcting the product's registry entries.

If you use a network location as your backup destination, make sure that you have provided a valid network user name and password. Veritas System Recovery 21 frequently accesses the backup destination to verify that you have valid recovery points. If your network account is in a domain, common security procedures lock your account after a certain number of failed logon attempts. If your logon credentials are invalid, you could be locked out of your network account after multiple, failed attempts by Veritas System Recovery 21 to access the backup destination.

Sometimes Windows incorrectly reports insufficient hard disk space when a recovery point is saved to a Linux Samba share. To solve this issue, verify that Windows identifies the correct amount of space.

You can now boot a UEFI-based computer using a Veritas System Recovery Disk on a USB device.

When creating a Veritas System Recovery Disk, you might receive the following error:

file:\\windows\system32\winload.exe status: 0xc0000001 The selected entry could not be loaded because the application is missing or corrupted.

This error is known to occur if your operating system resides on a drive that is formatted to FAT32.

To resolve this issue, reset %TEMP% to point to a secondary drive that is formatted to NTFS and that has enough disk space to host temporary program files that are included in the Veritas System Recovery Disk .iso file (approximately 400 MB to 600 MB, depending on the language being used). Then re-create a Veritas System Recovery Disk.

Veritas System Recovery Disk on a USB is not supported for the following disks or drives:

You cannot perform a delayed restore using a Veritas System Recovery Disk on USB drive if the recovery points are stored on a network location.

When a Veritas System Recovery Disk creation fails or is stopped, the recovery disk creation process is stopped. In some cases some files are left mounted in a temporary (folder name, SymSrdTemp) location and the files cannot be deleted. The WimCleaner.exe utility unmounts any such mounted system files and deletes the temporary folder (SymSrdTemp). Veritas System Recovery provides the 32-bit version of the WimCleaner.exe utility. The location of utility: <VSRInstallPath>\Utility\WimCleaner.exe. You can double-click the exe file to run the utility or use the command prompt to run the utility.

When LightsOut Restore is set up, it installs the Veritas Recovery Environment directly to the file system on the system partition (you cannot change this location), and places a Veritas Recovery Environment boot option within the Windows boot menu.

LightsOut Restore does not work on BitLocked drives. Therefore, if you BitLock your system drive, you cannot recover the drive using LightsOut Restore.

If you cannot boot your computer using LightsOut Restore, it could be because your operating system resides on a drive that is formatted to FAT32.

To resolve this issue, reset %TEMP% to point to a secondary drive that is formatted to NTFS. Then re-create a custom Veritas System Recovery Disk.

The software adds 46 bytes of data as a Service Principal Name to the Computer Object of the base schema. This attribute is added for every computer in the domain on which the agent is installed.

The application does not have any special requirements for the network traffic to replicate the updates to full or partial replicas.

The software uses the Computer Object from the base schema and adds the Service Principal Name as an attribute to the object. This is the attribute that the software reads from the directory.

You cannot deploy the Veritas System Recovery 21 Agent to remote machines if Use simple file sharing and File and Printer Sharing are disabled on them. Refer to the Veritas System Recovery 21 User's Guide for information on how to enable Use simple file sharing and File and Printer Sharing.

You might receive a reconnect error when trying to manage a second computer.

To resolve this issue, use Windows Firewall to open TCP port 135 on both the source and the target computers, and then try the connection again.

You might receive a reconnect error when trying to manage a second computer. This error message appears in the status bar of the product user interface:

Connecting to agent on <remote computer name/IP address>. You do not have sufficient privileges to perform this operation.

This error might occur because Distributed COM (DCOM) is disabled on the computer.

When you define a backup job for C:\ drive on Windows 10, version 2004 BIOS machine, Veritas System Recovery does not include the newly created Windows recovery partition by default. Ensure that you select the recovery partition manually.

Refer to the following technote for additional information about this issue.

On a BIOS machine, when you upgrade the operating system to Windows 10, version 1809 or later, you must edit the existing backup job and manually add the newly created Windows recovery partition to the backup definition.

Refer to the following technote for additional information about this issue.

After you install or upgrade to Veritas System Recovery 21 on a Windows 7 SP1, Windows 2008 SP2, Windows 2008 R2 SP1, or Small Business Server 2011 SP1 operating system, if Windows updates are not up-to-date, the restart fails. Ensure that you install all Windows updates to avoid this issue.

Physical to virtual conversion to an ESXi Server 6.5 and later fails if the destination contains a '.' (period).

Veritas System Recovery 21 does not support backups or restores that take more than 72 hours using the Veritas System Recovery Disk, because of the WinPE limitation.

Veritas recommends that the system volumes for backup and restore should be less than 16 TB. If the backup or restore takes more than 72 hours, Veritas recommends that you restore the system volumes only using the Veritas System Recovery Disk and then proceed with volumes more than 16 TB in Veritas System Recovery 21.

Physical to Virtual (P2V) conversion to VMware ESXi (P2V to VMDK) is not supported for more than 2 TB volumes from Veritas System Recovery. Refer to the following technote for additional information about this issue.

Veritas System Recovery 21 does not support VHDX of more than 2 TB size for the Physical to Virtual (P2V) conversion using the SV2i file where the system volumes are a combination of GPT and MBR disks. Refer to the following technote for additional information about this issue.

Upload to Amazon S3 offsite copy fails if the recovery point file name has special or localized characters. Refer to the following technote for additional information about this issue.

If you have a computer with multiple operating systems, LightsOut Restore created on one operating system is detected by the other operating system and may result in compatibility issues. Refer to the following technote for additional information about this issue.

The Ignore recovery point corruption option excludes the corrupted portion of the backup during restore. The ignored portion may include drive metadata information and system files. In this scenario, if your drive metadata is corrupted, it becomes inaccessible and if the system files are corrupted your computer does not restart after restore.

If a recovery point is compressed with high compression techniques and it is corrupted, the chances of successful restore with the Ignore Image corruption option are low because of the v2i file structure limitation.

After you install Veritas System Recovery 21, you cannot boot into Windows 10 UEFI computers hosted in Hyper-V (Boot failure).

Virtual conversion to an ESXi server on an x64 platform fails if the ESXi host password contains the '@' character. Veritas System Recovery uses VMware VDDK for the virtual conversion. VMware VDDK cannot parse the '@' character in the password. Refer to the following technote for additional information about this issue.

In the Veritas Recovery Environment, you must reconnect to the iSCSI target to view the iSCSI volumes. To reconnect to the iSCSI target, open a command prompt, and run the following commands in the order listed:

You can convert recovery points of a UEFI-based computer to the VHDX format; and ESXi 5.0 and later. You cannot convert recovery points of a UEFI-based computer to a VMware Workstation Disk or a VHD format. These virtual formats do not support the UEFI technology.

Managing Newer Versions of Veritas System Recovery

You cannot use previous versions of Veritas System Recovery to manage newer versions. For example, you cannot manage Veritas System Recovery 21 using Veritas System Recovery 18.

Veritas System Recovery 21 Backup Performance

Veritas System Recovery 21 is configured to provide optimal performance for most users. The default performance settings are recommended except in certain situations that require the backup window to be highly optimized. To facilitate performance tuning in these limited situations, go to the following tech note that provides information about the performance registry keys.

In some cases the alternate settings may improve performance. Alternate performance settings generally have the most effect when the recovery point (V2i file) is saved to a network share. When the recovery point is saved to a second internal hard drive or to an external USB or FireWire hard drive, the default settings generally provide the best results.

Veritas System Recovery 21 does not support creation of multiple Veritas System Recovery Disks on a single USB disk. For example, you cannot create a 32-bit and 64-bit recovery disk on the same USB drive.

Veritas System Recovery 21 does not support Windows 8.1 Update with wimboot partition for UEFI (Unified Extensible Firmware Interface)-based computers having a solid-state drive (SSD).

Veritas System Recovery 21 does not support dynamic volumes created on 4K native disks.

If you cannot run Veritas System Recovery 21 on a server that you have "hardened" using Microsoft's guidelines, do the following:

Veritas System Recovery 21 does not support restoring encrypted volumes (for example, HP encrypted volumes). You must un-encrypt the volumes before backing them up.

Veritas System Recovery 21 supports dual boot or boot-strapping environments. If you want to manually edit your partition's boot.ini file, do the following:

If a hard drive having Domain Controller setup is copied to a new disk using the Copy My HardDrive option, the users are not able to log in to the domain. This issue occurs as the Domain Controller detects a new hard disk signature and puts itself in isolation state.

If you restore a file or folder that is shared, the sharing permissions are not restored. You must manually reconfigure the sharing permissions.

If you restore a volume that is configured for ReadyBoost, the ReadyBoost settings are not restored. After you restore the volume, you must manually reconfigure the ReadyBoost settings.

Backup of a volume that is dedicated to ReadyBoost fails. To back up the volume ensure that it is not dedicated to ReadyBoost.

If you are running Japanese and English computers on the same network, Japanese computer names may appear garbled in the console.

When you configure a backup job to start a new recovery point set, ensure that the new set is not scheduled to start when the backup job is scheduled to create an incremental recovery point. If you do, the backup job that is scheduled to create the new recovery point set might not run as expected.

Veritas System Recovery 21 uses the Microsoft DISKPART utility to create and delete dynamic volumes.