Kurt, How about just renaming the imported filespaces to something like this:
RENAME FILESPACE SERVER.DOMDBS1 SERVERIMP.DOMDBS RENAME FILESPACE SERVER.DOMLOGS1 SERVERIMP.DOMLOGS Give this a try. For SQL Server... it is slightly more complicated, because there could be more filespaces involved.. but something similar could be followed if it works. I am not sure about Oracle. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 11/17/2005 04:21:56 PM: > Del, > > Thanks for the update, I didn't know that the TDP sticks to the > original filespace names. > > The global idea was to have the management classes defined so that a > restore until one month ago was possible. And then once a month an > export to allow restores further in time. > > An extra full backup could be taken under another nodename with a > longer retention, but some backups have to go over rather slow > WAN's, so a double full backup would pose problems too. > > The mergefilespace option would probably add a version that would > expire immediately (would an immediate restore prior to an expire > inventory be possible if n versions should be kept for an active > file and this is the n+1 version?). And after the restore, the > imported data should be deleted again to save disk space. > > But if I use the command 'rename filespace' to give the actual > filespaces a temporary name and the imported filespaces are renamed > to SERVER.DOMDBS and SERVER.DOMLOGS, then the restore from the TDP > GUI would work. Gonna test this tomorrow, unless the idea would be > shot by then. > > Is the same true for the TDP of Oracle / Informix and MS SQL? > > best regards, > Kurt >
