QUICKCOPY TAPE DUPLICATION DRIVER

The slower read performance from MSDP will cause the tape write buffer to empty faster than it can be filled. The current capacity and maximum theoretical write speeds are listed below for some tape drive generations.įor example, if a given MSDP storage server can rehydrate at 100 MB/sec on average, it would be impractical to allocate four LTO4 drives for duplication use which can write at a combined 480 MB/sec. Knowing the max write speed of the tape drive in relation to the source storage unit IO ( read speed) can help in determining the number of drives that could be allocated to the storage unit. To optimize duplications to tape, the generation of the tape/drive needs to be known. These should be tuned based on the backup/duplication load, available hardware, and server resources. The default SLP/lifecycle parameters and other resource management settings are not optimized in a way that makes best use of tape hardware. No error is directly caused by poor duplication performance, but some indirect failures could include:

should be explored in combination with these steps.

QUICKCOPY TAPE DUPLICATION DRIVER

Any possible hardware issues, driver updates, storage file system issues, etc. This article covers tuning Storage Lifecycle Policy (SLP)/lifecycle parameters, IO streams, job limits, SLP windows, and other resource management methods optimize disk to tape duplication performance. Backup jobs running out of time in the start windows status 196s.Duplication to tape from disk storage units such as AdvancedDisk, MSDP, and other OST technologies may not be performing optimally.

Quickcopy tape duplication