DRP quickly comes to mind. "move nodedata" with a preview may overcome that, but when doing DRP based on levels of service provided to the customer, being able to decide we only need 15 of the 3-5,000 offsite tapes trucked across the country is ... essential.
We jump through several hoops to determine which volumes belong to a particular node at DRP practice time with 4.x versions of TSM. A certain TSM competitor has a feature where you can specify different accounts for each drm event you define, thus better defining critical data sets. Back to the original question - You can always collocate/uncollocate fairly easily if you get into a crunch for tape space. Combining pools can be done, but takes more work. How confident are you that you will never run out of tape slots or tapes? Just my .02 on a slow Wednesday morning. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Wednesday, October 22, 2003 7:36 AM To: [EMAIL PROTECTED] Subject: Re: Collocation Vs Multiple Storage Pools From: Ray Baughman [mailto:[EMAIL PROTECTED] I've got a storage pool which contains data from 5 Nodes, which has collocation turn on. What are the pros and cons of running this way as opposed to having 5 separate storage pools? I was thinking management of the pools, but with only five pools this does not seem an issue. Also by having individual pools, I could easily find the tapes associated with a node. Any Ideas? Let's see: --ten separate reclamation sessions (five for primary pool, five for copy pool) --five different storage pool backups (from primary to copy) --more administration Why is it so important to point at a tape and know which node has data on it? -- Mark Stapleton ([EMAIL PROTECTED])
