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 -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"
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.
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.
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.
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.
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 ?
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.
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.
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.
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.
gautamgp
1 Rookie
•
226 Posts
2315
0
Posted May 18th, 2016 19:00
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.