03-01-2020 06:11 AM
03-01-2020 06:44 AM
03-01-2020 01:28 PM
It doesn't really make sense to add a tape STU to an existing disk STUG.
You indicate there are two disk STU's. Can you do one at a time, so leaving the STUG available?
The other advantage of this, is if something goes wrong during the resizing process you will still have some storage available (this is me being risk adverse).
03-12-2020 05:16 AM
THank you for your response. However, the disk is actually being shared by 3 media servers, and because of performance issues, we have to remove it and just allocate a chunk to each media server. WE plan to destage all of the images to tape, and then add the tape storage unit to the Storage Unit Group before we remove the disk and re allocate it
03-17-2020 02:57 PM
In which case, I don't believe it will be a problem adding the tape STU to the group (even if this is unusual).
You may want to change (temporarily) how the STUG is managed (from load balanced to prioritised or failover as required, but possibly not necessary) to give more predictable behaviour.
How are you currently "sharing" the disk between three media servers - CIFS? and do they have their own separate folders to write to? Do you intend to continue this moving forward, or move to dedicated direct attached stsorage (which would provide the bst performance).
03-18-2020 06:25 AM
Thanks again for your input. Yes, it's the same storage, and each media server has it's own folder. Currently we keep 90% of the data on the dsik, and de-stage at 95%. The plan is to start keeping 80% on disk, then 70 % ... until we get down to zero. Then once everything is migrated to tape, we will suspend scheduling, add then add the Tape storage units, then remove the disk, resume scheduling, reconfigure the disk, add them back to the group suspend scheduling again, and then remove the Tape storage units