CloudShell Version: 9.1 GA

Help Version: 1.5

Api Guide
View / Download All Help Versions
Online Help

This help article applies to CloudShell 9.1. To see the latest, click here.

You are here: Sandboxes > Sandbox Save and Restore Overview

Sandbox Save and Restore Overview

This article introduces the Save and Restore paid add-on, which enables you to save an active sandbox and later restore the saved sandbox to work on.

This feature supports only sandbox with virtual vCenter components, physical resources and CloudShell services. Sandboxes that include Apps based on other cloud service providers are not yet supported.

The Save and Restore add-on is part of the Sandbox Lifecycle initiative, which will be expanded in the future to include additional flows and use cases.

What is a saved sandbox?

When saving an active sandbox, CloudShell creates a complete copy of the sandbox and its components. CloudShell services and resources are copied as is. If the sandbox contains deployed vCenter Apps, CloudShell creates (in the vCenter server), all the artifacts that will be required to restore the VMs. The saved sandbox is an independent copy of the original sandbox, and can be restored to multiple sandboxes. When deleting a saved sandbox, CloudShell deletes (from the vCenter server) all artifacts related to that saved sandbox and only then deletes the saved sandbox artifacts from CloudShell.

For example, if you finished working on a sandbox, and would like to continue working on it later on, you can save the sandbox and return to it without losing any of your work.

In addition, if you are working on a sandbox and would like to create a backup before committing a major change, you can save the sandbox, continue working and restore the backup when needed.

Restore and delete saved sandboxes

From the My Saved Sandboxes dashboard, you can view your saved sandboxes, and restore and delete a saved sandbox.

Save and restore license

Since Save and Restore is a CloudShell paid add-on, you are required to purchase a dedicated license (SaveRestore) to benefit from these capabilities. Please contact your account manager for details.

Recommended workflow

  1. Enable Save and Restore in a blueprint. See Define the Blueprint's Properties.
  2. Reserve a blueprint from the Catalog
  3. Save a Sandbox
  4. Manage saved sandboxes in the Saved Sandboxes Dashboard
    1. Restore a Saved Sandbox
    2. Delete a Saved Sandbox

Configuration and administration process

This feature does not require any specific configuration other than obtaining a license from your account manager.

You can customize and manage certain aspects of the save and restore flow. For example, the admin can define the max saved sandboxes per user and configure certain aspects of the saving action in vCenter. The save and restore action logic is defined in orchestration scripts, similar to setup and teardown. These scripts can be customized according to your needs.