The advantage of using EXPORT: The "frozen" copy of the data belonging to the old "water" are removed from the TSM server and tape library. No new DB entries are created (well, 1, for the export tape), while moving "water" to a new domain as "ice" means the data and db entries are recreated when the new "water" backs up again.
The disadvantage of using EXPORT: You can't access, or view, the frozen data. The data is out there on a tape, but you can't look at it, or do anything with it, without doing an IMPORT first (and creating all the DB entries and taking the tape space on primary volumes). So which one you use depends on whether realistically need to ever access the "frozen" data again. If I were doing the export, FIRST I would do a select on the backups table for "water", and dump a list of all its files into a flat file. Retain the flat file so that you at least have a "table of contents" for what is on the export tape. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Wednesday, March 16, 2005 9:24 AM To: [email protected] Subject: Re: "Freezing" a node's data - revisiting 'Need to save permanent cop y of all files currently being stored' From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Steve Schaub >Because the underlying need is to preserve all the backup >versions as they >are as of today, not just to take a snapshot of the current data. > >Richard also responded to my question, and his point is that >my step 3 would >not rebind the inactive versions to the new domain, only the >active ones. > >So, if I read this correctly, there is no way to stop backup >versions from >rolling off? My inclination, in this case, would be to create an export tape of the node(s) in question. Exporting gives the option of either preserving all copies of all data, or just the active copies. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
