- VMware Technology Network
- :
- Cloud & SDDC
- :
- ESXi
- :
- ESXi Discussions
- :
- Installing VMware Data Protection on in ESXi 5.0 e...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Installing VMware Data Protection on in ESXi 5.0 environmnet
I am trying to install the VMware Data Protection plugin in our ESXi 5.0 environment. I have 4 ESXi 5.0 servers in a cluster and I have a vCenter server running Windows 2008 R2 which is also running Update Manager. I have the vSphere Client installed on a physical server outside of this environment from with I access vCenter. I downloaded the VMware Data Recovery iso and installed VMwareDataRecoveryPlugin.msi 2.1 on the vCenter server and everything appeared to install correctly but I do not see the Data Recovery plugin listed under plugins. I restarted the vSphere Client as well and I still do not see it. If I try to re-install the plugin I get the 'repair' or 'uninstall' option. I ran the 'repair' and restarted vCenter again, still no luck. We have Enterprise Plus licensing.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This issue may occur if a required port, such as port 902 UDP/TCP, is blocked or if there is a network issue.
To resolve this issue:
- Verify and ensure that port 902 is not blocked on the vCenter Server, or across the network.
- If the VDP appliance is deployed in a different network than vCenter Server, ensure that the routing is set up properly, including the firewall rules for all relevant ports.
You may also experience this issue if the Tomcat service is not restarted after deploying the VDP Appliance.
To resolve this issue, restart the vCenter Server Appliance and verify that the VDP plug-in is now available.
Notes:
- This issue may occur even when the VDP appliance and vCenter Server are in the same network and vCenter Server has been restarted.
- If the workaround in Unable to access VMware vCenter Support Assistant in vSphere Web Client (2042455) has been applied to your vCenter Server Appliance, you will not be able to install the VDP plugin.
Hope this helped
Best regards
Yours, Oscar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
see the administration Guide VMware Dataprotection
vSphere Data Protection Sizing
vSphere Data Protection sizing helps determine the vS
phere Data Protection appliance size and number of
appliances required based on:
Number of and type of VMs (do the VM contain file system or database data?)
Amount of data
Retention periods (daily, weekly, monthly, yearly)
Typical change rate
The following table shows examples for vSphere Data Protection sizing recommendations:
The recommendations above (note these are only guidelines) are based on the following assumptions:
The VMs primarily contain file system data. If the VMs primarily contain database data, the deduplication
rates will be lower.
70% initial deduplication rate for file system data.
99.7% daily deduplication rate for file system data.
The annual growth rate is 5%.
I
MPORTANT
If you are unsure of the size of the appliance to deploy, it is better to use a larger vSphere Data
Protection datastore. Once a appliance has been deployed, the size of the datastore cannot change.
Software Requirements
vSphere Data Protection 5.1 requires the following software:
VMware vCenter Server
vCenter Server Linux or Windows: Version 5.1
vSphere Web Client is supported on Microsoft Inte
rnet Explorer 7 and 8 or Mozilla Firefox 3.6 or
higher.
Web browsers need to be enabled with Adobe Flash Player 11.3 or higher to access the vSphere Web
Client or vSphere Data Protection functionality
Table 2-1.
Sample recommendations for vSphere Data Protection sizing
# of VMs
Data
storage
per client
Retention:
daily
Retention:
weekly
Retention:
monthly
Retention:
yearly Recommendation
2520 GB300001- 0.5 TB
25 20 GB 30 4 12 7 1- 2 TB
25 40 GB 30 4 12 7 2- 2 TB
5020 GB300001- 1 TB
50 20 GB 30 4 12 7 2- 2 TB
50 40 GB 30 4 12 7 3- 2 TB
10020 GB300001- 2 TB
100 20 GB 30 4 12 7 3- 2 TB
100 40 GB 30 4 12 7 6- 2 TB
13
Chapter 2 Installing and Configuring vSphere Data Protection
VMware ESX/ESXi (the following versions are supported)
ESX/ESXi 4.0, ESX/ESXi 4.1,ESXi 5.0, ESXi 5.1
Appliance version:
vSphere Data Protection: 5.1
System Requirements
The vSphere Data Protection appliance is available in three options:
0.5 TB
1 TB
2 TB
I
MPORTANT
Once vSphere Data Protection is deployed the size cannot be changed.
The system requirements for each option of vSphere
Data Protection are specified in the following table.
N
OTE
The additional disk space required that is above the
usable capacity of the appliance is for creating and
managing checkpoints.
vSphere Data Protection Specifications
vSphere Data Protection support
s the following specifications:
Each vSphere Data Protection appliance supports backup for up to 100 VMs
Each vCenter Server can support up to 10 vSphere Data Protection appliances
Support for 0.5 TB, 1 TB, or 2 TB of deduplication storage
Preinstallation Configuration
Prior to vSphere Data Protection installation, DNS and NTP need to be configured.
DNS Configuration
Before you deploy vSphere Data Protection, an entry needs to be added to the DNS Server for the appliance
IP address and FQDN. This DNS Server must support forward and reverse lookup.
I
MPORTANT
Failure to have DNS set up properly can cause many runtime or configuration issues.
To confirm that DNS is configured properly:
1 Open a command prompt and type the following command:
nslookup <
VDP_IP_address
> <
DNS_IP_address
>
The nslookup command will return the FQDN of the vSphere Data Protection appliance.
0.5 TB 1 TB 2 TB
Processors dedicated
to vSphere Data
Protection
Minimum four 2 GHz
processors available
to vSphere Data
Protection at all times
Minimum four 2 GHz
processors available
to vSphere Data
Protection at all times
Minimum four 2 GHz
processors available
to vSphere Data
Protection at all times
Physical memory
dedicated to vSphere
Data Protection
4 GB 4 GB 4 GB
Disk space 850 GB 1,600 GB 3,100 GB
Network connection 1 GbE connection 1 GbE connection 1 GbE connection
14
VMware, Inc.
2 Type the following command:
nslookup <
FQDN_of_VDP
> <
DNS_IP_address
>
The nslookup command will return the IP address of the vSphere Data Protection appliance.
3 If the nslookup commands returned the proper information, close the command prompt, if not resolve the
DNS configuration prior to vSphere Data Protection installation.
NTP Configuration
vSphere Data Protection uses Network Time Protocol (NTP). Before you install vSphere Data Protection, NTP
needs to be configured on the vCenter Server and the ESXi host that vSphere Data Protection will be installed
on.
See the ESXi and vCenter Server documentation for more information about configuring NTP.
User Account Configuration
Before the vCenter user account can be used with vSph
ere Data Protection, or before the SSO admin user can
be used with vSphere Data Protection, these users should be specifically added as administrator on the
vCenter root node. The following steps are used to conf
igure the vSphere Data Protection user or SSO admin
user using the vSphere Client.
1 Login to the vSphere Web Client and select
vCenter
>
Hosts and Clusters
.
2 On the left pane, click on the vCenter Server.
3Click the
Manage
tab and then the
Permissions
sub-tab.
4Click the
Add permission
icon.
5Click
Add
.
6 From the Domain drop-down select domain, server, or SYSTEM-DOMAIN.
7 Select the user that will administer vSphere Data
Protection or be the SSO admin user and then click
Add
.
8Click
OK
9 From the Assigned Role drop down select Administrator.
10 Confirm that the Propagate to child objects box is checked.
11 Click
OK
.
To Verify that user is listed under Administrators, go to
Home > Administration > Role Manager
and click the
Administrator
role. The user you just added should be listed to the right of that role.
I
MPORTANT
If the vSphere Data Protection backup user us
ing the VDP-configure UI belongs to a domain
account then it should be used in the format “SYSTEM-DOMAIN\admin” format in VDP-configure. If the
user name is entered in the format “admin@SYSTEM-DOMAIN” format then tasks related to backup job may
not show up on the Recent Running tasks.
Deploy the OVF Template
Prerequisites
The vSphere Data Protection appliance is installed on an ESXi 4.0, 4.1, 5.0, or 5.1 host.
vCenter 5.1 is required. Login to vCenter from a vSphere Web Client to deploy the OVF template.
The vSphere Data Protection appliance connects to ESXi using port 902. If there is a firewall between the
appliance and ESXi, port 902 must be open.
The VMware Client Integration Plug-in 5.1.0 needs to be installed in your browser.
15
Chapter 2 Installing and Configuring vSphere Data Protection
Procedure
1 Log in to the vSphere Web Client and select
vCenter > Datacenters.
2 On the Objects tab, click
Actions > Deploy OVF Template.
3 Select the source where the vSphere Data Protection appliance is located.
4 By default the select source dialog is set to OVF Packages. Change it to
OVA Packages
.
5 Select the app
liance and click
Open
.
6 After the appliance .ova file is selected, click
Next
.
7 Review the template details and click
Next
.
8 On the Accept EULAs screen, read
the license agreement, click
Accept
, and then click
Next
.
9 On the Select name and folder screen, enter the name for the appliance and click on folder or datacenter
you want it deployed in. Click
Next.
10 Select the host for the appliance and click
Next
.
11 Select the virtual disk format (
“Impact of Selecting Thin or Thick Provisioned Disks”
on page 47 provides
additional information) and the location of the storage for the appliance. Click
Next
.
12 Select the Destination Network for the appliance and click
Next
.
13 In the Customize template, specify the
Default Gateway
,
DNS
,
Network 1 IP Address
, and
Network 1
Netmask
. Confirm that the IP addresses are correct. Setting incorrect IP addresses in this dialog box will
require the .ova to be redeployed.
Click
Next
.
N
OTE
The vSphere Data Protection appliance does not su
pport DHCP. The appliance
requires a static IP
address.
14 On the Ready to complete screen, confirm that al
l of the deployment options are correct and click
Finish
.
vCenter deploys the vSphere Data Protection appliance. Monitor
Recent Tasks
to determine when the
deployment is complete.
vSphere Data Protection Installation and Configuration
Prerequisites
The vSphere Data Protection .ovf template (see
“Deploy the OVF Template”
on page 14) must have deployed
successfully, and you must be logged into the vCenter Server from the vSphere Web Client.
Procedure
1 Select
vCenter Home > vCenter > VMs and Templates
. Expand the vCenter tree and select the vSphere
Data Protection appliance. Right-click the appliance and select
Power On
.
2 Right-click the appliance and select
Open Console
.
3 After the installation files load, the Welcome screen
for the vSphere Data Protection menu appears. Open
a web browser and type:
ip address of VDP appliance
>:8543/vdp-configure/
4 From the VMware Login screen, enter the following:
aUser:
root
b Password:
changeme
cClick
Login
5 The Welcome screen appears. Click
Next
.
16
VMware, Inc.
6 The Network settings dialog box appears. Specify (or confirm) the following:
a IPv4 Static address
bNetmask
cGateway
d Primary DNS
eSecondary DNS
fHost name
gDomain
7Click
Next
.
8 The Time Zone dialog box appears. Select the appropriate time zone and click
Next
.
9 The vSphere Data Protection credentials dialog box a
ppears. For vSphere Data Protection credentials type
in the appliance password. This will be the universal configuration password. Specify a password that
contains the following:
Nine characters
At least one uppercase letter
At least one lowercase letter
At least one number
No special characters
10 Click
Next
.
11 The vCenter registration dialog box appears. Specify the following:
a vCenter user name (If the user belongs to a domain account then it should be entered in the format
“SYSTEM-DOMAIN\admin”.)
bvCenter password
c vCenter host name (IP address or FQDN)
dvCenter port
e SSO host name (IP address or FQDN)
f SSO port
12 Click
Test connection
.
A Connection success message will appear. If this message does not appear, troubleshoot your settings
and repeat this step until a successful message appears.
If you receive the message “Specified user either is
not a dedicated VDP user or does not have sufficient
vCenter privileges to administer VDP. Please update your user role and try again,” go to
“User Account
Configuration”
on page 14 for instructions on how to update the user role.
13 Click
OK
.
14 Click
Next
.
15 The Ready to Complete page appears. Click
Finish
.
16 A message appears that configuration is complete. Click
OK
.
Configuration of the vSphere Data Protection appliance is now complete, but you will need to return to the
vSphere Web Client and reboot the appliance. Using the vSphere Web Client, right click on the appliance and
select
Restart Guest OS
. In the Confirm Restart message, click
Yes
. The reboot can take up to 30 minutes.
17
Chapter 2 Installing and Configuring vSphere Data Protection
Post-Installation Configuration
During installation of vSphere Data Protection, when you first run the configuration utility, it runs in “install”
mode. This mode allows you to enter initial networking settings, time zone, appliance password, and vCenter
credentials. After initial installation, the VDP-configure utility runs in “maintenance” mode and displays a
different user interface.
To access VDP-configure, open a web browser and type:
ip address of VDP appliance
>:8543/vdp-configure/
The maintenance interface is used for:
Viewing Status—Allows you to see the services currently running (or currently stopped) on the appliance.
Starting and Stopping Services—Allows you to start and stop selected services on the appliance.
Collecting Logs—Allows you to download current logs from the appliance.
View or change vSphere Data Protection configuration—Allows you to view or change network settings,
configure vCenter Registration, or to view or edit system settings (timezone information and vSphere
Data Protection credentials).
Rolling Back an Appliance—Allows you to restore your appliance to an earlier known and valid state. (see
“Using Checkpoints and Rollback”
on page 42)
Upgrade—Allows you to upgrade ISO images on your vSphere Data Protection appliance.
Status Tab
The Status tab is used to view (and stop or start) vSphere Data Protection services.
Managing Status Options
The left-hand screen of the Status tab shows the status of key services in the vSphere Data Protection
appliance. The status of the following services is displayed:
Table 2-2.
Description of services running on the vSphere Data Protection appliance
Service Description
Core services These are the services that comprise the backup engine of the appliance. If these
services are disabled no backup jobs--either scheduled or “on demand”--will
run, and no restore activities can be initiated.
Management services Management services should only be stopped under the direction of technical
support.
File system services These are the services that allow backups to be mounted for file-level recovery
operations.
File level restore
services
These are the services that support the management of file level recovery
operations.
vSphere Data Protection Administration Guide
18
VMware, Inc.
The status that is displayed for these services can be:
Starting
Start Failed
Running
Stopping
Stop Failed
Stopped
Loading-getting state
Unrecoverable (Core services only)
Restoring (Management services only)
Restore Failed (Management services only)
Starting and Stopping Services
On the status screen you can start services that are stopped by clicking
Start
, or you can stop running services
by clicking
Stop
. In general, however, you should only stop running services under the direction of technical
support.
If you see that a service is stopped, you can attempt to re-start it by clicking
Start
, but in some cases, additional
troubleshooting steps are necessary for the service to work properly.
If all services are stopped, start the services in the following order:
1Core services
2 Management services
3Backup scheduler
4 Maintenance services
5 File system services
6 File level restore services
Collecting Log Files
The log file bundle is intended to facilitate sending logs of your vSphere Data Protection appliance to support
personnel. You can download all the logs from vSphere Data Protection services as a “log bundled” by clicking
Collect logs
. A “save as” dialog displays that will allow you to
download the log bundle to the file system of
the machine where your web browser is running. The log bundle is named LogBundle.zip.