<

HOW TO: Fix a broken VMware vSphere Data Protection (VDP) Appliance

Published on
38,476 Points
31,176 Views
3 Endorsements
Last Modified:
Andrew Hancock (VMware vExpert / EE Fellow)
MVE^2, Expert of the Year 2017-2011, Scribe 2016-2012, Author of the Year 2017-6,2013-2012 VMware vExpert 2018-2011 27 years of experience.
In my previous Experts Exchange Articles, most have featured Basic and Intermediate VMware and Virtualisation Topics.

If you would like to read my Basic VMware articles, they are listed at the end of this article for your convenience.

After a recent power outage this was the display on the console of the vSphere Data Protection 5.5 appliance! 


image1a.png
At first glance, it is clear that the Linux operating system has become corrupted and the Appliance is refusing to BOOT, hence the virtual machine is trying to BOOT from the network.

Options:-
 
  1. Investigate and repair the vSphere Data Protection 5.5 appliance.
  2. Deploy a new vSphere Data Protection 5.8 appliance and attach and Import the repository disks (the VM backups).
In this tutorial article I'm going to opt for Option B, and show you HOW TO: Fix a broken VMware vSphere Data Protection (VDP) Appliance, by deploying a new vSphere Data Protection 5.8 appliance and Attaching and Importing the repository disks (the VM backups).​ My work colleague has decided it will be faster for Option A! - (Check back later for the outcome!).


1. Deploying the vSphere Data Protection 5.8 appliance


The original version we were using was vSphere Data Protection 5.5, it is a good opportunity to upgrade to 5.8 that contains many bug fixes and improvements. We had checked previously that VDP 5.8 was backward compatible with the VDP 5.5 repository, so we downloaded the VMware vSphere Data Protection Appliance 5.8 OVA from VMware and Deploy the OVA.

Select Deploy OVF Template.

image2.pngBrowse to the location where the OVA has been downloaded:

image3.pngClick Next to continue.


image4.png
Ignore the EMC Corporation (Invalid certificate warning!), check the details in the Summary, and click Next to continue.

image5.pngAccept the terms of the VMware End User License Agreement (EULA), and click Next to continue.

image6a.pngEnter the Name for the Data Protection Appliance, we usually leave as the Default - vSphere Data Protection 5.8.

Click Next to continue.

image7a.png
Select the Cluster for the vSphere Data Protection resource.

Click Next to continue.

image8.pngSelect the Resource Pool for the vSphere Data Protection 5.8 appliance. 

Click Next to continue.

image9.png
Select the Storage datastore for the vSphere Data Protecxtion 5.8 appliance. 100GB of datastore is required for a thick deployment (highly recommended!). 

Click Next to continue.

image10.pngFor additional performance, I highly recommend a Thick Provisioned Eager Zeroed Disk. (This may take some additional time to provision). 

Click Next to continue.

image11.pngSelect your Production Network (the same network to which vCenter Server and your Active Directory Domain Controllers are also connected). 

Click Next to continue.

image12a.png
Enter Networking Properties for the vSphere Data Protection 5.8 appliance. These should be the same as the failed appliance. I also recommend the use of STATIC IP Address not DHCP. Do not forget to use a comma (,), in between DNS servers. Click Next to continue and Finish to start the deployment.

image13.pngimage14.pngSelect the vSphere Data Protection 5.8 appliance in the vSphere Client or vSphere Web Client.

image15a.pngand select Power On.

image16a.pngThe vSphere Data Protection 5.8 appliance has been successfully deployed and started.


2. Configuring and Attaching/Importing the backup repository to the vSphere Data Protection 5.8 appliance


Open a browser to the IP Address as specified on the console. Ignore any certificate warning messages. 

image18a.pngLogin with the default username of root, and password changeme.

image19a.pngAt the Welcome Wizard, click Next to continue.

image20a.pngEnter Network Settings for the vSphere Data Protection 5.8 Appliance. It is recommended to use a STATIC IP Address, and not a dynamic IP Address issued by a DHCP server. We are repairing a  vSphere Data Protection 5.5 Appliance, so in this tutorial we are using the same IP Address applied to the broken vSphere Data Protection 5.5 Appliance.

Click Next to continue.

image21a.pngSelect a Time zone the vSphere Data Protection 5.8 Appliance is located in. This should be the same Time zone as the vCenter Server. Click Next to continue.

image22a.png
Change the password to the VDP appliance, checking that it matches the password criteria. Click Next to continue.

