NetBackup domain and vSphere domain

2. The resemblance is uncanny

When you took your first class for VMware vSphere, you would have noticed that VMware platform is based on three-tier architecture. It is quite easy to learn NetBackup if you are already a certified VMware professional.

You have virtual machines; this is the life blood of the organization. This is where your applications are running.  Multiple virtual machines are hosted by ESXi hosts. Multiple ESXi hosts are managed a vCenter server. That is how the scalability is achieved and vSphere became an enterprise platform.

NetBackup pioneered this model more than a decade ago. It features three tiers. At the lowest level is NetBackup clients. Multiple clients may be protected using a NetBackup media server.  Multiple media servers are managed by a NetBackup master server.

NetBackup and vSphere: Architecture
NetBackup and vSphere: Architecture

NetBackup clients can be a physical systems (a Windows PC, a Mac, a UNIX system hosting an Oracle database etc.) sending backup streams to a media server. In a virtual environment, it can be a virtual machine or a physical system that can read data from VMware datastore. It is important to remember that your production virtual machines themselves do not stream backups, that operation is offloaded to a dedicated VM or a physical system. This system is known as VMware backup host. Thus NetBackup is providing agent-less backups for your virtual machines.

Now let us look at the media server. In terms of our architectural comparison, we compared a media server in NetBackup domain to an ESXi host in vSphere domain. Just like ESXi hosts have storage connected for serving virtual machines, media server has storage attached to it for serving backup clients. The storage connected used by ESX hosts is referred to as data store or primary storage.  It is on primary storage that your production virtual machines and applications live. The storage attached to media servers are known as secondary storage or backup storage. It is used for the purpose of storing the backups.

You know that ESXi systems can support multiple kinds of data stores. You have NFS data stores and VMFS data stores. You also know that VMFS can be on direct attached, Fibre Channel SAN attached or iSCSI SAN attached. Similarly media server can have secondary storage attached to it. There could be plain disk storage, capacity managed disk storage, deduplicated disk storage or even a tape library.  The disk storage may be directly mounted on media server or being served from dedicated storage server.

We know that multiple ESXi hosts can share the same data store. Similarly it is multiple media servers can share a storage server or tape library. Just like how VMware DRS can start VMs based on where least ESXi hosts, backup jobs are load balanced across media servers.

We know that vCenter is really the center of vSphere. vCenter is the management control station. Similarly, NetBackup master server is the center of NetBackup. Just like vCenter, master server hosts a central database and manages data protection for the entire backup environment.

In a vSphere domain ESXi (the ESXi hypervisor) and VMs coexist in a physical system. In NetBackup domain the media server and clients are almost always on different physical systems. There are some exceptions to this rule.

vCenter is generally a separate system for enterprise environments. For smaller environments, it could also be a VM on and ESXi host. Similarly, NetBackup master server is a separate system for large environments. It may also coexist with a media server.

It is worth mentioning that NetBackup also has a fourth tier. It is called NetBackup OpsCenter. NetBackup OpsCenter can do management and reporting on a number of NetBackup domains that are served by different master servers. This layer makes NetBackup even better scalability. You may have data centers across the globe. A NetBackup master server at each data center managers its own media servers that are protecting the clients. All these master servers report into OpsCenter. This is it like a super control and command center. By logging into this central OpsCenter dashboard, you can get a single-pane-of-glass view for the entire data protection infrastructure.

For a very crude comparison, think about vCenter Server Heartbeat that lets you manage multiple vCenter instances. OpsCenter is like vCenter heartbeat but much superior. OpsCenter is a standalone system with its own database for manages, monitor and report tasks. vCenter Heartbeat is more or less a glue that makes it possible to view all instances of vCenter from a single vSphere client GUI.

That is it for today! We will move on to details on each of these three layers in subsequent blogs.

Next: NetBackup Master Server vs. VMware vCenter Server

Back to NetBackup 101 for VMware Professionals main page


From VMware Administrator to Cloud Pilot

1. Your journey to the cloud

Are you an expert in virtualization? What is your title? VMware System Administrator, Virtualization Specialist, VM Administrator, vSphere guru……

Congratulations! You are on your way to Cloud. Sean Regan wrote a blog on Cloud Pilots. As organizations are getting into virtualizing business critical applications, the six figure income (or whatever is the equivalent) has to come from something bigger that managing a bunch of ESX hosts.

Why? Well, smaller environments are less likely host their own virtual infrastructure. Their computing requirements are served from Cloud. So they need you at Cloud providers’ data centers. Larger businesses may have their own private clouds. Whether you are a technology savvy college grad looking to start a career in IT or an expert in managing virtual machine environments, it will be a huge plus to add a few additional skills in your arsenal to get ready for the future.

How do we get there? If we have learned something from the recent economic downturn, the keyword is relevance. More and more organizations are looking for multi-skilled professionals. As a VMware professional you have already gotten some level of exposure to storage. That is one area where you could sharpen the saw. Another area you must have exposure is data protection. This is really the golden nugget for the future.

Data Protection is a huge responsibility and hence comes with higher compensation benefits. Now that cloud providers (whether serving external or internal customers) are hosting everything for mission critical applications, their cloud infrastructure must meet the RPO and RTO requirements which was traditionally the role of a backup administrator.

If you are a vSphere professional for a small environment, you may be already using some point products to protect your virtual machine data. VMware Data Recovery (vDR), vRanger, Veeam etc. are a few examples. Now imagine your next role as a Cloud Pilot for a large organization.

  • The infrastructure is no more a bunch of ESX hosts managed by a vCenter server
  • Now you are not an exclusive virtual machine administrator, you are in charge of protecting assets on various platforms required to power the Cloud
  • You need end to end visibility into the entire infrastructure, you must see both physical and virtual layers powering the Cloud
  • Data protection is no more copying a bunch of VMDK files to disk storage. Enter the world of storage level replication, continuous data protection, long term archival and more

This is what inspired me to write a series of blogs for virtual machine administrators. It is easy to learn lower end solutions like the ones mentioned earlier as those are designed for very small environments. Those solutions cannot grow the Cloud Pilot in you. An enterprise data protection platform like NetBackup may look a bit intimidating at the first sight, but imagine your worth and relevance if you can be the one capable of managing the cloud. So here is my attempt to bring you the concepts of NetBackup in the language you are already familiar.

Next: NetBackup domain vs. vSphere domain

Back to NetBackup 101 for VMware Professionals main page