Veritas™ System Recovery 23 Readme
- Veritas™ System Recovery 23 Readme
- Granular Restore Option
The drive(s) may not appear in System Recovery even if they appear in Microsoft Windows Disk Management.
System Recovery is a sector-based backup software that relies on the accurate partition information. This ensures a reliable and accurate backup. If errors are detected on any partition, that volume may not be displayed in System Recovery user interface as it is not viable for backup. Restoring an inaccurate volume could result in data loss or corruption. This is working as designed to protect your data. The errors need to be recovered when the volume is not displayed in System Recovery user interface.
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.
Physical to virtual conversion to an ESXi Server 6.5 and later fails if the destination contains a '.' (period).
Veritas System Recovery 23 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 23.
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 23 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 23, you cannot boot into Windows 10 UEFI computers hosted in Hyper-V (Boot failure).
Ensure that you install all Windows updates to avoid this issue.
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.
This issue is not observed on an x86 platform.
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:
net start msiscsi
iscsicli QAddTargetPortal <portal IP address>
iscsicli QloginTarget <target iqn>
Replace <target iqn> with the iqn of the iSCSI target.
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 23 using Veritas System Recovery 18.
Veritas System Recovery 23 Backup Performance
Veritas System Recovery 23 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 23 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 23 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 23 does not support dynamic volumes created on 4K native disks.
If you cannot run Veritas System Recovery 23 on a server that you have "hardened" using Microsoft's guidelines, do the following:
If the Veritas System Recovery 23 service is running, stop it by using either the Services Control Panel or by using a command prompt and typing the following command:
net stop "Veritas System Recovery"
Open a command prompt, and change to the root of your Veritas System Recovery 23 install (the default is C:\Program Files\Veritas\Veritas System Recovery).
Run the batch file, fixinstall.bat by typing the name of the batch file from the command prompt in the installation folder.
Start the Veritas System Recovery 23 service from the Services Control Panel or by using a command prompt and typing the following command:
net start "Veritas System Recovery"
Veritas System Recovery 23 does not support restoring encrypted volumes (for example, HP encrypted volumes). You must un-encrypt the volumes before backing them up.
Veritas System Recovery 23 supports dual boot or boot-strapping environments. If you want to manually edit your partition's boot.ini file, do the following:
Do not select the option to restart after a recovery point is restored.
Restore the recovery point.
From within Veritas System Recovery Disk, choose> .
Make the needed changes, and then restart your computer.
If a hard drive having Domain Controller setup is copied to a new disk using theoption, 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 23 uses the Microsoft DISKPART utility to create and delete dynamic volumes.
With One-to-one management, if the server in EFI mode deploys the agent on a Windows Server Core Computer, the Push Agent fails with the error E0D3EBC0.
In the Veritas System Recovery 23 version, unable to boot from the typical SRD ISO on the Windows 11 Education and Pro N editions.