We implemented the Normal, Monthly, and Quarterly node model for regulatory retention. Each node that requires it has three nodes, with 90 day, 5 year, and 10 year retention, with the frequency of backups matching the names. It was the best way overall, for us, to get it done. I would love for an archive function to be available, but alas, there isn't one. See Ya' Howard Coles Jr. Sr. Systems Engineer (615) 296-3416 John 3:16!
________________________________ From: ADSM: Dist Stor Manager on behalf of Shawn Drew Sent: Tue 12/29/2009 3:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] MSSQL archives We rolled out several SQL TDP agents this year and I'm only realizing now there doesn't seem to be a facility for long-term archiving. I noticed that Differential and Full backups can be bound to separate management classes (Unlike NDMP backups) I *assumed* that Full backups could have different management classes from each other. (I.E. A special year-end Full backup, bound to management class "07YEAR") However, I just tested it, and it rebinds ALL of the previous Full backups to the new management class. Then when I run another backup to the original MC, all the full backups, including the "07YEAR" backup gets rebound to the default MC. So, it seems my options are: - Tell the SQL admins to perform a filesystem .BAK backup, just for the Year-End archive. - Configure an additional SQL node for each host to hold the year-end Full backup. Both seem pretty unappetizing. Any other ideas? Regards, Shawn
