Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

How to enable multi-stream duplication within SLP

Created: 30 Aug 2010 • Updated: 15 Oct 2013 | 1 comment
LanceYoon's picture
This issue has been solved. See solution.

Does any one know how to enable multi-stream duplication?

I’ve created SLP as below. And policy set to use multi-stream. So up to 4 data streams created when backup performed. Right after backup completed, duplication started. but it uses only one tape drive. I expected the same number of data streams to occurs as well when duplicating.

I’ve searched manuals and other online sources. It seems that NetBackup does not support what I’m trying. I want multistream happens when duplication process occurs from dedup storage to tape library.

SLP
1.Backup  --> Destination is  "Deduplication Storage"
2.Duplication --> Destination is  "Tape Library (8 Drives) "

Any input will greatly be appreciated!

Comments 1 CommentJump to latest comment

Nicolai's picture

Do you know the "Best Practices for using Storage Lifecycle Policies" ?

It say on page 13 "Considerations when duplicating multiple stream application backups"

Many application backups such as Oracle and MS-SQL can be configured to back up data in multiple parallel streams. When data is backed up in this way the application API usually expects to restore it in parallel as well. This is not an issue if the backup is written to disk or to tape (using multiple tapes or multiplexing) but the process of duplicating from disk to tape or VTL is sequential and a set of backup streams written in parallel to disk and then duplicated to tape will be stored sequentially on the tape. This can present a problem if a restore needs to be made from the tape copy as the restore process may pause or even time out waiting for the required streams to be located on the tape.

Said that , you may achieve what you wan't by tuning MIN_GB_SIZE_PER_DUPLICATION_JOB/MAX_GB_SIZE_PER_DUPLICATION_JOB in the LIFECYCLE_PARAMETERS file.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

SOLUTION