Increase Productivity of Backup admins with Netbackup Self Service 8.2

IT infrastructure is rapidly increasing as a different kind of the number of applications are also increasing, each application required special skills set to manage so the number of application admins is also increasing and these the cycle has increased challenges for backup admin to keep testing backup and restore and that just to make sure that backup is valid or to meet compliance requirements. For such a task application stack holder are always highly depended on the backup admin

With the help of Netbackup self-service option dependancy on the backup, the administrator can be minimized by providing tenant access to the application stack holder to test the backup and restore it.

NetBackup Self Service 8.2 empowers users to self-serve common backup and restore requests while providing automation and control to IT. Self Service’s multi-tenant, role-based access, and dashboard features provide visibility over what’s protected and ongoing backup usage. Self Service’s request forms put complex policy management tasks safely in the h

For Enterprises Managing backups and restores for many thousands of endpoints across multiple locations and data centers is a task that typically requires a team of specialists. Effecting changes to policies can be a time consuming, an error-prone, manual activity that can leave vital resources unprotected. Enabling an intuitive self-service portal reduces complexity and errors, and automates a significant number of manual policy change activities. It also enables non-backup specialists to carry out backup and recovery-related tasks in a controlled and audited environment.

For Service providers Providing backup and restore services to multiple tenants across mixed platforms is a challenge for many service providers. Service providers can enable self-service

and automate tenant requests for backups and restores. This action puts the tenant in control and significantly reduces provisioning costs. NetBackup Self Service allows multiple tenants to access a tailored, self-service portal through which requests to back up and restore infrastructure are made intuitively. The status of their protected environments is tracked and reported. Service providers gain from automation while ensuring strict separation and security between tenant environments. Tenants gain control and visibility over what is protected.

For More information 

How to Protect Virtual Machine on Azure – Recovery Service Vault

My All-time favorite topic is data protection and I always love to spend my free time learning new data protection method from the different solution provider, here I have tried to configure the virtual machine backup with azure and I must say Microsoft engineer has really made the things very simple

A Recovery Services vault is a storage entity in Azure that houses data. The data is typically copies of data, or configuration information for virtual machines (VMs), workloads, servers, or workstations. we can use Recovery Services vaults to hold backup data for various Azure services such as IaaS VMs (Linux or Windows) and Azure SQL databases. Recovery Services vaults support System Center DPM, Windows Server, Azure Backup Server, and more. Recovery Services vaults make it easy to organize your backup data, while minimizing management overhead.

Within an Azure subscription, we can create up to 500 Recovery Services vaults per subscription per region.

Here are the some simple steps to configure the backup.


  • first we need to create Recovery service vault from the option available from the console


  • From the service vault creation window, it is mandatory to provide the details such as Subscription resource group, vault name, and region,

Virtual machine from the same region of recovery service vault can only be backup, we will not be able to back up if the Recovery service vault region is east Europe and virtual machine running on west Europe both has to be in same region


  • From the next windows we have chance to review applied settings


  • once the Recovery vault is create select go to resources


  • From the following windows, we have the option to select the backup method in my case I am trying to back up from azure virtual machine however we can also backup from azure stack and on-premise


  • Select the backup policy, or else we can also create new policy based on required RPO & RTO


  • select the VMs to backup


  • Select enable backup to active the backup policy


  • Backup jobs can be monitor from job monitor tab


Thanks to visit my Blogs ,


Nutanix Files (AFS) – Graceful Shutdown and Start-up

There can be a situation where you have to either shutdown the entire AOS cluster hosting Nutanix Files, or just the Nutanix Files (AFS) cluster.

Gracefully shutdown Nutanix Files and Nutanix AOS Cluster

  • Verify that no snapshot or replication is taking place.
  • Power off all guest VMs on the cluster, leaving only FSVMs (File Server VMs) and CVMs (Controller VMs) powered on.

Gracefully Shut down a Nutanix FILES (FSVMs) Cluster


STEP – 1 : Stopping all File Services

