Veritas NetBackup™ Troubleshooting Guide
- Introduction
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- About troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Recovering a Windows client disk
The following procedure explains how to perform a total recovery of a Windows NetBackup client in the event of a system disk failure.
NetBackup Bare Metal Restore (BMR) protects client systems by backing them up with a policy configured for BMR protection. A complete description of BMR backup and recovery procedures is available.
See the Bare Metal Restore System Administrator's Guide:
http://www.veritas.com/docs/DOC5332
This procedure assumes that the Windows operating system and NetBackup are reinstalled to boot the system and perform a restore.
The following are additional assumptions:
The NetBackup client was running a supported Microsoft Windows version.
The NetBackup client was backed up with a supported version of NetBackup client and server software.
The NetBackup master server to which the client sent its backups is operational. You request the restore from this server.
The backups included the directory where the operating system and its registry resided.
If the backups excluded any files that resided in the directory, you may not be able to restore the system identically to the previous configuration.
Defective hardware has been replaced.
Before starting, verify that you have the following:
Windows system software to reinstall on the NetBackup client that being restored. Reinstall the same type and version of software that was previously used.
NetBackup client software to install on the client that being restored.
Special drivers or other software that is required to make the hardware operational (for example, a special driver for the disk drive).
IP address and host name of the NetBackup client.
IP address and host name of the NetBackup master server.
The partitioning and the formatting scheme that was used on the system to be restored. You must duplicate that scheme during Windows installation.
To recover a Windows client disk
- Install a minimal Windows operating system (perform the Express install).
During the installation, do the following tasks:
Partition the disk as it was before the failure (if partitioning is necessary). Then, reformat each partition as it was before the failure.
Install the operating system in the same partition that was used before the failure.
Specify the default workgroup. Do not restore to the domain.
Follow any hardware manufacturers' instructions that apply.
- Reboot the system when the installation is complete.
- Configure the NetBackup client system to re-establish network connectivity to the NetBackup master server.
For example, if your network uses DNS, the configuration on the client must use the same IP address that was used before the failure. Also, it must specify the same name server (or another name server that recognizes both the NetBackup client and master server). On the client, configure DNS in the Network dialog, accessible from the Windows Control Panel.
- Install NetBackup client software.
Ensure that you specify the correct names for the client server and master server.
To specify the client name, start the Backup, Archive, and Restore interface on the client and click NetBackup Client Properties on the File menu. Enter the client name on the General tab of the NetBackup Client Properties dialog.
To specify the server name, click Specify NetBackup Machines and Policy Type on the File menu.
Refer to the NetBackup Installation Guide for instructions:
- Install any NetBackup patches that had previously been installed.
- Enable debug logging by creating the following debug log directories on the client:
install_path\NetBackup\Logs\tar install_path\NetBackup\Logs\bpinetd
NetBackup creates logs in these directories.
- Stop and restart the NetBackup Client service.
This action enables NetBackup to start logging to the bpinetd debug log.
- Use the NetBackup Backup, Archive, and Restore interface to restore the system files and user files to the client system.
For example, if all files are on the C drive, restoring that drive restores the entire system.
To restore files, you do not need to be the administrator, but you must have restore privileges. For instructions, refer to the online Help or refer to the following:
See the NetBackup Backup, Archive, and Restore Getting Started Guide:
http://www.veritas.com/docs/DOC5332
NetBackup restores the registry when it restores the Windows system files. For example, if the system files are in the C:\Winnt directory, NetBackup restores the registry when it restores that directory and its subordinate subdirectories and files.
- Check for ERR or WRN messages in the log files that are in the directories you created in step 6.
If the logs indicate problems with the restore of Windows system files, resolve those problems before proceeding.
- Stop the NetBackup Client service and verify that the bpinetd program is no longer running.
- Restart the NetBackup client system.
When the boot process is complete, the system is restored to the state it was in at the time of the last backup.