I have a similar issues as discussed in http://www.veritas.com/community/forums/using-bpdu... . I want to clarify if we list and identify the images need to cancelled and cancelled it, shall we call the cancelled backup duplicatye images again to be process for tape duplication?
AFAIK, if you cancel the SLP processing from the CLI, or cancel SLP by image from the CLI, then all incomplete stages for the SLP or image are cancelled.
If you show us the output from these, then we might be able to help you spot a configuration problem:
bpstulist -L -g nbstl -L nbstlutil report
Please see the attached outcomes.
If you cancel a backup image under SLP control, you have to duplicate it manual. It is not possible to re-SLP a backup image that has either been canceled or marked as complete.
Furthermore, if you cancel a backup image, it may expire immediately, depending on retention period.
A backup image under SLP control has infinity retention, when either SLP is being completed or canceled the original retention is applied.
Ok, since we are not able to re-run it again, how can we improve the backup duplication performance (tape library)? We dont want to lose any data here. Any suggestions?
Ensure you have NUMBER_DATA_BUFFERS and SIZE_DATA_BUFFERS configured
in [INSTALL_PAHT]/Netbackup/db/config
create file NUMBER_DATA_BUFFERS and put 256 or 512 in it
create file SIZE_DATA_BUFFERS and put 262144 in it
file must be called exactly as above - not dot extension are allowed. That should speed up tape writes a lot.
http://www.veritas.com/docs/000016306
What is the recommended values for NUMBER_DATA_BUFFERS and SIZE_DATA_BUFFERS? I've attached my master/media server configuration/system information
Also here's the tape library/tape cartridge info:
LTO Ultrium 6 Tape Drive
2.5 TB native cartridge capacity (up to 6.25 TB with 2.5:1 data compression)
576 GB/hour (160 MBps) native data transfer rate
6 Gbps SAS connectivity
NUMBER_DATA_BUFFERS = 256
SIZE_DATA_BUFFERS = 262144
Pretty universal settings providing good performance on all systems. Please see my previous post on how to configure or use the tech note I linked to.
Leave client registry to default - 0
Historical NET_BUFFER_SZ on the client used to be a discussion subject , but now has no meaning by now becuase of modern TCP/IP stack, NIC TCP offload etc etc.
Best practices for NET_BUFFER_SZ and Buffer_size, why can't NetBackup change the TCP send/receive space
http://www.veritas.com/docs/000026262
