Your server is defined, not assembled
strackt records packages, services, users, and firewall rules in a versioned definition. The next managed operation brings the setup back into line with it.
Recorded in the definition
- System packages and their versions.
- Services, users, and firewall rules.
- The settings that keep your server running.
Protected separately
- Application code and its release history.
- Databases, uploads and other application data.
Defined once. Ready for what comes next.
One recorded setup supports three different operations.
Upgrade in place
From the definitionYour data stays on this server. A configuration change is not a database restore.
A reviewed distribution release becomes part of the definition.
Prepare the next system while the current generation remains available.
Check the configuration and service compatibility before activation.
Activate on the same machine. Reboot when boot components require it.
Move a workload
From the definitionThe workload’s data moves too. Provisioning the target is only part of the move.
Recreate the workload’s required services on the destination.
Transfer application data before switching the workload.
Check the destination. The move waits for cutover confirmation.
Confirm cutover, bridge remaining traffic, then drain and clean up the source.
Rebuild a server
From the definitionThe definition rebuilds the setup. Available backups recover the data.
Recover the recorded application, service, and system configuration.
Build a compatible replacement from the recorded configuration.
Restore the available backup onto the replacement. Code cannot recreate missing business data.
Check the recovered application and services before returning them to use.
Illustrated sequence. Playback compresses time; it does not operate a live server.
Experiment with a way back
You keep SSH access. Manual changes to managed settings can be replaced by the next configuration operation.