Windows service model
The pilot agent runs as a managed Windows service.
Agent tour
From Windows installation to controlled SQL Server protection.
The agent tour illustrates the pilot workflow for connecting a Windows environment, discovering supported SQL Server workloads and applying centrally managed backup policies.
Activate
ConnectedLicense activation
✓Use a controlled activation workflow
✓Register the machine identity
✓Confirm API connectivity
Step 1 of 5
License activation
Connect the installed agent to the intended customer and device identity.
- Use a controlled activation workflow
- Register the machine identity
- Confirm API connectivity
Step 2 of 5
SQL Server discovery
Identify supported SQL Server instances and databases before protection is configured.
- Detect available instances
- Review database inventory
- Avoid duplicate or unintended selections
Step 3 of 5
Access validation
Check whether the service context can perform the required SQL Server backup operations.
- Validate service-account access
- Surface permission requirements
- Avoid silent backup failures
Step 4 of 5
Database selection
Choose the databases that should enter the managed protection workflow.
- Confirm workload ownership
- Exclude unsupported or temporary databases
- Review expected data volume
Step 5 of 5
Policy synchronization
Receive approved schedules, retention and storage instructions from the platform.
- Apply assigned policies
- Report agent health
- Return backup and verification outcomes
1 / 5
This is an illustrative product walkthrough. Screens, labels and released capabilities may evolve as the platform develops.
Tour principles
Designed to explain the workflow without overstating the outcome.
SQL Server focus
The current public pilot is presented around Microsoft SQL Server workflows.
Controlled permissions
Required access should be documented and limited to the operational need.
See your environment