Problem description
In a VMware environment, newly deployed Virtual Machines matching existing Autoconfiguration rules are not appearing as "Configured" immediately after rule creation. Users may expect the backup assignment to be instantaneous, but the VMs remain in an unconfigured state until a manual action is taken or a specific time period elapses.
Cause
The "Apply All Rules" button was not clicked in the UI after the rule was created. Consequently, the VMs were only discovered and configured after the 24-hour periodic automatic configuration cycle was completed.
Druva triggers this auto-configuration every 24 hours after the virtual machine list is updated; this interval is a fixed system setting and cannot be modified or scheduled for a specific time.
Resolution
To ensure virtual machines are configured according to your rules, use one of the following methods:
1. Immediate Manual Configuration
After you create or modify a rule, click Apply All Rules in the Druva UI. This manually triggers the system to evaluate eligible virtual machines and configure them for backup immediately.
2. Automatic Scheduled Configuration
If no manual action is taken, simply wait for the periodic automatic configuration. Druva will automatically trigger the rules every 24 hours. Note that you cannot modify this interval or specify a particular time for this job to run.
Include and exclude filters
Include Filters: Ensure the VM's attributes (Tags, Datastores, or Clusters) align with the rule criteria.
Exclude Filters: Verify that the VM is not being caught by an exclusion filter that overrides the inclusion logic, preventing it from being configured during the discovery cycle.
Verification
To verify if the resolution has worked:
After clicking Apply All Rules, navigate to the Virtual Machines list.
Filter by "Configured" status.
Confirm that the previously unconfigured VMs are now associated with the intended backup policy.