A blueprint is a master or baseline entity that could contain virtual machines, networking, preinstalled software, company branding, use case collateral, and content (overview pages, resources to show files, and more). A blueprint is the container that includes the snapshots of an environment.
Snapshots capture the state of an environment at a specific moment and function as a version of the blueprint. This includes all virtual machines, RAM, CPU, disk allocations, network configurations, users, installed software, documents, and settings. They can even save the current states of RAM and disk, preserving any running services and applications at the time. This detailed backup allows you to restore the environment to exactly how it was when the snapshot was taken, making it a powerful tool for recovery, testing, and deployment.
In this section, we will cover:
- Creating a blueprint. Create a new blueprint when taking snapshots.
- Creating/saving snapshots. Capture the exact state of an environment at a specific point in time.
- Managing snapshots. Maintain blueprints and snapshots for more flexibility when managing an environment.
- Managing snapshot regions. Manage snapshot regions, to make use of that blueprint across different use cases and scenarios.
- Adding blueprints to different projects. Add blueprints to different projects, to store your blueprint in multiple data centers, and enable you to provide experiences geographically closer to your audience.