We have some DBAs who are upset that they get media waits when several TDP sessions in parallel try to restore objects that have ended up on the same VTL volume. (When DBAs get upset, their managers get upset. And when their managers get upset....) I understand, as I'm sure we all do, that "tape" volumes are inherently single-access at a time, but since we're fairly well invested in LAN-free backups, we can't easily convert to FILE devices as our primary storage pools.
I see two work-arounds: migrate from VTL to a FILE-based storage pool, or use a FILE-based copy-storage pool. The latter scheme would leave files accessible for LAN-free clients when possible. My hope is, rather than go to a media wait, sessions that can't get data from a VTL volume because another session has a tape would instead get the volume from an available COPY storage pool volume that is available for multiple simultaneous reads. Can anyone confirm that TSM will use an available copy pool volume rather than make the session wait for a primary tape volume? Thanks, Nick --- Nick Laflamme (512) 977-2344 ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
