UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Lieutenant Commander
Lieutenant Commander
161 views

Backup failed after timeout

Hi!

The backup was started. The tape has been loaded into the drive. Disk Agent started on the client server.
And nothing happens. Job logs show timeouts:

[Normal] From: **PERSONAL INFORMATION REMOVED** "E:" Time: 18.02.2021 13:41:18
STARTING Disk Agent for server-srv2.domain.com:/E "E:".

[Normal] From: **PERSONAL INFORMATION REMOVED** "F:" Time: 18.02.2021 13:41:19
STARTING Disk Agent for server-srv2.domain.com:/F "F:".

[Major] From: **PERSONAL INFORMATION REMOVED** "Task_day3" Time: 18.02.2021 15:41:23
[61:1002] The VBDA named "E:" on host server-fr3.domain.com
reached its inactivity timeout of 7200 seconds.
The agent on host will be shutdown.

[Major] From: **PERSONAL INFORMATION REMOVED** "Task_day3" Time: 18.02.2021 15:42:00
[61:1002] The VBDA named "F:" on host server-fr1.domain.com
reached its inactivity timeout of 7200 seconds.
The agent on host will be shutdown.

The debug.log file has entries:

2/18/2021 10:57:17 AM CHANGE_JOURNAL.10828.7448 ["/da/clp/win_ntfs/change_journal/DirectoryDB.cpp $Rev: 20234 $ $Date:: 2011-05-13 17:13:42":1370] A.06.20 b407
DirectoryDB::UnlockDB: Could not open directory database lock file (null)lck backupSpaceId = \Shares

2/18/2021 10:57:17 AM CHANGE_JOURNAL.10828.7448 ["/da/clp/win_ntfs/change_journal/DirectoryDB.cpp $Rev: 20234 $ $Date:: 2011-05-13 17:13:42":914] A.06.20 b407
DirectoryDB::Cleanup: Could not unlock the directory database with backupSpaceId \Shares

2/18/2021 10:57:19 AM VBDA.10828.7448 ["/da/bda/win32.c $Rev: 34480 $ $Date:: 2012-11-07 14:50:46":2159] A.06.20 b407
GetVolumeName failed for Mountpoint [/H] with error [123]


2/18/2021 10:57:19 AM VBDA.10828.7448 ["/da/bda/win32.c $Rev: 34480 $ $Date:: 2012-11-07 14:50:46":2159] A.06.20 b407
GetVolumeName failed for Mountpoint [\\?\H:] with error [123]


2/18/2021 10:57:20 AM VBDA.10828.7448 ["/da/bda/win32.c $Rev: 34480 $ $Date:: 2012-11-07 14:50:46":2159] A.06.20 b407
GetVolumeName failed for Mountpoint [\\?\H:] with error [123]

Populator::GetFullPathname: Could not find parent directory for parentRefNum 11. This is an error unless the index corresponds to the root directory (zero).
Populator::GetFullPathname: Could not find parent directory for parentRefNum 11. This is an error unless the index corresponds to the root directory (zero).
Populator::GetFullPathname: Could not find parent directory for parentRefNum 11. This is an error unless the index corresponds to the root directory (zero).
Populator::GetFullPathname: Could not find parent directory for parentRefNum 5715574. This is an error unless the index corresponds to the root directory (zero).

2/18/2021 11:08:08 AM DP_POP.8028.8364 ["/da/clp/win_ntfs/change_journal/db_populate/Populator.cpp $Rev: 17510 $ $Date:: 2011-01-31 19:39:19":446] A.06.20 b407
Populator::StreamToFile: Could not find full path for file ??????

2/18/2021 5:54:14 PM CHANGE_JOURNAL.12148.548 ["/lib/cmn/dbglog.c $Rev: 24973 $ $Date:: 2011-10-06 18:01:05":533] A.06.20 b407
###
RUNNING LOW ON MEMORY!
virtual total: -128 [KB]
virtual used: 85416 [KB]
physical total: 33553908 [KB]
physical used: 32937908 [KB]
commit limit: 88077460 [KB]
mem usage: 88072316 [KB]
mem usage: 99 [%]
###

What does error [123] mean and how can I fix it?

The servers are running constantly. They contain a lot of files that many people work with. Why is there a timeout?

 

 

0 Likes
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.