BkOnline1
1 Nickel

ndmp recovery

Background Info:

Platform: Windows 2012R2, Tape: LT05; Networker 8.2.1; EMC VNX NAS

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

Our Celerra was decommissioned due to end of life, now we need to recover an entire file system from tape to a new VNX NAS.

I did the following:

scanner -I  \\.\Tape1

mminfo -avot  --- shows the media info including SSID for the file system we need to restore.

However, when I run the nsrndmp_recover command --(nsrndmp_recover -D5 -s networker_server -c NAS-Filer01 -S <SSID> -v off -m NAS-Filer01::Shared2/Shared2  /root_vmd_1/Shared2); it gives the following (see below) and hung for hours without any further activity on the jukebox or console.

Note that server is talking to tape library as scanner, inventory, and withdrawal CMDs works without a problem.

Console Output from nsrndmp_recover:

"NDMP Service Debug: The process id for NDMP service is 0x99b6400"

"nsrndmp_recover: Performing recovery from Non-NDMP type of device"

AUTH_MD5 connection succeeded!"

"ndmp_skiprecord: 1"

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

What am I doing wrong? Please help.

Thanks

-----Full command output----

C:\>nsrndmp_recover -D5 -s networker-server -c NAS-Filer01 -S-v off -m NAS-Filer01::/Shared02/Shared02 /root_vdm_4/Shared02


