ADSM-L

Re: ANS0328E

2007-03-15 08:44:58
Subject: Re: ANS0328E
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Mar 2007 08:44:42 -0400
Fred,

That should work as well, you will just want to make sure
that all the filespaces are renamed in the same manner,
following the naming standard.

For example, assume you original filespaces are:
     SERVER1\meta\0000
     SERVER1\data\0001
     SERVER1\data\0002
     SERVER1\data\0003

Rename to:
     SERVER1-R\meta\0000
     SERVER1-R\data\0001
     SERVER1-R\data\0002
     SERVER1-R\data\0003

In other words, make sure you rename all of the filespace
in a similar pattern because the data for a single databases
is split between multiple filespaces, depending on how
many stripes you used to perform the backup.

I tried this on my test server, and it worked fine with 3 stripes.
I was able to do a restore from the renamed filespaces.
They backup appear in the GUI under the server names "SERVER1-R".

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 03/14/2007
11:38:41 PM:

> Del,
>
> I had the APAR in front of me as I started to type, but my
> symptoms appeared to be different.  But I tried the rename
> node and rneame filespace approach and it worked just fine.
> However, that requires the sysadmin to change both the
> dsm.opt and the scheduled service.  With a couple of dozen
> machines amd sysadmins saying why me?, I got to wondering if
> I couldn't get the same results if I just renamed the
> filespaces without renaming the node. Tjat doesn't require
> the intervention of the sysadmin.  I'm going to try that on a
> test machine in the morning.
>

<Prev in Thread] Current Thread [Next in Thread>