Tag Archives: Data Protection

Vembu Install Guide – Part 2 vSphere Configuration

Following on from the previous installation of Vembu Backup Server v3.7 on Windows Server 2016; this post will walk through the configuration steps to add a vCenter target and configure virtual machine backup jobs.

Vembu Install Guide – Part 1 Installation

Vembu Install Guide – Part 2 vSphere Configuration

Initial Configuration

On the Windows server running Vembu Backup Server browse to https://localhost:6061 and login with the default username and password of admin admin. Alternatively from a remote machine browse to the FQDN or IP address of the Vembu Backup Server over port 6061. If you changed the web UI port or default credentials during setup then update accordingly.


The Vembu BDR dashboard will load.


When logging in you will notice the license notification in the bottom left hand corner. The full feature set is available for 30 days, after which you can continue with Vembu BDR Suite free edition. To purchase licenses you can register the server from the Management tab, under Server Management, and Server Registration.

Email notifications can also be configured from the Management tab, under Settings, and Email Settings.

If you didn’t configure a backup repository during installation then we’ll need to do this now before continuing. Select the Management tab, from the drop down menu and click Storage Management.

Select the appropriate location for the backup repository, this can be a local disk:


Or a SAN / NAS hosted network share:


Configuring vSphere Backups

Once a valid storage repository is in place we can begin configuring backup jobs. First let’s add the vCenter: from the Backup tab select VMware vSphere. Click Add VMware vSphere Server and enter the vCenter FQDN or IP address, and credentials. Click Save.


Added vCenter Servers can be viewed in the List VMware Servers page.


Setup a backup job by clicking Backup next to the relevant vCenter Server, the backup wizard loads.

Select the clusters, hosts or VMs to backup. You can exclude VMs or individual disks here also. When you’re ready, click Next.


Set the backup schedule to your own preferences, and click Next.


Configure the appropriate retention policy and click Next.


Application aware backups can be configured here, select any servers that require application consistent snapshots, such as Exchange, SQL, etc. and select whether transaction logs should be truncated post backup. You need to enter valid guest OS credentials, create a service account for this purpose if one doesn’t already exist.


Review the settings, and click Next. You can run the backup straight away by ticking the option if required.


Click Ok to confirm creation of the new backup job, you will now see this in the list of backup jobs.


If you opted to run the backup immediately you will see the backup progress page.


You can run the backup at any time from the List all Backups page, and also edit or delete backup jobs.



Vembu Install Guide – Part 1 Installation

Vembu Install Guide – Part 2 vSphere Configuration


Vembu Install Guide – Part 1 Installation

This post will walk through the installation of Vembu BDR Server v3.7 on Windows Server 2016, in preparation for backing up a VMware environment. At the time of writing the most recent version is v3.7.0 Update 1, which provides compatibility with vSphere 6.5.

Vembu Install Guide – Part 1 Installation

Vembu Install Guide – Part 2 vSphere Configuration

About Vembu BDR Suite

Vembu BDR Suite consists of a number of key products and is available in both free and paid for versions. Vembu free edition offers agentless VMware and Hyper-V backup and restore for virtual environments, and disk image backups for physical Windows machines. In both cases Vembu backups take application-aware snapshots using application-specific VSS writers to ensure clean and consistent recovery of Exchange, SQL Server, Active Directory, and Sharepoint. Transaction log files are truncated after each successful backup.

The free Vembu BDR Suite is sufficient for protecting servers in test or production environments for small to medium businesses. The free version includes a 30 day trial of advanced features such as replication, near Continuous Data Protection (CDP) providing RTO & RPO of under 15 minutes, Changed Block Tracking (CBT), and offsite backup features; offsite DR replication, cloud DR replication, WAN acceleration, distributed Vembu agents, bandwidth throttling, and more. After the 30 day trial ends you can continue to backup unlimited machines forever using the features of the free suite. For a full list see the feature comparison page.


