Start a Conversation

Unsolved

This post is more than 5 years old

L

1010

August 7th, 2016 09:00

how can I do the networker disaster and recovery ?

Dear buddy

    I want to make a networker server disaster and recovery test on the same platform.  If the local site would be distory inclusing network server . how can I get some part of data back from clone pool on remote site.

    To simulate it, here is :

捕获1_up1.JPG.jpg

the red line show the original client pool directory and the blude line show the clone pool directory. when it starts, the red line show pools were remove and just clone pools left.

   I also  got the latest boostrap SSID : 4221526714

saveset1_up2.JPG.jpg

I also make sure fs pool also have an clone copy

3.2K Posts

August 7th, 2016 09:00

I try to use the nsrdr with the laster SSID

nsrdr4_up7.JPG.jpg

nsrdr6_up8.JPG.jpg

nsrdr9_up9.JPG.jpg

3.2K Posts

August 7th, 2016 09:00

the old site pool information is back

mmrecovx4_up5.JPG.jpg

I was failed when I try to restore some files by using networker user

networkeruser2_restoreup6.JPG.jpg

3.2K Posts

August 7th, 2016 09:00

I also make sure fs pool also have an clone copy

saveset2_up3.JPG.jpg

then I try to use the mmrecov with the latest SSID

mmrecovx2_up4.JPG.jpg

3.2K Posts

August 7th, 2016 09:00

it shows that the restore needs fs pools's data which ready be destoried. That is not right.

It should be get the data back from the clone pool "fsclone". I dno not know why and try many times.

nsrdr_after6_up11.JPG.jpg

Please help me

Thanks

3.2K Posts

August 7th, 2016 09:00

what exciting me is  the old original networker clients information shows at new networker console

nsrdr_after1_up10.JPG.jpg

However , I can not still restore any single datafile from clone pool

networkeruser2_restoreup6.JPG.jpg

2.4K Posts

August 7th, 2016 23:00

Hello,

unfortunately my Chinese language skills are not better than my Suaheli ones ... but let me try to respond to your 2 key statements here:

  - The DR/bootstrap recovery does not also care about the file indexes - they are just not included.

    They must be recovered in an extra step later.

    I recommend to do this separately as otherwise the DR routine will be busy for a longer time than it is needed to

    recover the media db. And this is what is essential.

    The easiest way to do that is by running the nsrck command. Please read the manual for details.

    Another method would be to rebuild the file index information by scanning the appropriate save set

    (scanner -i -S ...).

  - If there are multiple instances of a save set, NW by default will always use the earliest/oldest instance for recoveries.

    If you want him to read from a clone media, there are several methods to achieve that:

    - mark the first instance as 'suspect'   :   nsrmm -o suspect -S

    - make the media with the original save set unavailable (or delete it)

    - You can also run a save set recovery from the command line and specify the cloneid along with the ssid:

         recover -S ...

Hope this will help.

3.2K Posts

August 8th, 2016 00:00

dear

I will try on my test enviroument

thanks

No Events found!

Top