Del,
It works like a charm, thanks a lot!
I've first renamed the original filespaced to a temporary name and replaced
them then by the imported filespaces. It works too of course but it might be
dangerous to foul with the original file spaces if you let the customer itself
handle it.
But with renaming the servername in the file space, you now see two Server
Notes in the TDP GUI and a restore of an imported Notes database goes directly
to the correct Notes server as they do both belong to the same TSM node.
It's really a good-to-know item. I've tested it with the TDP for SQL too, it
works there too of course.
Still got to test it for Oracle and Informix, but it will work too. Although
there is metadata of the backups in Oracle stored as well (control file or
recovery catalog), so it might be that the original filespace names should be
used.
But the procedure is rather to occur for a Notes database (lost mail) then for
an Oracle database.
best regards,
Kurt
________________________________
From: ADSM: Dist Stor Manager on behalf of Del Hoobler
Sent: Fri 18/11/2005 0:01
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] export / import TDP Notes backup
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" <ADSM-L AT VM.MARIST DOT EDU> 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
>
|