Both the free and licensed versions of Vembu BDR Suite can be used to backup unlimited virtual machines forever. When planning an installation consider the following:

  • Vembu BDR Server runs only on 64 bit operating systems: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2. Windows 10 is also supported but it is advisable to use only for evaluation purposes.
  • The Vembu BDR Backup Server should have a minimum of 8 GB RAM (16 GB recommended) and 4 vCPU (8 vCPU recommended). The NIC(s) should be 1 Gbps or above.
  • Storage repository for backups can be either a local drive, or any SAN / NAS device connected using CIFS (SMB) or NFS share. When calculating storage also consider adding 10% for storage of metadata.
  • The backup port used is 32004.
  • There are no external database requirements since an embedded Postgres SQL database is used.
  • To save money on Windows licensing you can also deploy the Vembu BDR backup server as a VMware/Hyper-V virtual appliance, this can be obtained from vembu-sales@vembu.com.
  • Vembu 3.7.0 U1 is compatible with versions 4.x of vSphere, right the way through to 6.5, and Hyper-V versions 2008 R2 through to 2016.
  • The Vembu management interface can be accessed using IE v11 and above, Firefox v28 and above, or Chrome v34 and above. Ports 6060 and 6061 should be open.
  • Vembu BDR Suite can be downloaded here and the release notes for v3.7.0 Update 1 here. Ensure you read through the current known limitations in the release notes.

Additional Links

The great thing about Vembu products is the accessibility of information. All the data needed to determine whether Vembu solutions are right for you is available on their website; full product and solution write ups, demos, webinars, datasheets, documentation, knowledgebase, community forum and support, right the way through to visibility on pricing, resellers / distributors and service providers.

Vembu BDR Suite PricingVembu Webinars and DemosVembu Technical DocumentsVembu Product DatasheetsVembu Technology Blog.

Installation Process

Download the Vembu BDR Server here. The installer is the same for both the paid and free versions, you can apply a license for the advanced features or continue to use the unlicensed features at no cost.

Copy the VembuBDRSetup executable to your Windows server, right click and select Run as Administrator, accept any Windows/UAC prompts. The installation wizard will load, click Next.


Accept the end user license agreement and click Next.


Review the configuration settings, if you’re going for a simple, straight forward setup then click Install. If you want to customize any of the settings then select Let me customize the configurations.


The configurations that can be customized are the PostgreSQL Server configuration parameters; such as instance name, installation location, and database storage location (the default installation location for both PostgreSQL and Vembu BDR Backup Server is C:\Program Files).


The storage repository for backups can be changed, this needs to either be a local drive or any SAN / NAS device connected using CIFS (SMB) or NFS share.


If required the default web server port and web console username and password can also be updated.


Accept any new settings and click Install.


Vembu BDR Backup Server will now be installed.


Once complete click Finish.


Providing you left the check boxes on the completion page selected the web console will auto load. Log in with the default username and password of admin admin, unless you changed this during setup.


Select the required time zone and click Save.


Enter a unique ID for this particular instance of Vembu BDR and click Update.


The Vembu BDR dashboard will load.


Vembu is now installed and we can go ahead and configure our backup targets. In the next post we’ll add a license, a SAN storage repository, and a vCenter, then start backing up some virtual machines.


Vembu Install Guide – Part 1 Installation

Vembu Install Guide – Part 2 vSphere Configuration

vSphere Data Protection Install Guide

This post will walk through the installation of vSphere Data Protection (VDP) 6.1.3; a vSphere integrated backup and recovery solution. Data Protection is based on EMC Avamar deduplication backup and recovery software, and can also integrate with EMC Data Domain for scalability. In addition to full virtual machine backups vSphere Data Protection offers file level restores, application level backup and restores,  backup data replication to remote sites, and reporting. An emergency host level restore feature has been added for situations where the vCenter Server or web interface is unavailable. For more information on the features available to vSphere Data Protection 6.1.x see this technical overview.

