Gathering Data Protector Logs for HP When opening a Data Protector support case with HP, you will need server specs, patch level, session report, and extended logs. Here is how you get this info. Hp J3680 Installation Software here. HP has not confirmed this vulnerability and software updates are not available. Indicators of Compromise HP Data Protector versions 8.0 and prior are affected.
What follows is the recommended information and logs one should gather when opening a Data Protector case with HP. Note: the following only applies to a Data Protector 7.01 Windows Environment.
• Server Specs • Data Protector Patch Level • Full Session Report • Extended logs 1) Server Specs No matter the issue you are having, invariably the server specs for the Cell Manager need to be provided. This may also apply to your Installation Servers, Backup Host, or any other affected hosts by the issue you are having. Generally the OS/Build is acceptable, such as: Windows 2008 R2 Enterprise x64. 2) Data Protector Patch Level As with providing server specs, the patch level of all related systems will usually be requested as well. Run this command from every host that has the DP inet agent installed: omnicheck -patches Copy/Paste the output into the support case for each system related to the issue. 3) Full Session Report More than likely you will want to include the full session report from the backup job that had issues.
This session report will contain a detailed output of the backup job containing all of the related messages you would see in the DP GUI. You can find the Session ID by browsing the Reporting context in DP GUI, and selecting your job. The right pane will look something like this: [138:742] Backup session '2013/07/22-3' of the backup specification 'VEAgent VM-Desktops',backup group 'VMWARE' has errors: 19.
In this example, 2013/07/22-3 is the Session ID. Cinque Storie Ferraresi Pdf Printer there. Copy/Paste that value into the following cmd, which you will execute on the Cell Manager: omnidb -session -report >C: session.txt Upload the session.txt file to HP Support case.
4) Extended logs In many cases, the default session report will not provide enough debug information to find what is actually the problem. Epson R3000 Repair Manual. What will be needed is some extended logging. However, to gather this additional debug info, you will have to first enable the debugging, re-produce the issue, and then disable the debugging. The debug process will typically create dozens of log files, depending on the issue, which you can then zip up and upload to the HP Support case. There are two primary debug use cases: • Troubleshooting Data Protector GUI • Troubleshooting DP Backup Jobs that are failing/etc. Troubleshooting DP GUI Exit the GUI, and restart it from the MS-DOS prompt in debug mode: cd Program Files Omniback bin manager.exe –debug 1-500 yourname.txt Reproduce the error in the DP GUI and then exit the GUI to stop the debugging.
Depending on the nature of the issue, this will create a debug.txt file on every host related to the issue. On each host, in the following location, look for long file names starting with OB2DBG and ending with yourname.txt: (Windows 2003) Program Files Omniback tmp (Windows 2008) Program Data Omniback tmp Gather all these debug files from each host, zip them up (per host), and upload to HP Support Case. Canon Ir2318l Printer Driver For Windows 7 32bit. Troubleshooting Failing Backup Jobs Depending on the nature of your failing backup job you might deviate from these steps, but this will generally apply to all failing backup jobs: On the Cell Manager open the CMD prompt and execute the following: omnisv stop / omnisv start -debug 1-500 yourname.txt On any other related system(s) with a DP INET agent installed, go to Windows services, stop the Data Protector INET service.
Coments are closed