05/12/16 18:50:06.023578 mmdbd server host name: networker-server
05/12/16 18:50:06.180428 RPC Authentication: error in LookupAccountSid: No mapping between account names and security IDs was done. (Win32 error 0x534)
05/12/16 18:50:06.211709 lgto_auth: redirected to networker-server prog 390103 vers 2
05/12/16 18:50:06.227344 lgto_auth for `nsrmmdbd' succeeded
05/12/16 18:50:06.258623 Destructive Restore is specified.
05/12/16 18:50:06.258623 SSID = 2968749678, Mount point =/Shared02/Shared02, Raw device =(null)
05/12/16 18:50:06.274261 save set name: /root_vdm_4/Shared02
05/12/16 18:50:06.274261 Not a Celestra retrieval.
05/12/16 18:50:06.274261 save set name: /root_vdm_4/Shared02
05/12/16 18:50:06.305546 lgto_auth: redirected to networker-server prog 390103 vers 2
05/12/16 18:50:06.321180 lgto_auth for `nsrd' succeeded
05/12/16 18:50:06.336813 ndmp_create_connect: host(NAS-Filer01),user(ndmp),data(0000000000000000),timeout(60)
05/12/16 18:50:06.352453 socket (776) is opened for NDMP connection.
05/12/16 18:50:06.352453 ndmp_wait_connect: ndp=0000000002CEF000,timeout=60
05/12/16 18:50:06.368089 ndmp_skiprecord: 1
05/12/16 18:50:06.368089 Error in message header: No such file or directory.
05/12/16 18:50:06.368089 ndmp_skiprecord: 1
05/12/16 18:50:06.368089 dispatch NDMP_NOTIFY_CONNECTION_STATUS seqno 1
05/12/16 18:50:06.383729 ndmp_notify_connect: ndp(0000000002CEF000)
05/12/16 18:50:06.383729 Receive successful NDMP connection.
05/12/16 18:50:06.383729 ndmp_connect_open: ndp(0000000002CEF000)
05/12/16 18:50:06.399368 call NDMP_CONNECT_OPEN seqno 1
05/12/16 18:50:06.399368 ndmp_skiprecord: 0
05/12/16 18:50:06.399368 NDMP version 4 is used.
05/12/16 18:50:06.399368 ndmp_connect_auth= ndp(0000000002CEF000), host(NAS-Filer01), user (ndmp)
05/12/16 18:50:06.415003 call NDMP_CONFIG_GET_SERVER_INFO seqno 2
05/12/16 18:50:06.415003 ndmp_skiprecord: 1
05/12/16 18:50:06.415003 dispatch NDMP_LOG_MESSAGE seqno 3
05/12/16 18:50:06.430642 NDMP Service Debug: The process id for NDMP service is 0x84ff480
05/12/16 18:50:06.430642 ndmp_skiprecord: 1
05/12/16 18:50:06.430642 type supported : 1
05/12/16 18:50:06.446280 type supported : 2
05/12/16 18:50:06.446280 The NDMP user 'ndmp' has a password for host 'NAS-Filer01'.
05/12/16 18:50:06.446280 authentication method=2, host=NAS-Filer01, user=ndmp, pas=0000000002CF4E40
05/12/16 18:50:06.461917 CreateMD5Digest: ndp(0000000002CEF000)
05/12/16 18:50:06.461917 call NDMP_CONFIG_GET_AUTH_ATTR seqno 3
05/12/16 18:50:06.461917 ndmp_skiprecord: 1
05/12/16 18:50:06.477556 call NDMP_CONNECT_CLIENT_AUTH seqno 4
05/12/16 18:50:06.477556 ndmp_skiprecord: 1
05/12/16 18:50:06.477556 AUTH_MD5 connection succeeded!
05/12/16 18:50:06.493193 ndmp_connect_close
05/12/16 18:50:06.493193 call NDMP_CONNECT_CLOSE seqno 5
05/12/16 18:50:06.493193 ndmp_shutdown 42795:nsrndmp_recover: Performing recover from Non-NDMP type of device
05/12/16 18:50:06.508833 In fetchcvr_id func: fetching the details of saveset 2968749678
05/12/16 18:50:06.524474 get_vol_place:
05/12/16 18:50:06.540108 lgto_auth: redirected to networker-server prog 390103 vers 2
05/12/16 18:50:06.571390 lgto_auth for `nsrd' succeeded
05/12/16 18:50:06.587022 jukebox_device_host(), client:'', server:'', jukebox:'', device_type: ''
05/12/16 18:50:06.602657 jukebox_device_host(), no jukebox named: ''
05/12/16 18:50:06.602657 device_host(), devfull:
05/12/16 18:50:06.618295 save set name: /root_vdm_4/Shared02
05/12/16 18:50:06.633932 nsrdsa_recover started, pid 4796
05/12/16 18:50:06.633932 Reading savetime from nsrdsa_save
05/12/16 18:50:06.633932 reset the ndmp_clnt_tbl to use the ndmp_bt_clnt_tbl.
05/12/16 18:50:06.649570 task = 2
05/12/16 18:50:06.649570 The block size used as in NSR_ATTR_NDMP_BLOCK_SIZE : 61440
05/12/16 18:50:06.649570 ndmp_create_connect: host(NAS-Filer01),user(ndmp),data(0000000000CAF400),timeout(60)
05/12/16 18:50:06.665208 socket (796) is opened for NDMP connection.
05/12/16 18:50:06.680851 ndmp_wait_connect: ndp=0000000002DC0440,timeout=60
05/12/16 18:50:06.680851 ndmp_skiprecord: 1
05/12/16 18:50:06.680851 Error in message header: No such file or directory.
05/12/16 18:50:06.696488 ndmp_skiprecord: 1
05/12/16 18:50:06.696488 dispatch NDMP_NOTIFY_CONNECTION_STATUS seqno 1
05/12/16 18:50:06.712128 ndmp_notify_connect: ndp(0000000002DC0440)
05/12/16 18:50:06.712128 Receive successful NDMP connection.
05/12/16 18:50:06.727761 ndmp_connect_open: ndp(0000000002DC0440)
05/12/16 18:50:06.727761 call NDMP_CONNECT_OPEN seqno 1
05/12/16 18:50:06.727761 ndmp_skiprecord: 0
05/12/16 18:50:06.743403 NDMP version 4 is used.
05/12/16 18:50:06.743403 ndmp_connect_auth= ndp(0000000002DC0440), host(NAS-Filer01), user (ndmp)
05/12/16 18:50:06.759044 call NDMP_CONFIG_GET_SERVER_INFO seqno 2
05/12/16 18:50:06.759044 ndmp_skiprecord: 1
05/12/16 18:50:06.759044 dispatch NDMP_LOG_MESSAGE seqno 3
05/12/16 18:50:06.774679 NDMP Service Debug: The process id for NDMP service is 0x84ff480
05/12/16 18:50:06.774679 ndmp_skiprecord: 1
05/12/16 18:50:06.774679 type supported : 1
05/12/16 18:50:06.790317 type supported : 2
05/12/16 18:50:06.790317 The NDMP user 'ndmp' has a password for host 'NAS-Filer01'.
05/12/16 18:50:06.790317 authentication method=2, host=NAS-Filer01, user=ndmp, pas=0000000002DA1400
05/12/16 18:50:06.805954 CreateMD5Digest: ndp(0000000002DC0440)
05/12/16 18:50:06.805954 call NDMP_CONFIG_GET_AUTH_ATTR seqno 3
05/12/16 18:50:06.821593 ndmp_skiprecord: 1
05/12/16 18:50:06.821593 call NDMP_CONNECT_CLIENT_AUTH seqno 4
05/12/16 18:50:06.821593 ndmp_skiprecord: 1
05/12/16 18:50:06.837231 AUTH_MD5 connection succeeded!
05/12/16 18:50:06.837231 Connected to NDMP data server NAS-Filer01
05/12/16 18:50:06.852869 ndmp_negotiate_extensions(): try_bre 0, try_cae 1, try_cab 1
05/12/16 18:50:06.852869 call NDMP_CONFIG_GET_SERVER_INFO seqno 5
05/12/16 18:50:06.852869 ndmp_skiprecord: 1
05/12/16 18:50:06.868507 call NDMP_CONFIG_GET_EXT_LIST seqno 6
05/12/16 18:50:06.868507 ndmp_skiprecord: 1
05/12/16 18:50:06.884146 NDMP CAE is available
05/12/16 18:50:06.884146 call NDMP_CONFIG_SET_EXT_LIST seqno 7
05/12/16 18:50:06.884146 ndmp_skiprecord: 1
05/12/16 18:50:06.884146 NDMP data server extensions supported: cae 1, cab 0
05/12/16 18:50:06.727761 Saving ssn session 0x0000000002344A50 [0] (fd 688) to [0], ssn_max_pollfd 1
05/12/16 18:50:06.852869 RPC Authentication: error in LookupAccountSid: No mapping between account names and security IDs was done. (Win32 error 0x534)
05/12/16 18:50:06.884146 lgto_auth: redirected to networker-server prog 390103 vers 2
05/12/16 18:50:06.899788 lgto_auth for `nsrmmdbd' succeeded
05/12/16 18:50:06.899788 call NDMP_CONFIG_GET_CONNECTION_TYPE seqno 8
05/12/16 18:50:06.946698 ndmp_skiprecord: 1
05/12/16 18:50:06.946698 Data server uses IPV4 for data connection
05/12/16 18:50:06.946698 Data server uses IPV6 for data connection

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