Design Considerations

  • vSphere Data Protection is deployed as an OVA template.
  • The virtual appliance can be deployed with the following configurations:
    • 0.5 TB backup datastore, 873 GB disk space, 4 vCPU, 4 GB memory.
    • 1 TB backup datastore, 1600 GB disk space, 4 vCPU, 4 GB memory.
    • 2 TB backup datastore, 3 TB disk space, 4 vCPU, 4 GB memory.
    • 4 TB backup datastore, 6 TB disk space, 4 vCPU, 8 GB memory.
    • 6 TB backup datastore, 9 TB disk space, 4 vCPU, 10 GB memory.
    • 8 TB backup datastore, 12 TB disk space, 4 vCPU, 12 GB memory.
  • The backup datastore can be extended after deployment, up to the maximum size of 8 TB per appliance.
  • For assistance with sizing the appliance for your environment see pages 27 and 28 of the vSphere Data Protection Administratrion Guide.
  • To avoid block size limitations the appliance should be deployed to VMFS5 or later.
  • Each vCenter Server supports up to 20 vSphere Data Protection appliances.
  • Each vSphere Data Protection appliance supports up to 400 virtual machines however…
  • The amount of virtual machines each appliance typically supports is 150 – 200. This is dependent on factors such as the virtual machine size, the amount of changed data, and the date retention period.
  • By default Data Protection can backup machines utilising SAN, NAS, or VSAN datastores.
  • For hosts using DAS, or hosts in remote locations, external proxies can be deployed as virtual appliances from the VDP UI.
  • Up to 8 proxies can be deployed per vSphere Data Protection appliance.
  • Review the vSphere Data Protection 6.1.x Release Notes and vSphere Data Protection Administratrion Guide.


  • The table below lists the supported vCenter Server versions for 6.1 variations of vSphere Data Protection.


  • If you are using vCenter 5.5 U3 with Data Protection 6.1, 6.1.1, or 6.1.2, see this kb.
  • All variations of Data Protection 6.1.x support ESXi 5.1 through to ESXi 6.0 U2. For ESXi 6.5 version 6.1.3 of Data Protection should be used.
  • To check compatibility with any other VMware products see the Product Interoperability Matrix.
  • Editions of vSphere Essentials Plus and above (or vSphere with Operations Management / vCloud Suite) include licensing for vSphere Data Protection.
  • FQDN resolution must be in place. A forward and reverse DNS entry needs manually adding.
  • A static IP address is required for the VDP appliance and any additional proxy appliances.
  • The vCenter Server and attached ESXi hosts must be configured with an NTP server. The VDP appliance pulls the time configuration from vSphere.
  • The following disk types are unsupported: independent, RDM independent (virtual compatibility mode), and RDM physical compatibility mode.
  • Each virtual machine to be backed up should be running VMware Tools and hardware v7 or above.

Install VDP

Download the VMware vSphere Data Protection OVA here. The ISO is used for upgrades. Browse to the vSphere web client and right click the cluster where the virtual appliance will reside. Click Deploy OVF Template. Browse to the downloaded OVA file and click Next.


Review the OVF template details and click Next.


Accept the EULA and click Next.


Enter a name for the virtual appliance and select a location, click Next.


Select the datastore for the virtual appliance and click Next. Select the VM network to use and click Next.


Enter the network settings for the virtual appliance. Review the summary page, tick the Power on after deployment box and click Finish.


Configure VDP

DNS values for forward and reverse lookup must be in place for the configuration wizard. Manually add a DNS host record for the IP address of the virtual appliance and the desired host name and domain.

After deployment browse to https:\\:8543/vdp-configure, where is the IP address or FQDN of the vSphere Data Protection appliance. Log in with the root default password changeme.


The configuration wizard will load, click Next.


Enter a host name and domain for the appliance. The network settings are auto- populated, click Next. If DNS forward and reverse lookup values are not in place the wizard will fail at this point.


Select a time zone and click Next.


Configure a new root password for the virtual appliance and click Next.


Enter the vCenter Server details and click Test Connection. If successful click Next.


Select the size of the datastore to create for backup data, click Next.


Select the storage to use and the provisioning type, click Next. Accept the default CPU and memory allocations and click Next.


Select or leave the Customer Experience Improvement Program check box and click Next.


Select whether or not to run performance analysis on the storage configuration. The performance analysis tests the read, write, and seek speeds of the underlying storage. Once ready click Next to apply the changes. Click Yes to confirm. The virtual appliance will now be reconfigured and rebooted.


This process can take around 15 minutes depending on your infrastructure. When the appliance is back online a VDP icon will be added to the home page of the vSphere web client, default alarms are also added.


To view and change settings related to the virtual appliance you can log back into https:\\:8543/vdp-configure, where is the IP address or FQDN of the vSphere Data Protection appliance.


The installation is now complete and you can begin scheduling backup jobs using the Create Backup Job wizard.