I've been using this forum for quite a while, but never had the opportunity/need to post. Most of my answers were found lurking in the background and searching previous threads. I haven't seen much about my "issue", so I thought I would post and see what feedback I could get.
After 4 years of a legal hold / eDiscovery mandate, our need to retain everything has been lifted. A bit of background information.
Environment - Hardware
AIX 5.3.12 SP4 running TSM 6.2.2.
Library - L700 LTO-2 (phased out but still connected)
SpectraLogic T50e LTO-5 (fully configured and managing all data to tape transactions)
DataDomain 890 for VTL (recently configured and managing entire environment)
TSM - Notable information
Single TSM Database @ ~560Tb.
1000+ nodes
8Pb occupancy pool
7-8Tb backed up nightly
~90 AIX hosts (active)
~500 Windows hosts (active)
With so much data residing in 1 database, we can't make a drastic change like updating the retention limits on and entire policy, it would kill the server. Instead, we are looking at taking smaller bites of the apple. These include (but are not limited to) the following ...
Remove nodes that have been decommissioned
Mothball the environment and start over
Start 2nd instance of TSM and share resources. Migrate nodes to new server.
Create all new policy groups and migrate hosts to it 1 by 1.
Has anybody else had the same scenario and how did you resolve. At this point, we are in the planning phase of how we will attack this giant problem. We know and understand it will take several months to complete. I've never managed TSM in a "normal" environment, so going through 400 tapes per week and working all day to keep pools low enough to get through the next days backups is all I know.
Any help from people who have went through a similar scenario would be appreciated.
Regards,
QueueBall
After 4 years of a legal hold / eDiscovery mandate, our need to retain everything has been lifted. A bit of background information.
Environment - Hardware
AIX 5.3.12 SP4 running TSM 6.2.2.
Library - L700 LTO-2 (phased out but still connected)
SpectraLogic T50e LTO-5 (fully configured and managing all data to tape transactions)
DataDomain 890 for VTL (recently configured and managing entire environment)
TSM - Notable information
Single TSM Database @ ~560Tb.
1000+ nodes
8Pb occupancy pool
7-8Tb backed up nightly
~90 AIX hosts (active)
~500 Windows hosts (active)
With so much data residing in 1 database, we can't make a drastic change like updating the retention limits on and entire policy, it would kill the server. Instead, we are looking at taking smaller bites of the apple. These include (but are not limited to) the following ...
Remove nodes that have been decommissioned
Mothball the environment and start over
Start 2nd instance of TSM and share resources. Migrate nodes to new server.
Create all new policy groups and migrate hosts to it 1 by 1.
Has anybody else had the same scenario and how did you resolve. At this point, we are in the planning phase of how we will attack this giant problem. We know and understand it will take several months to complete. I've never managed TSM in a "normal" environment, so going through 400 tapes per week and working all day to keep pools low enough to get through the next days backups is all I know.
Any help from people who have went through a similar scenario would be appreciated.
Regards,
QueueBall