My client has a TS3310 library with 6 x LTO3 drives and want to add (and eventually replace with) six LTO5 drives.
They want to keep the six LTO3 drives alongside the LTO5 drives.
So, is it best to define a second library within TSM, with a second dvice class? My thoughts were to have a devc defined
as Ultium3c and the new one as ultrium5c. The existing format of 'DRIVES' is not valid when i have a mixture of drives.
In terms of migrating the data off LTO3, will TSM allow me to run a 'move data' from the LTO3 to LTO5 volumes, bearing in
mind they are in a separate library?
My initial advice was to:
- remove all LTO3 scratch volumes.
- replace the LTO3 drives with the LTO5 drives
- populate as many slots as possible with new LTO5 media
- define drives and paths to TSM
- run move data to start emptying and removing the LTO3 media
Best to stick to my initial advice?
They want to keep the six LTO3 drives alongside the LTO5 drives.
So, is it best to define a second library within TSM, with a second dvice class? My thoughts were to have a devc defined
as Ultium3c and the new one as ultrium5c. The existing format of 'DRIVES' is not valid when i have a mixture of drives.
In terms of migrating the data off LTO3, will TSM allow me to run a 'move data' from the LTO3 to LTO5 volumes, bearing in
mind they are in a separate library?
My initial advice was to:
- remove all LTO3 scratch volumes.
- replace the LTO3 drives with the LTO5 drives
- populate as many slots as possible with new LTO5 media
- define drives and paths to TSM
- run move data to start emptying and removing the LTO3 media
Best to stick to my initial advice?