One problem I ran into at a client site was with the transaction logs. You can set up different nodenames to backup the once weekly/monthly full backups, but a portion of that backup is a log file. When you do the restore, you do the physical first..the full database and then replay the logs. But the daily logs are under a different nodename to TSM than the partial log that is under the weekly/monthly nodename. So the logical restore will fail.
You should also not run the onmsync (?) utility! This will sync the sysutils file with the entries in TSM. If you run this under the daily nodename, then the weekly/monthly backups will be purged from the sysutils table. And I don't believe you can restore if you don't have an entry in the sysutils table. Just my $.02. Bill Boyer "Some days you're the bug, some days you're the windshield" - ?? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Marek Slusarski Sent: Tuesday, May 24, 2005 9:25 AM To: ADSM-L@VM.MARIST.EDU Subject: archive in TDP for DBS I'm currently running daily backups keeping 10 versions of Informix database (two weeks/daily backups). However, the Informix admin requires a one daily backups to be saved for a specified period of time (4 weeks ) and one monthly to be saved for one year. The keyproblem is, that TDP for Informix ( not only for Informix) has no archive-feature (no archive copy group). I'm thinking about registering a second node for a second backup of the databases on Informix but I know that Informix traces its backups by "emergency boot file" and inserts into sysutils database so I don't know if after backing up Informix database by two or three different nodes I still be able to restore. Does anyone have anything like this implemented? Thanks! Marek