0 Kudos
23 Replies
gautamgp
2 Iron

Re: ndmp recovery

Hi,

    You cannot user scanner to build the indexes for NDMP savesets. If the indexes are present then you can use nsrck command to rebuild the indexes.

-c option is for source client

you can do the following

Use either NetWorker recover wizard or NetWorker User GUI and select old Celerra as the Source Client and New VNX as the Destination CLient and perform a Saveset Recovery of the file system you are looking for.

0 Kudos
BkOnline1
1 Nickel

Re: ndmp recovery

Gautam, thanks for coming to my help.

However, after running the 'nsrck' then retried the nsrndmp_recover command, the result remains the same.

Also, nsrck out put shows  NAS-Filer client contains 12 records occupying 35KB.

I used scanner -I because that's what most people in other forums recommends for NDMP recovery.

NetWorker GUI is not showing anything.

Note that there is no existing Index as this is a brand new Networker server setup just for this recovery operation. The original Networker server is gone.

Please what should I do next.

0 Kudos
ble1
5 Iridium

Re: ndmp recovery

Was Celerra to VNX supported?  I know VNX in first gen was pretty much Celerra, but I'm not sure about difference they made in respect to ndmpd.  Also, if NAS-filer01 is original client, why is that mentioned in -m too (or did you call new VNX box after original Celerra so it was kind of HW upgrade?).  The log itself on NW side doesn't say much so you must check ndmpd log on VNX side.

