Mark, One caveat about using EXPORT for TDP data:
I don't remember the beginning of this thread, if you said WHY you are trying to do export/import of TDP data, or which TDP it is. Your need to be conscious of how the TDP works, and where you are going with the data, to decide whether this is going to work for you. For example, The TDP for Oracle works through the Oracle RMAN catalog. Other TDP's work other ways. You have to take into account what is expected when you do the restore. For example, if you used EXPORT to take the TSM TDP filespace to a DR site, and IMPORTed the data back to your TSM server at the DR site, that would not be sufficient to enable you to restore. You would also need to have a valid RMAN catalog for the TDP to connect to. Et. cetera. Plan, plan, plan. Test, test, test. 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 Mark Bertrand Sent: Thursday, September 02, 2004 3:10 PM To: [EMAIL PROTECTED] Subject: Re: Export Node Retention question Thanks Wanda, I am going to start using this feature immediately. Mark -----Original Message----- From: Prather, Wanda [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 1:27 PM To: [EMAIL PROTECTED] Subject: [spam] Re: Export Node Retention question More stuff: When you do an import, you import the whole node, or at least a whole filespace. Can't get any more granular than filespace. You are essentially reloading everything back into the TSM server DB and storage pools. Then you start the regular B/A client and restore whatever files you want to the client. So it's a 2-step process with IMPORT, where with a BACKUPSET you can restore directly from the backupset tape. Things that are on EITHER an EXPORT or BACKUPSET tape are not governed by expiration rules. Whatever is on the tape, stays on the tape. When you IMPORT a filespace, the data is back in the TSM DB and the inactive file copies (if you included the inactive data in the export) are again governed by expiration rules. Look at HELP IMPORT NODE, the DATES= parm. It controls whether the imported inactive files start to expire immediately or not. EXPORT/IMPORT works on filespaces, so can be used for application data bases backed up by TSM for Oracle, SQL, etc. 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 Dwight Cook Sent: Thursday, September 02, 2004 2:04 PM To: [EMAIL PROTECTED] Subject: Re: Export Node Retention question that is the beauty of export tapes.... as long as the tape is OK and as long as you have a server version that can read the export tape (probably created on an earlier version) and all the other things that go along with media type and devices to read it.... you can keep it forever! I keep sample export tape sets so when I upgrade TSM I'll be able to see if I can still import what I had exported earlier. I went up to 5.2 and could still import as far back as 3.7 (or was it 4.1) ??? anyway, I got paranoid and called back in all my long term data and imported it and re-exported it to new media on the new 5.2 server. Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 925-8045 Mark Bertrand <[EMAIL PROTECTED] UNWIRED.COM> To Sent by: "ADSM: [EMAIL PROTECTED] Dist Stor cc Manager" <[EMAIL PROTECTED] Subject .EDU> Export Node Retention question 09/02/2004 11:13 AM Please respond to "ADSM: Dist Stor Manager" I have looked in the manual and through Mark's monthly FAQ but can not find this specific information. I am looking into the Export node to tape function to retain active and inactive backup files since backupsets only grab active files. Am I correct that a file deleted from the client is considered inactive by the server. And, although it can be restored at the client by selecting inactive files, it will not be picked up by a backupset? I am not concerned with retaining the client settings, only the data. How long can I keep an Export Node to tape for? Where is this set at, gen backupset has a retention setting. How does this differ from a backupset? I know one difference is that backupset can be retained for a specified period. Also, what controls the exported node data for expirations and retention files? Can I use it to restore individual files, all the info that I have read only shows a complete import option. Can it be used for databases, I know backupsets cannot. Server: W2K TSM 5.1.6.3 Client: W2K TSM 5.1.5.15 TDP 2.2.1 Thanks, Mark Bertrand
