Unsolved
1 Message
0
1166
November 9th, 2020 01:00
Unable to mount DD Device while Moving Networker 9.1 Server Software from one Physical Server to Another Physical Server
Hello Friends,
In my Organization, We are using EMC Networker 9.1.1.4 for backup operations on Windows Server 2008 R2.
As I know that this Version of Networker has already expired and we have to Upgrade it to the latest version of Networker i.e. 19.x.
But to Upgrade from 9.1 to 19.x I have to move this software from one physical server to Another Physical server. Because the existing server is having an old OS (i.e. Win 2008) and so I want to move this software to Win 2016 (i.e. Completely Different Physical Server) having same hostname and IP address.
Now to achieve this, I followed NSRDR methodology which I think is the best and easy way. Below are the steps (Shortly) which I followed / Planned.
1. Downtime
2. Bootstrap Backup (Record the details)
3. Power off existing server
4. Start New Server with same IP and Hostname as Old Server
5. Install Networker Server Software 9.1.1.4 (Same Version)
6. Attach DD - Create a DD Device and Provide same access info on which Bootstrap is located.
7. Once bootstrap is accessible run NSRDR to recover the database.
8. run scanner on all other devices.
9. License Information.
Now while attaching the Data Domain (Pt. No. 6) DD information is reflecting correctly even while configuring the Device, The wizard shows the existing DD Device with Yellow Exclamatory mark, So the Wizard gets completed and device gets added successfully. But after that when I tried to scan and mount the device it gives an error "Cancelled by the Server, Operation timed out."
After that I referred the community post which says that no need to mount the device manually, instead simply run the nsrdr command and follow the instruction.
But that too did not worked. During the nsrdr process, where it scan the device and mount it and at that point it gives error.
Please Help...
bingo.1
2.4K Posts
0
November 9th, 2020 08:00
I personally would never recover the bootstrap from a DD boost device. Why? - because it potentially could create problems, especially with forgotten access information. But I admit this is a very personal decision.
What I have done for years is to daily clone the current bootstrap to a locally attached file type device (FTD) where you can easily monitor its content. You better relabel the volume at the beginning of the process to ensure that it will only hold a single bootstrap. Make sure that you run a full bootstrap backup as the last backup on the old server so that the bootstrap (clone) is up-to-date and will contain all save sets in the media index.
Then copy this directory to the new server (most likely to the same directory), create the appropriate FTD and run the nsrdr command on this device. It will work without problems.
After you recovered the bootstrap, you need to scan the other disk devices device paths or you set these volumes to 'appendable' and mount them.
Scanner and mount (nsrmm) are 2 different commands - you cannot combine them. So please verify exactly when the issue arises. To get more information, add more verbosity to these commands and pipe the output to an appropriate text file.
Also use nsr_render_log and verify what' in the daemon.raw file.