0 Kudos
BkOnline1
1 Nickel

Re: ndmp recovery

Actually, the old NAS were Celerra NS480 and VNX7500 while the new NAS is VNX3200 --just for recovery purpose.

Basically, the 2 old NAS (ns480 & vnx7500) were decommissioned and data moved to a different platform.  VNX3200 was retained for recovery purposes.

We have recreated dummy instances of the old NAS and repopulate Networker client requirement. But I read somewhere that in order for it to work, the original clientID from the SaveSet must be used. I'm not sure how to do that.

0 Kudos
gautamgp
2 Iron

Re: ndmp recovery

yes that is correct. you would need the original Client ID of the old client. Was it not backed up to this NetWorker Server ? if backed up to another server, is that alive ?

0 Kudos
BkOnline1
1 Nickel

Re: ndmp recovery

The original Client-ID of the old client is available on tape. I got it by running 'mminfo -aVS'.

But I'm not sure how to apply it to the newly recreated dummy client on networker.

Is there a config file to edit to insert the old client-ID - as the GUI is not editable?

When I tried to recreate the client using the old client-ID, Networker complained that I cannot reuse the same client name/ID combination. It suggested instead to use a completely different (bogus) name OR leave the Client-ID field blank.

I'm not sure how that will work for recovery.

0 Kudos
Highlighted
gautamgp
2 Iron

Re: ndmp recovery

It's Good that you found the Old Client ID. You can do the following to replace the client ID,

                          1. Copy the Client ID from Globals (1of1) tab of the Old NAS client you created.

                          2. Delete the Old NAS Client from NetWorker GUI

                          3. Create another client with name dummy1 and before you click ok, put the Client ID that you noted in step 1. It will give you a warning, accept it and you old NAS client would be free and without any client ID.

                          4. Create client with the OLD NAS filer name and put the "old client ID" in the "Globals (1of1) tab. and click ok.

                          5. Run scanner and nsrck to rebuild the indexes

                          6. Try to perform the recovery.

My 2 Cents.

BkOnline1
1 Nickel

Re: ndmp recovery

I have deleted the Old NAS client from networker,

Created another client with the name "dummy1" and assigned the original Client-ID obtained from tape, but system rejected the dummy1 name as an invalid hostname.

I attempted to use other valid client names from the Old NAS, but all were produced this error: "Found NAS-Filer01, client ID: fe3f12******00004. Specify this client ID or leave the client ID blank. Otherwise the client name must first be renamed."

Basically, I can't use any valid client name as those are all present in the media index.

To complete the steps you suggested, I went ahead and setup a new valid host name as an alias to the original NAS-Filer01 client-name pointing it to the same IP as NAS-Filer01, put in the old Client-ID, did nsrck, tried recovery but still get the same problem.

**I did not do scanner again since the media info had already been done. Is my thinking right on this or do I have to repeat the scanning process?

Is there a way to move or hide the Index from Networker so as to recreate the Old client with the original client ID before reintroducing the media index into the mix?

I have gone through over a week scanning dozens of LT05 tapes into the media index and will hate to have to repeat this process.

Note: the old NAS filers and the old Networker servers are all gone for good. We are trying to recreate/restore the data from a new Networker-server to a new NAS filer.

Please any help will be highly appreciated.

0 Kudos
gautamgp
2 Iron

Re: ndmp recovery

Hi,

  You need to assign the new Client ID (for the old NAS Client) generated by NetWorker to dummy1. it will give you a warning that it is assigned to another host and would you like to rename it, accept it.

Then create the old NAS client with the Client ID that you found from the Tape. Run Scanner and try to perform the recovery.

You will also have to make sure, NetWorker server is able to resolve the old NAS client, you can put a host entry for any dummy IP.

0 Kudos