In a Networker Server DR event, you will need to reinstall SO and Networker. Then, you will need to re-create your backup device where boostrap reside.

For data domain devices, you can use the wizard to create the ddboost device, and you will see the folder where your bootstrap-device was pointing, but with a yellow indicator. Select that folder and select the right pool. Then, uncheck "Label after create"...

After create the ddboost device, from command line, run "scanner -m " to add the volume to media index. Then, mount it manually.

Verify you can see the bootstap savesets. If it's ok, proceed with nsrdr command.

Hope it helps

You don't need to scan and mount the volume.

Just use nsrdr (before that, check the admin guide).

You can also generate the whole procedure with EMC SolVe Desktop.

Thanks for the update..

But i am trying to do POC.

So can i perform the activities keeping the present datazone alive and running??

As i will be using the same datadomains , will build a new server .

Can it be possible or i need to make the present datazone down and do the POC ??

Thanks for the update..

But i am trying to do POC.

So can i perform the activities keeping the present datazone alive and running??

As i will be using the same datadomains , will build a new server .

Can it be possible or i need to make the present datazone down and do the POC ??

I wanted to do POC of disaster recovery in a fresh server .

But present backup-server and everything is up and running fine.

1 ) So keeping it up and running can i able to perform disaster recovery with the metadata of present backup server ?

2 ) Moreover when i will perform the activity i have to keep same hostname as present backup-server but can i keep different ip? ( if i keep same ip it will conflict with the present system)

I guess he wants to say he wants to do DR, but on some other box using existing box alive.  So, no, you need box with same name so either you do it on the same box or you shut down original box while you do DR POC.

When doin a DR the complete configuration (res) and media database (mm) is restored.

In addition you can restore all/some client file indexes (index).

Please take a look at the documentation for alle requirements - don't understand exactly what you mean with "keeping the present datazone alive".

Mkeil.

I have not used nsrdr yet, but I suppose that if you are doing a DR, you need first to re-attach your data domain device before run nsrdr... I don't think nsrdr can create your device for you

avishek87, I would not do this in the same network.

Using a different IP depends on the OS. It should work, but maybe you'll get a new hostid.

The hostname must be the same (and the configuration of it (hosts file)).

You can try this with an AFTD, and copy this AFTD to an isolated host.

The approach is the same.

mkeil: if so... where is going to find Networker the bootstrap?

I would never fiddle around with the production server.

This is what we did:

  - virtualize the BU server and restart him as isolated VM.

  - clone the bootstrap to a local (A)FTD

  - export all NW client names and create a fake table for the hosts file

  - copy the bootstrap media and the hosts file to the virtual NW server

  - install NW here and create the (A)FTD to recover from. DO NOT LABEL THE MEDIA.

  - run the DR procedure

The only missing part would be the CFIs but who really needs them ;-)

Ledugarte, thats correct. But you've not to mount the volume or run scanner on it.

ledugarte, you should always have the bootstrap report for the ssid's. If not, nsrdr will scan the volume and will use the last bootstrap save set found.

My doub was because I have done test before with ddboost devices:

1. Create ddboost device and label a volume

2. Backup something to this device

3. Delete ddboost device

4. Delete volume

5. Create ddboost device again

At this point, when I tried to mount, Networker says that the volume "XX" was not in the media database, so, I scanned the device to add in to media database. After that, I could mount it, and access the backup with no problem.

So, If nsrdr can do this procedure.. excellent.

Thanks for your explanation, mkeil

Avishek87, If you need to do a POC for DR, why don't install an isolated NW server with only a few test clients?. You can create a ddboot unit for this Test-NWserver in the same Data Domain.

I think you only need to demonstrate that DR works in a controlled environment... so, create a little new environment.