Flashes (Alerts)
Abstract
Microsoft Windows system state backup might be incomplete on systems with installed HP OpenView products. If system state is restored the system will not boot. A fix for this problem is described in this document.
Content
Problem description
Microsoft Windows system state backup might be incomplete on systems with installed HP OpenView products. In this case, if the system state is restored the system will not boot. One known symptom is a Microsoft Windows Boot Manager message indicating that the NLS data is missing or corrupted.
A subsequent investigation of the restored system shows that many system state files were not backed up, which is why they could not be restored. No related error is reported during the system state backup or restore operation. The operating system will need to be repaired by copying in the correct versions of the missing files, or it will need to be rebuilt.
This problem is also described in APAR IC72446.
The fix for this problem can be found in the "Recommended action" section of this document.
Additional technical detail
During system state backup, the TSM backup-archive client uses Microsoft Volume Shadowcopy Service (VSS) to determine which system state components to back up and, for each component, which files to back up.
Files protected by Windows Resource Protection (WRP) are part of the Microsoft VSS System Writer and thus part of the system state. These files are normally enumerated by the VSS System Writer and backed up as part of the system state. These files are not backed up as part of the file system where the files reside.
The installation of the HP OpenView component "HPOvXpl" creates an incorrectly formatted registry value that causes many of the files protected by WRP to be omitted from VSS System Writer file enumeration. Since these files are not included in the VSS System Writer enumeration, they are not backed up as part of the system state. Therefore a system state restore operation will be incomplete. The missing files are critical to the operating system and their absence renders the operating system unbootable.
Note: This problem is not specific to Tivoli Storage Manager, but can occur for any backup product that uses VSS to back up the system state on a system with HP OpenView installed.
Conditions for this problem to occur
This problem will occur if all of the following conditions are met:
1. The operating system is any of the following:
- Microsoft Windows Server 2008
- Microsoft Windows Server 2008 R2
- Microsoft Windows Vista
- Microsoft Windows 7
This problem applies to any edition of these operating systems.
Microsoft Windows Server 2003 and Microsoft Windows XP are unaffected by this problem.
2. An HP OpenView product is installed. HP OpenView is a suite of products including:
- HP OpenView Operations for Windows
- HP Operations Manager for Windows
- HP Performance Agent
- HP Performance Manager
- HP Operations Agent
- HP Reporter
3. The following registry subkey, value and data are present on the system and the data portion contains one or more occurrences of the "/" character:
- Subkey
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HPOvTrcSvc
Value
- ImagePath
Data
- C:/Program Files/HP/HP BTO Software/bin/ovtrcsvc.exe
Note: The Data string is a path that identifies the location of program ovtrcsvc.exe. The path on your systems might differ from the one shown above but the important detail is the use of "/" instead of "\" as a directory delimiter. If the delimiter is "/" then the system is affected by this problem. If the path contains the correct delimiter "\" then the system is not affected.
4. Any version of the Tivoli Storage Manager backup-archive client is used to back up system state.
Recommended action
Check your Microsoft Windows systems to see if they meet the conditions described above. If an HP OpenView product is not installed on a system then the system should not be affected. If an HP OpenView product is installed or if you are not sure an HP OpenView product is installed, then use the instructions below to determine if the problem exists and if so, correct it.
Attention: These instructions require you to use the Windows Registry Editor, regedit.exe, to view and edit the registry. Errors in editing the registry can render the operating system unstable or unbootable. If you are not familiar or comfortable with editing the registry, ask your system administrator for assistance.
An alternative to performing these steps is get the fix directly from HP at http://support.openview.hp.com/selfsolve/document/KM1034078. You must have a valid HP support contract to access the content. Disclaimer: IBM makes no claim or representation as to the completeness, accuracy or currency of the content or any part thereof.
1. Click Start then click Run. In the Open box type regedit. Click OK. This will launch the registry editor.
2. Locate then click on the following registry subkey:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HPOvTrcSvc
If this subkey does not exist then the system is unaffected by this problem; in this case no further action is necessary for this system.
3. In the Name column locate ImagePath. Examine the value in the corresponding Data column. If the value is
- C:\Program Files\HP\HP BTO Software\bin\ovtrcsvc.exe
then the system is unaffected by this problem; in this case no further action is necessary for this system. Note that the value might differ from the one shown above but the important detail is that the correct "\" directory delimiter is used.
If the value is
- C:/Program Files/HP/HP BTO Software/bin/ovtrcsvc.exe
then the system is affected by this problem. In this case, proceed with the next step.
4. Right-click on ImagePath then click Modify. In the Value data box carefully change each occurrence of "/" to "\" but leave the rest of the data unchanged. If you make a mistake, click Cancel then try this step again. When you are satisfied with the changes click OK.
5. Reboot the system. Until the system is rebooted the problem will persist.
6. Back up the system state. Most users schedule daily backup operations that include the system state, in which case a correct system state backup will occur at that time. If you prefer not to wait for the next scheduled backup you can manually back up the system state.
Related Information
Was this topic helpful?
Document Information
Modified date:
25 September 2022
UID
swg21462430