NetBackup restore jobs for more than 100,000 files may be delayed for several hours before starting to write data
|Article:TECH164518|||||Created: 2011-07-13|||||Updated: 2014-05-23|||||Article URL http://www.symantec.com/docs/TECH164518|
When restoring directories with a large number of files (more than 100,000), the job may remain queued and not go active. The job details may show "Begin restore" in the Activity Monitor for many hours. On the master server the bprd and a bpdbm process will be observed consuming a lot of CPU cycles.
The restore job will eventually start, but delays of longer than 17 hours have been observed.
NetBackup 7.1 and above are affected by this issue.
An algorithm change was made in NetBackup 7.1 that resulted in this delay when processing flat file backup of millions of files. Normally this type of backup is recommended for a FlashBackup policy which would not be affected, as opposed to a Standard or MS-Windows policy.
The formal resolution to this issue (Etrack 2373538) is included in the following release:
- NetBackup 7.6 Maintenance Update 2 (220.127.116.11)
NetBackup 18.104.22.168 is available for download at the link included in the Related Articles below.
The restore will eventually complete if it is allowed to run long enough.
The restore can also be completed by selecting smaller subdirectories (< 100,000 files each) and submitting each as an independent restore job.
Restores of 2.5 million files are processed for 17+ hours in bpdbm before going active
Article URL http://www.symantec.com/docs/TECH164518