Monday, 11 July 2022

What's New - Vembu BDR Suite 5.2

Recently I got a chance to get my hands on the latest Vembu BDR Suite 5.2 and there are pretty cool new features which have been added, The last version I worked on and dedicated a detailed blog post was v4.0 and from v4.0 to v5.2 there have been many new features that have been added to Vembu BDR 5.2 like Restoring to Microsoft Azure, BDR Suite 360 Server and Multi-tenancy.

What's New - Vembu BDR Suite 5.2

Restore to Microsoft Azure

BDRSuite now allows restoring the VMware VMs, Hyper-V VMs, Windows Servers & Windows Workstations backups to Microsoft Azure. You can initiate the restore directly from your BDRSuite Backup Server or Offsite DR Server

BDRSuite 360 Server

The BDRSuite 360 Server enables customers and service providers to monitor the backup activity of the BDRSuite Backup Servers deployed on their customer locations across multiple sites from a centralized web-based console.

Multitenancy

The multitenancy architecture of BDRSuite is redesigned to support advanced use cases of MSPs. You can now create multiple tenants and allocate one or more entities to each tenant. Every tenant will get multiple user roles to monitor and manage all the entities added under them.

Enhancements in BDRSuite v5.2

  • Improved application creation steps to add Microsoft 365 accounts to BDRSuite
  • On-demand backup scheduling for Microsoft 365 backups
  • Enhanced backup progress window for Microsoft 365 backups
  • Enhanced backup report for Microsoft 365 backups
  • Subfolder tree view for Microsoft 365 Mailbox
  • Subfolder tree view for OneDrive
  • Subfolder tree view for Group OneDrive
  • User-level backup report for Microsoft-365
  • PST Download of Microsoft 365 now supports all Microsoft Outlook versions
  • On-demand backup scheduling for Google Workspace backups.

Installation and Configuration 

The installation of Vembu BDR Suite v5.2.0 is pretty straightforward and we can opt out for a Standalone Installation (recommended where only one BDR Suite Backup Server is Deployed) or Cluster Installation (recommended for scalability and load balancing).


When Selecting the cluster installation type we further have the option to select how we want to install the main node in the cluster and the database associated with it.



Once the installation is completed login using the default username and password (admin) and start configuring Vembu BDR Suite by registering the backup server (for license management), configure Backup Repository, adding data sources for backup and configuring your backup jobs (creation and scheduling).


After registering the backup server the next task on the list is to configure the Backup Repository to store your data.



Depending upon the type of storage we can select the repository type for NAS select Simple and select Scale Out when pooling multiple storage volumes and select Disk Rotation if you want to add only one disk with a flexibility to rotate the disk with a new One when it's full.

Add Data Sources - 1) VMware vSphere (ESXi and vCenter) and Backup Proxy for VMware, 2) Add Microsoft Hyper-V (Hyper-V Cluster, Hyper-V Servers StandAlone and SMB) 3), Microsoft Windows.



Configure Backups : While selecting the basic job details we have an option to create a job without using a template wherein we want to create a backup from scratch or we have an option to create a job using an existing template.


Will be able to see the inventory list from the datasource we have added and then we can select the server we want to backup and create the backup job by adding simple job details, which disk to include / exclude , scheduling, and save the backup configuration.

** While configuring the backup job we have an option to select the individual VM's we want to backup or select the entire ESXi host which will then backup all the VM's running on that ESXi host.

Restore Backup Data / Recovery : Vembu BDR allows us to restore backup data from BDR Suite Backup Server using multiple recovery options.

Depending upon the type of scenario we have the and based on the need of the recovery there are various options to choose from, for example Instant Boot VM help us recover our virtual machine with minimal amount of downtime and ensure business continuity and disaster recovery.

Summary and Final Thoughts

Vembu BDRSuite is a comprehensive Backup and Disaster Recovery solution for virtual, physical, cloud, and SaaS applications and is designed to meet all the backup requirements of small, medium, and enterprise businesses. Vembu BDR offers Agent-less Backup for VMware, Hyper-V VM's, AWS EC2 Instances, Microsoft 365 and Google Workspace.

I think since I have started using Vembu BDR 4.x till today Vembu has came a long way with all the new feature's that has been added to the product itself and the overall enhancement's done towards day 2 support, by adding detailed documentation of product installation and configuration, white papers, knowledge bases is something which is remarkable.


Download a free trial edition of BDRSuite v5.2 here: Download Vembu BDR Suite – vembu.com

Wednesday, 1 July 2020

Back to Basics - VMware Tanzu Mission Control

Recently started spending some time learning more about VMware Tanzu Portfolio which is broadly categorised into three important aspects (Build, Run and Manage) and on each of these logical layers there are various products and services that fit's in for example VMware Tanzu Application Service falls under the category of Build (Allowing developers for creating the application/ building the code) , RUN (VMware Tanzu Kubernetes Grid - is a multi-cloud Kubernetes footprint that we can run both on-premises in vSphere (vSphere 7 with Kubernetes and vSphere 6.7 ) and also in the public cloud and finally the third logical aspect is to Manage ( Tanzu Mission Control ) for managing kubernetes and containerised applications across multiple clouds.

VMware Tanzu Portfolio Architecture Diagram

Image Source - https://tanzu.vmware.com/tanzu
Dedicated this article to talk more about Tanzu Mission Control and highlighting key points that we need to know about TMC,which falls under the category of Manage when looked into the overall VMware Tanzu Portfolio.
  • VMware Tanzu Mission Control a.k.a TMC provides a single point for teams to manage their Kubernetes clusters, TMC is available as SaaS offering and is accessible via VMware Cloud Services (https://console.cloud.vmware.com/).We can can login via enterprise federation or by using our VMware ID and once logged in we need to get in touch with VMware to get VMWare Tanzu Mission Control enabled for our org.
  • With TMC we can use API Based kubernetes service for centralising cluster lifecycle management across all environments,Clusters in TMC can be either provisioned clusters which are created in TMC and the entire lifecycle (Creation, Upgrades, Deletion) is managed by TMC or We can attach clusters (clusters provisioned outside to VMware TMC ) and TMC doesn't manage the lifecycle of those clusters.
  • Currently Amazon EC2 is the only available option under Provisioned cluster wherein we can specify Cluster Group, AWS Cloud Provider Account (Required when provisioning a cluster in public cloud), Region, SSH Keys, Kubernetes Version and VPC details when creating a new cluster.
  • When Attaching the clusters in TMC we are registering already existing clusters like AKS, EKS,GKE, or any other kubernetes cluster with VMware Tanzu Mission Control Service so as the required cluster agent extensions can be installed on those clusters and the connection can be verified.
  • The overall TMC architecture is govern via the policies which are applied to the organization > cluster groups and cascade down to the clusters, and there are majorly three types of policies in TMC 1) Access policies which helps us provide the role base access control to overall hierarchy 2) Network policies which helps us to restrict network communications defining how pods communicate with each other, by default there isn't any restriction and network policy is defined in TMC and 3) Image registry policies for restricting image registries from which images can be pulled by default TMC doesn't impose any restrictions.