Incremental Catalog backup fails with Status 41 (network connection timeout)
Exact Error Message
15:38:11.876 [18923] <16> bpbrm main: db_FLISTsend failed: network
connection timed out (41)
15:38:11.876 [18923] <16> bpbrm main: db_FLISTsend failed: network
connection timed out (41)
Details:
Following a 10-minute delay, the bpbkar log file on the client ( /usr/openv/netbackup/logs/bpbkar/log.
Creating or amending the file /usr/openv/netbackup/bin/DBMto to contain the value "30" increases the timeout (from the default of 10 minutes) allowing the incremental backups to complete. However, it was found that the incremental backup then took around 8 hours to complete.
The bpdbm log ( /usr/openv/netbackup/logs/bpdbm/log. ) shows:
The delays can be seen between the entries for "add_files: updating" and "add_files: 5000 files added", for a given process, which has cumulative effect on the time the Catalog backup takes.
Solution:
It was found that following these changes, the Incremental Catalog backup successfully completed in 15 minutes.
Overview:
An Incremental Catalog Backup fails with Status 41 (network connection timeout), whereas the Full Catalog Backup completed in approximately 20 minutes.
Troubleshooting:
The bpbrm log file on the media server ( /usr/openv/netbackup/logs/bpbrm/log.
An Incremental Catalog Backup fails with Status 41 (network connection timeout), whereas the Full Catalog Backup completed in approximately 20 minutes.
Troubleshooting:
The bpbrm log file on the media server ( /usr/openv/netbackup/logs/bpbrm/log.
15:38:11.876 [18923] <16> bpbrm main: db_FLISTsend failed: network connection timed out (41)
Following a 10-minute delay, the bpbkar log file on the client ( /usr/openv/netbackup/logs/bpbkar/log.
15:28:12.868 [18954] <2> bpbkar SelectFile: INF - Resolved_path = /usr/openv/netbackup/db/images/master1/1231000000/SYM_INC_1231711779_UBAK.f
15:38:59.484 [18954] <4> bpbkar PrintFile: /data/openv/netbackup/db/images/master1/1231000000/
15:38:59.484 [18954] <16> bpbkar sighandler: ERR - bpbkar killed by SIGPIPE
15:38:59.484 [18954] <2> bpbkar sighandler: INF - ignoring additional SIGPIPE signals
Creating or amending the file /usr/openv/netbackup/bin/DBMto to contain the value "30" increases the timeout (from the default of 10 minutes) allowing the incremental backups to complete. However, it was found that the incremental backup then took around 8 hours to complete.
The bpdbm log ( /usr/openv/netbackup/logs/bpdbm/log.
10:31:34.768 [19001] <2> add_files: updating
/usr/openv/netbackup/db/images/master1/1243000000/tmp/NB-Catalog_1243231645_INCR.f
10:48:29.184 [19001] <2> add_files: 5000 files added to
/usr/openv/netbackup/db/images/master1/1243000000/tmp/NB-Catalog_1243231645_INCR.f
10:48:35.557 [22486] <2> add_files: updating
/usr/openv/netbackup/db/images/master1/1243000000/tmp/NB-Catalog_1243231645_INCR.f
11:05:50.079 [22486] <2> add_files: 5000 files added to
/usr/openv/netbackup/db/images/master1/1243000000/tmp/NB-Catalog_1243231645_INCR.f
The delays can be seen between the entries for "add_files: updating" and "add_files: 5000 files added", for a given process, which has cumulative effect on the time the Catalog backup takes.
Solution:
- Create /usr/openv/netbackup/bin/DBMto with the entry "30" to correct the Status 41 Error, restart the NetBackup services.
- Create the file /usr/openv/netbackup/MAX_FILES_PER_ADD, with the entry 500, restart the NetBackup services.
It was found that following these changes, the Incremental Catalog backup successfully completed in 15 minutes.
No comments:
Post a Comment