Protecting data from a Cloud Environment created prior to August, 2020

Allie Hajian
  • Updated

Cloud Environments (Galaxy, Jupyter or RStudio) created before August 1, 2020 are incompatible with current features, and must be re-created. Learn how to see if you have an incompatible Cloud Environment as well as step-by-step instructions for protecting generated data and re-creating the Cloud Environment. 

1. Identify notebooks in old clusters

To see what Cloud Environments you created under each billing project, and when you created them, go to

See a virtual machine or cluster created before August 1st, 2020? Note the Billing Project name and keep reading. 


2. Check content of affected notebooks

To check what notebooks are affected, go to Your Workspaces and filter by the Billing Project (from step one above). Within the workspace, check in the Analyses tab of the filtered workspaces to see what analysis you ran. 

3. Save any data you want to keep

If you don’t save your output data to workspace storage (i.e., Google bucket), or if you delete your Persistent Disk (PD), the data will be lost when you delete your Cloud Environment.

If you want to keep output data from a notebook, save it to the workspace bucket. Copying notebook output to a Google bucket explains exactly how. 

4. Create a new Cloud Environment

4.1. When you are ready to create a new Cloud Environment (e.g., you’ve copied your files into workspace or other storage), click on the Cloud icon in the sidebar (Analyses tab display).

4.2. In the Jupyter Cloud Environment pane, click Delete Environment Options near the bottom.

4.3. If you do not need to customize your Cloud Environment, you can create a new one now.

If you want to select the number of your compute instance CPUs , or enter a start-up script, click on the "Customize" option for different application configurations and other custom settings. 

To learn more about your persistent disk deletion options, see Detachable persistent disks.

5. What if you used startup scripts?

Once you re-create the Jupyter Cloud Environment, you need to rerun the startup script to install custom software, libraries, and dependencies. Put the URI for the script in the Startup script field of the Custom compute profile before re-creating the Jupyter environment. 

Using a GATK custom startup script (workshops)

If you used the GATK custom startup script in a workshop, the URL to use when running the notebook again should be in the notebook itself.

Can't find your personal startup script? 

If you used your own custom startup script but can’t remember which one you used, we can help you find that information. Email us at or slack us at #dsp-comms-user-ed for help. 

Was this article helpful?



Please sign in to leave a comment.