Yes, but one thing to keep in mind is that most people would also want to keep the "Last Version" also, even if it is inactive. The reason is that if someone deletes a file, the next day it would be inactive, but those are files that are often requested for restore.
Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Doug Thorneycroft [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 9:19 AM To: [EMAIL PROTECTED] Subject: Re: Idea for a TSM feature Yes, I posed a similar question a month or so ago, My idea was to add a switch to migration that would migrate only inactive files. This way you could restore an entire server using multiple sessions, without needing to use collocation or worry about tape contention. -----Original Message----- From: James Thompson [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 8:44 AM To: [EMAIL PROTECTED] Subject: Idea for a TSM feature Thought I would throw an idea I had for a TSM feature out on the listserv and get some thoughts no whether this would be useful or not. The feature that I would like to see is the ability to create a special disk storage pool, that would only migrate inactive versions of backup objects to the next storage pool. This would keep all the active versions on disk storage. I'm sure everyone has certain nodes(systems) that are of more importance than others. Could be the CEO's desktop filesystem or a critical server. Advantages: Fast restore of active versions. No tape mounts required for restore of active versions. Fast creation of backupsets. No tape mounts required for generating Backupsets (Instant Archives) Disadvantages: Higher hardware cost for additional disk storage. Any thoughts on the matter? James Thompson _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
