bpduplicate very slow
Created: 06 Feb 2012 | 6 comments
Hi,
I want to duplicate some images from one tape to another. The job runs with only 61 KB/min.
How can I speed up my bpduplicate???
My environment:
NBU 6.5.6
Master + Media-Server: Windows 2003 R2 EE x64
Drives: LTO4 - HP-ESL712E-Library
TIA
Dirk
Discussion Filed Under:
Group Ownership:
Comments
MORE info please....
What is your bpduplicate parameters?
Is source and destination media server the same server (eliminating network)?
Are you duplication MPX source images to non-MPX copies?
If so, slow duplicates are to be expected.
Have you checked/verified BUFFER settings?
http://www.symantec.com/docs/TECH17706
Do you have bptm log on media server(s) to track read and write process?
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Hi Marianne, I have started
Hi Marianne,
I have started the bpduplicate over GUI/catalog/duplicate.
source and destination media server is the same - it´s a san-media-server.
it´s a oracle-backup with RMAN.
our buffer-settings should be ok. The settings were recommended by a Symantec-supporter.
There is no bptm-log until now.
I don´t know if the tape is ok - because a normal restore of some images is aborted.this is the reason why I want to duplicate it.
Isolate the bottleneck
First confirm what Mary says, be sure you are not sending data across the network between media servers, the MPX is and issue but not a big deal, the next step is your buffers, the size of buffers you use to read and write are different you have SIZE_DATA_BUFFERS (read) and SIZE_DATA_BUFFERS_RESTORE (write) this is nice trick in case you source beffurs are smaller than 256kb, the other turn side is that you have a bigger buffer than 256kb, which tape drives cannot handle.
To isolate the issue run a DD test from your media server to the destination drives and check the speeds this will tell you if the issue is at OS, NBU or Source level, if the speeds are good than something is going on at NBU or Source level, the easy one here is to do the same with the source but in this case read from with dd command and send the data to null, this will remove the source from the equation or confirm the bottleneck, if speed is good than something is going on with netbackup configuration.
Hope this helps.
Regards.
Omar A Villa
Netbackup Expert
These are my personal views and not those of the company I work for
Were the source backups
Were the source backups multiplexed? If so, did you select the Preserve Multiplexing tickbox?
mpx -> non-mpx duplication will be S-L-O-W...
Please create bptm log on media server for troubleshooting.
Ensure that you have VERBOSE entry in vm.conf on media server to troubleshoot possible device errors. (NBU must be restarted for entry to take effect.) Device errors will then be logged in Event Viewer System and/or Application log.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
typo in SIZE_DATA_BUFFERS_DISK
If you have SIZE_DATA_BUFFERS_DISK defined, check for typo errors. Let say the intended value is 262144 but you my mistake wrote 214114. The result is painfully duplication speed (been there done that).
Assumption is the mother of all mess ups.
If this post solved you’re questions please send a gratitude by marking it as a solution.
Hi@ll, I have created the
Hi@ll,
I have created the file SIZE_DATA_BUFFERS_RESTORE with the same entry as SIZE_DATA_BUFFERS and selected Preserve Multiplexing.
Now my duplicate runs fine.
Thank you all
Dirk
Would you like to reply?
Login or Register to post your comment.