Forum Discussion
Before we look at the log, please give us more info.
NBU version?
VCenter version?
OS on Master/media/backup host?
(Unix is not supported as backup host)
OS on VM being backed up?
Is the problem with this VM only, or with others as well?
Has backup worked before?
- IT-Infrastructu4 years agoLevel 3
Hi Marianne
NBU version? 7.7.2
VCenter version? - 6.7.0
OS on Master/media/backup host? - Windows 2008 R2
OS on VM being backed up? Linux cnbjlnx400 4.4.0-189-generic #219-Ubuntu SMP Tue Aug 11 12:26:50 UTC 2020 x86_64 x86_64 x86_64 GNU/LinuxIs the problem with this VM only, or with others as well? - Yes only with one VM server
Has backup worked before? - Yes till yesterday it is working fine
- Marianne4 years agoLevel 6
Do you know why there is 23 minutes difference between Job Details and VxMS log?
Could you please upload bpbkar log where we can trace PID 8648 ?
In all honesty, I am battling to find anything useful in VxMS log.
There are these warnings and errors towards the end of the file, but I have no idea what it means. Google search of the warnings and errors find nothing.13:20:44.0149 : buildRvpBitmap:VixGuest.cpp:1998 <WARN> : Virtual disk optimization disabled
13:20:44.0305 : allocMemory:RvpBitmapX64.cpp:531 <ERROR> : Exception: VERIFY_WIN32_HANDLE
13:20:44.0305 : log:Error.cpp:249 <WARN> : Error: 0x00001070 occured in file D:/NB/7.7.2/src/vxms/plugin/common/map/rvp/RvpBitmapX64.cpp, at line 531
13:20:44.0305 : log:Error.cpp:249 <WARN> : Error: 0x00001070 occured in file D:/NB/7.7.2/src/vxms/plugin/common/map/rvp/RvpBitmapX64.cpp, at line 531
13:20:44.0305 : vixMapObjCtl:VixCoordinator.cpp:977 <WARN> : Returning: 4208
13:20:44.0305 : vix_map_objctl:libvix.cpp:1216 <WARN> : Returning: 4208Looking at Status Code Ref Guide for status 4208, I'm not sure how relevant this is, since the master server seems to be your media server and backup host (client):
NetBackup status code: 4208
Message: Could not send snapshot metadata or statefiles
Explanation: Snapshot metadata that is created by the client cannot be transferred on the master server.
Recommended Action: Verify the following:
-
The NetBackup client can communicate with the NetBackup master.
-
The state file location on the NetBackup client has write permission. The typical location of the NetBackup state file on the NetBackup client is as follows:
Windows:
C:\Program Files\Veritas\NetBackup\db\snapshot\<client>
UNIX:
/usr/openv/netbackup/db/snapshot/<client>
- IT-Infrastructu4 years agoLevel 3
I Have tried clearing the path and initiated the backup but again it got failed with same error
-
- Marianne4 years agoLevel 6
You may also want to go through the list of possible reasons for Status 6 in the Status Code Ref Guide:
https://www.veritas.com/content/support/en_US/doc/44037985-127664609-0/v15096798-127664609
See if anything is relevant here.
- Hamza_H4 years agoModerator
Hello,
I agree with Marianne ,vxms logs doesn't match with the detaillled status (there is a delay of 23 minutes) did you share a snip of logs of a first retry and detailled status of the second?
I can see that you used san, did you try with nbd?
please share bpbkar logs.
what are types of Filesystem on the vm ?
Related Content
- 4 months ago
- 7 months ago
- 5 months ago