Detach a Google Volume from an Instance
Objective
Detach a volume from a running instance.
Table of Contents
Prerequisites
- A running instance with an attached volume.
Overview
You must use caution when detaching a volume from a running instance in order to ensure that no data is lost or corrupted. How you detach a volume will depend largely on the function of the volume. For example, if you are performing writes to the volume (i.e database or sys-log server), it is imperative that you freeze the file system before detaching the volume. However, if the volume is storing static data, freezing the file system may not be necessary. By default, when an instance is terminated, any attached volumes will automatically become "detached" from the running instance.
As a best practice, you will always want to create one last snapshot of a volume if you plan to delete it. You can either take the snapshot before you detach the volume or after it's been detached. Therefore, if you want to create one last snapshot before you detach (and possibly delete the volume), you should take one last backup snapshot.
Before you Detach a Volume
- Freeze the volume (if supported by the file system)
- Make sure that all files are closed and that there are no pending writes to the disk.
Manually detaching a Volume
There are two different ways you can detach a volume from a running instance:
- Detach at the server level
- Detach at the volume level
Detach at the Server Level
To detach an volume from an instance, go to the Volumes tab of an instance and click the Detach button (eraser icon) and confirm the action.
Detach at the Volume Level
Under Clouds > Google > Volumes, click on the Detach button of a volume.
You can also click the Detach button from the homepage of a selected volume.
- © Copyright 2015 RightScale Technical Support