Hi Lloyd, We have tried Backupset for a wild now but we see that it takes approx 3 weeks to archive all 300 nodes. If the backupset fails then do we need to restart the entire job and we are getting behind the schedule. We looking at to create smaller "node groups" but still it takes a long time. :(
I was thinking to maybe setup a second TSM Server and export the data from one server to the other and that maybe can reduce the time. I'm guessing that the problem is probably all tape mounts that is required to collocate all data so maybe that is something to look at? Or what do you think? A good information to know is that the end-user looking at to grow up to 100 TB in the next 4-5 years. Thanks Christian -----Ursprungligt meddelande----- Från: Lloyd Dieter [mailto:[EMAIL PROTECTED] Skickat: den 3 januari 2008 13:09 Till: [email protected] Ämne: Re: Suggestion for Archive? Christian, This sounds like an excellent use for backupsets, or else possibly periodic exports. Other sites have a second instance of TSM that is used for periodic large backups and long-term retention requirements. I generally discourage archives for large amounts of data, due to the DB entries that are created, as well as the amount of time required to create those archives. The only sites that I have with "out of control" database growth are attempting to do what you describe. -Lloyd On Thu, 03 Jan 2008 11:09:13 +0100 Christian Svensson <[EMAIL PROTECTED]> wrote thusly: > Hi all, > > I hope you all had a great new year. > > Just a quick question. > > Has anyone tried to archive 20 TB data every mouth for 10 years? If yes > how are you doing that and how is your environment looks like? > > > > Happy New year > > Christian
