When you set up test environments, you can push your live production database—if GDPR and your own policies allow—to the test environments in order to run tests with live data.
Take your backups further. Use them to generate new test environments, work locally without an internet connection and debug safely with replicas of your production environment, object storage or production database.
Our backups run on a grandparent, parent, child model and run automatically from the moment you deploy an application.
Just because we generate backups automatically or even on custom schedules, doesn’t mean you can’t make a manual backup whenever you want.
This is especially useful for bonus use-cases. For example, you might want to create a spare backup before a code deployment or a large content change, in which case the manual backup option comes in handy.
Our backup and restore system also allows you to restore to any environment, not just the environment you took the backup from.
When you set up test environments, you can push your live production database—if GDPR and your own policies allow—to the test environments in order to run tests with live data.
Teams may need different testing environments for different kinds of testing that happens at the same time. With Divio, you can create as many test environments as you need, with or without production data.
When you set up test environments, you can push your live production database—if GDPR and your own policies allow—to the test environments in order to run tests with live data.
Pull data offline in order to test. You can even change the data locally and then push it back online and to the live environment after you finish testing.
Whether you’re on a flight, a train or the deck of a cabana over the ocean, you can work locally with a replica of the production environment (code, object storage and/or database). Later, just connect online to push your changes to your actual production environment.