Start a Conversation

Unsolved

10 Posts

3419

July 12th, 2018 05:00

Folder recovery from a File server (Configured as an Image backup)

Hello everyone,

We have configured File server as Image backup. The daily backup size is around 4TB. We have a restore request where the user wants to restore one of his folder. We tried mounting the backup and it doesn't work and we got below error message:

"Latest job id:(02/07/2018 time:1:00 pm) 155854:nsrvproxy_flr: Starting Saveset Mount... 155858:nsrvproxy_flr: Mounting Saveset Id 'SSID' on vCenter 'vCenter Name' at VM 'VMName(vm-1234)' using NetWorker server 'NSR Server' for user 'username'. 162830:nsrvproxy_flr: Mount Job Id '1207229'. 167477:nsrvproxy_flr: Unable to retrieve device information for mount of clone 1527273127 of saveset 906516135: Unable to retrieve Data Domain information. 164881:nsrvproxy_flr: Operation completed with errors."


EMC support suggested us to add flrrecover user account as Management user in the NetWorker server- Data Domain properties to perform the recover successfully. Has anyone faced similar issue or upgrading the client version same to NetWorker Server version might work? Kindly help. Thanks.

Below are the details about the hosts:

NetWorker Server version - 9.2.1.2

NetWorker Client version - 9.0.1.2

FLR Version - 2.1.1-41_1

July 13th, 2018 03:00

Login to nmc > go to devices> data domain> properties > enter dd hostname , password and port no. See vmware integration for more details

10 Posts

July 16th, 2018 06:00

Hello princeaijaz,

Thanks for the reply. We have already updated the Management username, password and port number as well in the DD properties. Still we couldn't perform the recovery. Last month I have performed the restore, it worked fine. Not sure what was changed.

Error logs:

155854:nsrvproxy_flr: Starting Saveset Mount...

155858:nsrvproxy_flr: Mounting Saveset Id 'SSID' on vCenter 'vCenter.com' at VM 'VMware' using NetWorker server 'NetWorker Server' for user 'MyUserID'.

162830:nsrvproxy_flr: Mount Job Id '1248120'.

167477:nsrvproxy_flr: Unable to retrieve device information for mount of clone SSID of saveset SSID: Unable to retrieve Data Domain information.

164881:nsrvproxy_flr: Operation completed with errors.

4 Operator

 • 

1.3K Posts

July 16th, 2018 06:00

@Chan46

     This is a VM Image level backup thus having a 4TB image backups is not a very good idea according to me. Specially if quiesce is enabled and also when it comes to file level restores. Also, you mentioned about having a client agent but keep in mind this agent does not contribute in the backups.

     My recommendation to you is to remove this machine from the VM image level backup workflow and add it for agent level backups.

10 Posts

July 16th, 2018 07:00

CrazyRov 

 

Thanks for the suggestion.

 

Actually this is a File server and recently it was migrated to Image backup from Traditional as the Backup running time was going for about days utilizing more resources which is affecting the other backups. But the retention we follow here is 2 months hence the data will be purged by that time. We performed a restore last month but the backup image size was about 400 Gigs. Now this is a different file server which has huge backup image. I hope this was due to the DD credentials. EMC suggested us to change the Management username, password and ports as mentioned by princeaijaz . It didn't help though as we tried that earlier. Awaiting for update from EMC.

10 Posts

August 2nd, 2018 23:00

Hi All,

Thanks for your suggestion. Found the solution from another DECN post. Below are the steps:

Update the DD device access information to use the same name format as the DD system.  For example, if the DD system is using the short name, then the DD device access configuration should be updated to reflect the short name.  Here is an overview of the instructions to validate and update the Device access information:

1. Open the NetWorker Administration Console of the respective DataZone.

2. Select the "Devices" tab.

3. In the left pane tree-view, select "Data Domain Systems".

4. In the right pane detail view, determine if the Data Domain name is using the short name, fully qualified domain name, or the IP address.

5. In the left pane tree-view, select "Devices".

6. In the right pane detail view, right click the device and select "Modify device properties".

7. In "General" tab, ensure the "Device access information" is using the same format as the Data Domain name.

8. Select OK in the Device Properties window to save the changes.

No Events found!

Top