Troubleshooting

This section includes the following topics:

Problems booting from CD or DVD
Long restore times
Solaris media boot network parameters issue
How to recover client when BMR configuration is deleted accidentally
First boot after BMR restore fails on UNIX platforms
Client network based boot issue
Verify backup failure while recovering Windows client
The VM takes long time for booting after BMR Physical backup conversion to virtual machine is performed on 32-bit architecture Windows OS
BMR-enabled physical backup to Virtual Machine conversion job fails on Windows platform
Troubleshooting issues regarding creation of virtual machine from client backup
If the boot server has a base installation of Solaris 10 update 11, the creation of SRTs can fail
Many services on Solaris 11 and newer print warning messages during a system boot and during BMR first boot
Solaris Zone recovery on Solaris 11 and newer takes time to reconfigure after a BMR restore during first boot
A Solaris BMR restore operation fails if the text-installer package is not present in the customized AI ISO
The /boot partition must be on a separate partition for a multiple device-based OS configuration
Multiple error messages might be displayed during the first boot after the restoration of a client with ZFS storage pools
BMR may not format or clear the ZFS metadata
Specifying the short name of the client to protect with Auto Image Replication and BMR
A restore task may remain in a finalized state in the disaster recovery domain even after the client restores successfully
IPv6 support for BMR
Automatic boot may fail for HP-UX after a restore
Prepare to Restore may not work for a Solaris client
Use of Virtual Instance Converter (VIC) hosts on Windows (x64) having NetBackup 8.1 is not supported in NetBackup 8.1 release for NetBackup 8.0 and earlier clients

Troubleshooting

Feedback

Feedback