{"id":5454,"date":"2015-02-25T16:23:21","date_gmt":"2015-02-25T06:23:21","guid":{"rendered":"http:\/\/nsrd.info\/blog\/?p=5454"},"modified":"2018-12-11T13:01:45","modified_gmt":"2018-12-11T03:01:45","slug":"testing-and-debugging-an-emergency-restore","status":"publish","type":"post","link":"https:\/\/nsrd.info\/blog\/2015\/02\/25\/testing-and-debugging-an-emergency-restore\/","title":{"rendered":"Testing (and debugging) an emergency restore"},"content":{"rendered":"

A few days ago I had some spare time up my sleeve, and I decided to test out the Emergency Restore function in NetWorker VBA\/EBR. After all, you never want to test out emergency recovery procedures for the first time in an emergency<\/em>, so I wanted to be prepared.<\/p>\n

If you’ve not seen it, the Emergency Restore panel is accessed from your EBR appliance (https:\/\/applianceName:8580\/ebr-configure) and looks like the following:<\/p>\n

\"EBR<\/a><\/p>\n

The goal of the Emergency Restore function is simple: you have a virtual machine you urgently need to restore, but<\/em> the vCenter server is also down. Of course, in an ideal scenario, you should never need to use the Emergency Restore function, but ideal<\/em> and reality<\/em> don’t always converge with 100% overlap.<\/p>\n

In this scenario, to simulate my vCenter server being down, I went into vCenter, selected the ESX server I wanted to recover a virtual machine for (c64<\/strong>), and disconnected<\/em> from it. To all intents and purposes to the ESX server, vCenter was down \u2013 at least, enough to satisfy VBA that I really needed to use the Emergency Restore function.<\/p>\n

Once you’ve selected the VM, and the backup of the VM you want to restore, you click the Restore<\/em> button to get things underway. The first prompt looks like the following:<\/p>\n

\"EBR<\/a>(Yes, my ESX server is named after the Commodore 64. For what it’s worth, my vCenter server is c128<\/em> and a smaller ESX server I’ve got configured is plus4<\/em>.)<\/p>\n

Entering the ESX server details and login credentials, you click OK to jump through to the recovery options (including the name of the new virtual machine):<\/p>\n

\"EBR<\/a>After you fill in the new virtual machine name and choose the datastore you want to recover from, it’s as simple as clicking Restore<\/em> and the ball is rolling. Except…<\/p>\n

\"EBR<\/a><\/p>\n

After about 5 minutes, it failed, and the error I got was:<\/p>\n

Restore failed.<\/p>\n

Server could not create a restore task at this time. Please ensure your ESX host is resolvable by your DNS server. In addition, as configuration changes may take a few minutes to become effective, please try again at a later time.<\/p><\/blockquote>\n

From a cursory inspection, I couldn’t find any reference to the error on the support website, so I initially thought I must have done something wrong. Having re-read the Emergency Restore section of the VMware Integration Guide a few times, I was confident I hadn’t missed anything, so I figured the ESX server might have been taking a few minutes to be sufficiently standalone after the disconnection, and gave it a good ten or fifteen minutes before reattempting, but got the same error.<\/p>\n

So I went through and did a bit of digging on the actual EBR server itself, diving into the logs there. I eventually re-ran the recovery while tailing the EBR logs, and noticed it attempting to connect to a Data Domain system I knew was down at the time … and had my ahah!<\/em> moment.<\/p>\n

You see I’d previously backed up the virtual machine to one Data Domain, but when I needed to run some other tests, changed my configuration and started backing up the virtual infrastructure to another Data Domain. EBR needed both<\/em> online to complete the recovery, of course!<\/p>\n

Once I had the original Data Domain powered up and running, the Emergency Restore went without a single hitch, and I was pleased to see this little message:<\/p>\n

\"Successful<\/a><\/p>\n

Before too long I was seeing good progress on the restore:<\/p>\n

\"Emergency<\/a><\/p>\n

And not long after that, I saw the sort of message you always want to see in an emergency recovery:<\/p>\n

\"EBR<\/a><\/p>\n

There you have it \u2013 the Emergency Restore function tested well away from any emergency situation, and a bit of debugging while I was at it.<\/p>\n

I’m sure you’ll hope you never need to use the Emergency Restore feature within your virtual environment, but knowing it’s there \u2013 and knowing how simple the process is \u2013 might help you avoid serious problems in an emergency.<\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

A few days ago I had some spare time up my sleeve, and I decided to test out the Emergency…<\/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":[1181,16,19,1213],"tags":[1214,372,1249,788,1252,1215,1163,1216,1084,1087],"class_list":["post-5454","post","type-post","status-publish","format-standard","hentry","category-data-domain-2","category-networker","category-recovery","category-vba","tag-emergency-restore","tag-esx","tag-networker","tag-recover","tag-recovery","tag-restore","tag-vba","tag-vcenter","tag-virtualisation","tag-vmware"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t