Create your first policy. Verify the recovery point.
Start with a small test virtual machine after installation and data-path checks. This guide covers the VM policy workflow; apply additional platform-specific prerequisites for database or application consistency.
UI field names come from the existing VM policy template. Options vary by platform and delivered version. OpenStack/Safir, VMware and OpenShift data paths have different prerequisites.
Screenshots were captured from the actual lab interface on 16 October 2026. The interface is in English; explanations follow your selected language. Resource names, dates and settings are examples; use values for your own environment.
Installation and licensing checks completed
Correct platform inventory and healthy data path
Reachable repository with sufficient capacity
Test target reserved for isolated recovery
01
1. Select a test source and success criteria
Choose a small VM that will not affect production data. Include a test file or application data to check after recovery. Record source name, platform, approximate disk size and target recovery point. For databases, do not equate a VM snapshot with application-consistency acceptance.
Expected result
The test source and data to validate after restore are defined in advance.
02
2. Fill in Create Policy and Attribute fields
Open Create Policy in the VM policy screen. In Attribute, select the platform using Policy Type and the source connection using Server. Enter a recognizable Policy Name, such as demo-vm-full. Select the validated repository record in Storage. Check server identity when multiple environments share similar names.
Attribute: Policy Type, Server, Policy Name and Storage. This example shows a policy form before its fields are filled in. Enlarge ↗
Expected result
Platform, source connection, policy name and storage target are correct.
03
3. Select only the test VM in Clients
Move to Clients and select the test VM. If using search or filters, review the selected list again and make sure previously selected hidden entries are not included. For multi-disk VMs, validate the required disk set and capacity against platform scope.
Clients: one lab VM is selected using search; Summary shows 1 Machines Selected. The form was not saved. Enlarge ↗
Expected result
The policy includes only the approved test source.
04
4. Configure Advanced Settings and retention
Set Backup Retention Time to match the test plan. Use archive, synthetic, replication or consistency options only when their components have been validated. OpenStack application consistency requires guest/hook preparation; OpenShift database profiles require Secret, RBAC and adapter prerequisites. Keep unnecessary options disabled for the first test.
Advanced Settings: the Crash-consistent profile and Backup Retention Time. Visible options do not establish out-of-the-box support or identical acceptance scope in every environment. Enlarge ↗
Expected result
Retention is clear and prerequisites for selected options are satisfied.
05
5. Plan the initial Full run in Schedules
In Schedules, use Set Full Backup Days to define Full days. Review Days, Months, Repeat and start/end times, allowing for the server time zone and overlapping jobs. Start Now triggers an immediate run; select it only in an approved test window. Do not assume an incremental chain is ready before a successful initial full point exists. Verify source, storage and retention choices from earlier steps, then save with Create Policy.
Schedules: Days, Months, Repeat and Full/Incremental time windows. Times are examples; Start Now was not selected and Create Policy was not submitted. Enlarge ↗
Expected result
The policy is saved with the correct source and target and a defined initial Full run time.
06
6. Monitor the run and job details
Monitor the scheduled run in the task or notification screen. Check that policy name, source and job type match the test plan. If queued, inspect queue status rather than create another job. On failure, record job ID, time, component and an error message with credentials removed.
Expected result
The job completes and its final status is checked, not just its progress percentage.
07
7. Check the backup point and recovery readiness
Find the source in the backup list. Review the new point’s time, Full type, repository and disk/data scope. Record the test file and source state, then proceed to the isolated-target restore guide. A successful backup record does not complete acceptance until data has been restored and checked.
Home → Backups → Backup List: Last Backup for an existing Safir lab policy. This is a separate existing test job, not the unsaved example shown in the policy screens. Enlarge ↗
Expected result
A selectable recovery point exists and is recorded for the isolated restore test.
COMMON QUESTIONS
Can I choose Incremental for the first run?
Start the first test with Full. Incremental chain validity depends on the platform and an existing full point; VMware CBT and OpenStack incremental requirements are assessed separately.