recover -s orilla<\/strong>\n4181:recover: Path \/synology\/pmdg\/Documents is within othalla:\/volume1\/pmdg\n53362:recover: Cannot start session with server orilla: Client 'othalla.turbamentis.int' is not properly configured on the NetWorker Server or 'othalla.turbamentis.int'(if not a virtual host) is not in the aliases list for client 'orilla.turbamentis.int'.\n88866:nsrd: Client 'othalla.turbamentis.int' is not properly configured on the NetWorker Server\nor 'othalla.turbamentis.int'(if not a virtual host) is not in the aliases list for client 'orilla.turbamentis.int'.<\/pre>\nBasically what the recovery error is saying that NetWorker has detected the path we’re sitting on\/trying to recover from actually resides on a different host, and that host doesn’t appear to be a valid NetWorker client. Luckily, there’s a simple solution. (While the best solution might be a budget request with the home change board to buy a small Unity system, I’d just spent my remaining budget on home lab server upgrades, so I felt it best not to file that request.)<\/p>\n
In this case the NFS mount was on the NetWorker server itself, so all I had to do was to tell NetWorker I wanted to recover from the NetWorker client:<\/p>\n
root@orilla Documents]# recover -s orilla -c orilla<\/strong>\nCurrent working directory is \/synology\/pmdg\/Documents\/\nrecover> add \"Stop, Collaborate and Listen.pdf\"<\/strong>\n\/synology\/pmdg\/Documents\n1 file(s) marked for recovery\nrecover> relocate \/tmp<\/strong>\nrecover> recover<\/strong>\nRecovering 1 file from \/synology\/pmdg\/Documents\/ into \/tmp\nVolumes needed (all on-line):\n Backup.01 at Backup_01\nTotal estimated disk space needed for recover is 1532 KB.\nRequesting 1 file(s), this may take a while...\nRecover start time: Sun 08 May 2016 18:28:46 AEST\nRequesting 1 recover session(s) from server.\n129290:recover: Successfully established direct file retrieve session for save-set ID '2922310001' with adv_file volume 'Backup.01'.\n.\/Stop, Collaborate and Listen.pdf\nReceived 1 file(s) from NSR server `orilla'\nRecover completion time: Sun 08 May 2016 18:28:46 AEST\nrecover> quit<\/strong><\/pre>\nAnd that’s how simple the process is.<\/p>\n
While ideally we shouldn’t be doing this sort of backup \u2013 a double network transfer is hardly bandwidth efficient, it’s always good to keep it in your repertoire just in case<\/em> you need it.<\/p>\n","protected":false},"excerpt":{"rendered":"Backing up data from an NFS mount-point is not ideal, but sometimes we don’t have a choice. There’s a few reasons…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[6,19],"tags":[138,1194,788],"class_list":["post-5882","post","type-post","status-publish","format-standard","hentry","category-basics","category-recovery","tag-backup","tag-nfs","tag-recover"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t
![\"NFS](\"https:\/\/nsrd.info\/blog\/wp-content\/uploads\/2016\/05\/NFS-Backup.jpg\")
<\/a><\/p>\n