Skip to main content

Configure OpenStack virtual machines

Make sure to review all prerequisites before you start configuring your virtual machines (VMs) for backup.

Prerequisites for Configuring OpenStack VMs

  • Decide whether to use the default group or create a new administrative group. Administrative groups logically group servers and VMs based on attributes such as location, OS, or workload type.

  • Decide whether to use the default backup policy or create a customized policy defining backup schedules, retention periods, and bandwidth rules.

  • Ensure at least one OpenStack backup proxy VM is deployed and registered via Keystone credentials (Username, Password, Project Name, Domain, Identity API URL).

  • Only virtual machines with persistent Cinder volumes can be configured for backup. VMs with ephemeral disks are discovered but disabled for configuration.

  • Understanding VM Discovery: Druva supports the following discovery triggers for OpenStack:

    • Automated periodic refresh: Discovered VM lists are refreshed automatically every 24 hours.

    • Manual refresh: Update the VM list at any time by clicking Discover VMs on the All Virtual Machines page.

    • Discovery during proxy registration: Registering a new backup proxy triggers an immediate discovery cycle.

Procedure

  1. Log in to the Druva Management Console.

  2. Select your Organization from the top menu bar (if organizations are enabled).

  3. Navigate to Protect > OpenStack.

    The All Projects page appears, listing all registered OpenStack projects.

  4. Select the desired OpenStack project from the Project list in the left navigation pane.

  5. Click Discover VMs to trigger VM discovery for the project.

    📝 Note

    ​Hover over Discover VMs to check the Last Discovery Run timestamp.

  6. Click Proceed in the VM Discovery dialog to navigate to the All Virtual Machines list.

  7. Select the virtual machines you want to protect.

  8. Click Configure for Backup.

  9. In the Configure for Backup dialog, specify the following details and Click Save.

    The status of the virtual machines updates to Configured, and they appear on the Configured VMs page.
    ​

Field

Description

Administrative Group

Administrative groups are formed to simplify server management. It is a logical categorization of servers and virtual machines that share similar attributes. Servers can be grouped based on similar attributes like server type, server location, and operating system.

You can either:

  • Select an existing administrative group or

  • create a new one to logically categorize the OpenStack VM.

Storage Region

Region where you want to store the backups of backup recovery points. You cannot change storage later.

  • If only Azure Storage is provisioned, you’ll see the Azure storage options supported by Druva.

  • If only AWS Storage is provisioned, you’ll see AWS storage options.

  • If both Azure Storage and AWS Storage are provisioned options for both will appear. You can select either option.
    For more information, see Azure Cloud Storage for Enterprise Workloads.

📝 Note

​Storage region cannot be changed after configuration.

Backup Policy

Select the backup policy defining the schedule and retention rules for the VM.

You can

  • Choose an existing or the default backup policy.

  • Create a new backup policy.

For more information on creating a new policy, see Manage backup policy.

Backup Proxy

Select the registered OpenStack backup proxy that will execute backup jobs for these VMs.

FAQ

What happens if an OpenStack project is discovered but no backup proxy is deployed?

A proxy is required for data protection. If no backup proxy is registered for the project, you cannot configure or back up its VMs. The Configure for Backup page will display no available proxies, and the Configured VMs page will show:

No virtual machines are configured for backup

Related Articles
Did this answer your question?