image23a.pngEnter the vCenter username and password, and the vCenter Server IP Address or Host Name, and Click Test Connection. We recommend the SSO username Administrator@vSphere.local account. This is used to register the appliance with vCenter Server. You did remember your SSO Administrator password!

Click Next to continue.

image24a.pngThe VDP appliance we are replacing was a standard VDP appliance. If you are deploying or replacing a VDP Advanced applaince, select VDP Advanced and enter your License Key. Click Next to continue.

image25a.png
Up until this step, we have been deploying a new  vSphere Data Protection 5.8 Appliance. If you want to create a new standalone  vSphere Data Protection 5.8 Appliance, select Create new storage, and select the capacity, 0.5, 1.0 or 2.0TB.

We want to recover our vSphere Data Protection 5.5 Appliance backups, so we will be selecting Attach existing VDP storage. Click Next to continue.

image26a.pngBrowse to the location of the existing vSphere Data Protection 5.5 Appliance repository storage. Click Next to continue.

image27a.png
Select and add all the disks to the appliance. Click Next to continue.

image28a.pngThe disks will be verified, imported and attached to the appliance. Click Next to continue.

image29a.pngReview the minimum CPU and memory requirements for this capacity, we use a 2.0 TB appliance, and our tests have shown, that 4 vCPU and a memory of 16GB is suitable. Click Next to continue.

image30a.png
Click Next to continue.

image31a.pngClick Yes to continue to Import the storage.

image32a.png
Enter the username and password for the old vSphere Data Protection 5.5 Appliance.

image34a.pngThe VDP appliance services are started and the disks are mounted and backups imported into the Restore Job list.

image35a.pngSelect Restart Now to restart the Appliance.

It takes a few minutes for the VDP appliance to become ready as it configures itself. Time to grab a coffee; all the hard work has been completed. 

image36a.pngWhen the appliance is ready and the blue console appears, login via the Web Client.


 

3. Backup Repository Confirmation


A quick method to estbalish the backup repository has been imported successfully is to start the Web Client and select the Restore option. Selection vSphere Data Protection, in the left hand window.

image37a.png
Click Connect to connect to the vSphere Data Protection 5.8 appliance.
image38a.pngSelect Restore.

image39a.pngThe imported backups from the old vSphere Data Protection 5.5 appliance are located in REPLICATE folder. Select the REPLICATE folder, and all your old backups with the previous vSphere Data Protection 5.5 appliance, will be available to restore.

image40a.png
Congratulations, you have Fixed a broken VMware vSphere Data Protection (VDP) Appliance, by deploying a new vSphere Data Protection 5.8 appliance and attaching and Importing the repository disks (the VM backups).​

It took me less than 30 minutes, to Import the VMware vSphere Data Protection 5.8 (VDP) Appliance, attach and import the disks, wait for the configuration before I was able to start Restores!

You would still need to setup Backup Jobs and complete email notifications for full recovery.

(my work colleague never fixed that VMware vSphere Data Protection 5.5 appliance!)
 
During this series of articles VMware released VMware vSphere 5.5 and VMware vSphere Hypervisor ESXi 5.5. These articles are also applicable to VMware vSphere Hypervisor ESXi 5.0 and 5.5. For consistency, I have used VMware vSphere Hypervisor ESXi 5.1 throughout this series.

Basic VMware Articles Series: 

 
 
 
 
 
 
 
 
 
 
 
 
 


****************************************************************************
Thank you for reading my article, please leave valuable feedback. If you liked my VMware article and would like to see more Articles from me, please click the Yes button near the: Was this article helpful? at the bottom of this article just below and to the right of this information. Thank You. Do not forget if you have a question about this article or another VMware, Virtualisation, Windows Server 2012 question, why not post a Question for me and the other Experts Exchange Experts in the VMware, Virtualisation, Windows 2008, Windows 2012 Zones. I look forward to hearing from you. - Andy :- twitter @einsteinagogo
****************************************************************************
3
Enjoy this complimentary article view.

Get unlimited access to our entire library of technical procedures, guides, and tutorials written by certified industry professionals.

Get 7 days free
Click here to view the full article

Using this article for work? Experts Exchange can benefit your whole team.

Learn More
COLLABORATE WITH CERTIFIED PROFESSIONALS
Experts Exchange is a tech solutions provider where users receive personalized tech help from vetted certified professionals. These industry professionals also write and publish relevant articles on our site.
Ask questions about what you read
If you have a question about something within an article, you can receive help directly from the article author. Experts Exchange article authors are available to answer questions and further the discussion.
Learn from the best.