1.1 : For AOS 5.0.x – 5.5.x:

minerva stop fsvm

1.2 : FOR AOS 5.6 and later:

From any CVM, enter the “afs” command prompt:

nutanix@cvm: afs

<afs> infra.stop *

​The infra.stop * command will stop Nutanix Files services and power off the FSVMs for all File Servers.

Gracefully Shutdown the AOS Cluster

Once only the CVMs remain powered on, from any CVM, run:

STEP 1 : Gracefully STOP an AOS Cluster:

nutanix@cvm: cluster stop

STEP 2 : Gracefully shutdown the CVMs in an AOS Cluster:

Once the cluster is stopped, we can then shutdown the CVMs itself via:

nutanix@cvm: sudo shutdown -h now

You can now Power-off the hosts to conduct maintenance or physical hardware re-location.


Bringing it back online – AOS and Nutanix Files Cluster


In order to bring back online a AOS Cluster and Nutanix Files Cluster, we will first:

  1. Power ON the physical hosts
  2. Ensure all CVMs are UP/Online (CVMs auto-start when hosts are up)
  3. Ensure all physical network connections are in-place and green

STEP – 1 : Powering up a Nutanix AOS Cluster

Once all CVMs are up, ssh login to a CVM with user ‘nutanix’ and run:

cluster start


STEP – 2 : Verify AOS Cluster Services:

nutanix@cvm: cluster status (make sure all services are up)

STEP – 3 : Powering UP Nutanix Files (AFS) Cluster


3.1 – Starting File Services on AOS 5.0.x – 5.5.x

minerva -a start

3.2 – Starting File Services on AOS 5.6 and later:

Login to a CVM and enter the afs prompt by typing:

nutanix@cvm: afs

Once inside the afs prompt

<afs> infra.start *

The start command will power on the FSVMs for all File Servers and start Nutanix Files services.
To read further on gracefully shutting down a Nutanix AOS and Nutanix Files Cluster, please refer to the Nutanix Portal Documentation:

Nutanix Files – Graceful Shutdown of a Nutanix Cluster

Nutanix Files 3.5 Guide 

How to delete Prism Central VM-next.Nutanix

Sometimes it is necessary to delete and re-deploy Prism Central (PC) VM. Instances may include errors that occurred during PC deployment or when PC version deployed is outside of Software Product Interoperability matrix.

Starting with version 5.5, Prism Central becomes the primary management plane and houses features like SSP, Calm, RBAC, Microsegmentation, etc. Therefore it is important to follow recommended process when deleting PC VM:

  1. Identify the cluster on which the Prism Central VM that you wish to delete has been deployed. Copy the Prism Central VM name from this cluster.
  2. Unregister and clean up all clusters registered to Prism Central.
  3. Check if all clusters have been unregistered from Prism Central by executing the following command from any CVM in each cluster.
  4. Delete the Prism Central VM.
  5. Check if the Prism Central VM has been deleted by logging into the cluster’s Prism Element UI and browsing the VM section.


For detailed instruction please refer to How to delete a Prism Central VM.

The article also references KB-4944 Unregister from Prism Central and cleanup | Force unregister PE from PC after PC is deleted

Software Product Interoperability

Netbackup 8.2 / 3.2 is now GA

NetBackup 8.2 is now GA and have added new feature and enhancement toward unified user experience

  1. its expanded capabilities with Agentless Everywhere for VMware, SQL Availability Groups, RedHat KVM, OpenStack, Nutanix, and MongoDB, and more
  2. Enhanced CloudCatalyst performance and added support for additional cloud storage like AWS Glacier and Snowball targets
  3. More checks has added to Appliance Upgrade Readiness Analyzer (AURA) tool for error free upgrade
  4. Instant Access is now supported on both the older 5230 model and the NetBackup Virtual Appliance
  5. The CloudCatalyst configuration has been moved to the NetBackup user interface to simplify & streamline the configuration experience
  6. Automated policy to backup and protects the KMS Database