--- title: Node Images --- # Node Images Use this page to understand how saved images fit into node management in MyAccount. This page is intentionally limited to the node management context. It explains when you create or use a saved image from a node, what it is for, and which node actions it affects. For the full standalone image workflow, see the dedicated image pages listed in [Related resources](#related-resources). For point-in-time storage copies, see [Node Snapshots](/docs/myaccount/node/features/snapshots). --- ## Where Saved Images Appear After you create a node, saved images can appear in three places: | Place | What you do there | | ----------------- | ---------------------------------------------------------------------- | | Node action menu | Create a saved image when the node state supports it. | | Snapshots tab | Create a saved image from an existing snapshot. | | Saved Images area | View saved images created from nodes and use them to create new nodes. | The portal shows or hides these options based on the selected node, node family, node state, operating system, permissions, and system validation. The flows below assume you have already opened **Compute > Nodes** and selected the node or node action menu. --- ## Saved Images in Node Management A saved image is a reusable image created from a node. Use it when you want to launch another node from the same configured operating system and software state. Saved images are useful when: - You configured a node and want to reuse that setup. - You want a repeatable base image for future nodes. - You need a recovery or migration point that can be used to create a new node. In node management, saved images are created from the node action menu by using **Save Image** where available. ### Before Creating a Saved Image Check these points before saving an image: - The node state requirement depends on the node series. - Locked nodes cannot create saved images until they are unlocked. - Some licensed images, such as nodes with an attached MS SQL license, do not support saved-image creation. - While the image is being saved, other management actions on the node can be disabled. - Saved images can have their own billing impact. ### Save Image Availability by Node Series The **Save Image** action is available only when the node series and node state pass validation. | Node series | When Save Image can be created | Notes | | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | C3, M3, SDC3, GDC3, M3VPS, C3VPS, E1, E1WC | While the node is Running, where the action is otherwise available. | These series use the snapshot-based saved-image path, so the node does not need to be powered off first. | | Other save-image-supported series, including older C/C2 and M/M2 plan families where shown in the portal | Only after the node is Powered off. | If the node is Running, power it off and then retry **Save Image**. | The portal can still hide or disable **Save Image** for other reasons, including locked nodes, Disaster Recovery target nodes, Spot nodes, transitional states, Recovery Mode, unsupported VM type, or an attached MS SQL license. :::tip Best Practice Use a saved image for repeatable node creation, not as a substitute for regular data backup. If the workload stores changing data, use backups or snapshots as appropriate. ::: ### Create a Saved Image from a Node Use this flow when you want to create a saved image directly from an existing node: 1. Select the node action menu and choose **Save Image**. 2. If the portal asks for the node to be powered off, power off the node and retry the action. Some node series can save an image while running; see [Save Image Availability by Node Series](#save-image-availability-by-node-series). 3. In the **Save Image** dialog, review the storage billing note. 4. Enter a saved image name. The name can contain only letters, digits, underscores, and hyphens. 5. Select **Save Image**. 6. Wait for the save-image process to complete. During this time, the node can show a saving state and other node actions can be unavailable. 7. After the image is ready, open the **Saved Images** area to view it or use it while creating another node. The saved image is created from the node root or OS disk only. Attached volumes are not included in a saved image created from the node. ### Create a Saved Image from a Snapshot Where supported, you can also create a saved image from an existing node snapshot: 1. Find the snapshot in the snapshot list. 2. Open the snapshot action menu and select **Save as Image**. 3. In the **Save Image** dialog, review the storage billing note. 4. Enter a saved image name. The name can contain only letters, digits, underscores, and hyphens. 5. Select **Save Image**. 6. After the process starts, wait for the saved image to become available in the **Saved Images** area. The **Save as Image** action is disabled for snapshots that are **In progress** or **Terminating**. It is also disabled when the node is in a save-image state such as **Live saving** or **Initializing**, or when the node is a Disaster Recovery target node. ### Creating a Node from a Saved Image When you create a node from a saved image, the image is used as the base image in the create-node flow. The portal can restrict the target plan based on the saved image and current node plan compatibility. In general, expect to choose the same or a compatible higher configuration when creating a new node from a saved image. For E1-series saved images, the target node can use E1-specific root storage selection. The minimum selectable storage can depend on the size of the saved image. After the saved image is selected, the rest of the create-node flow still matters: - Plan - Billing option - Backup - Network - Security group - SSH keys or password access - Volumes - Advanced settings For the full launch flow, see [Create a node](/docs/myaccount/node/getting-started/create-node). --- ## Images vs Snapshots | Use case | Use saved image | Use snapshot | | ------------------------------------------------------- | --------------- | ----------------------------------------------------------- | | Launch another node with the same configured base state | Yes | Sometimes, if saving an image from a snapshot is supported. | | Capture a point-in-time restore point | No | Yes | | Prepare a reusable image for future node creation | Yes | No | | Protect data before a risky change | Sometimes | Yes | | Include attached volumes in the capture | No | Yes, where supported. | | Keep a node configuration for repeatable deployment | Yes | No | For the snapshot side of this comparison, see [Node Snapshots](/docs/myaccount/node/features/snapshots). --- ## How Saved Images Affect Other Node Actions Saved images can affect other node operations: - Saved image creation can temporarily disable node management actions. - Locked nodes can block save image actions. - Deleting a node does not replace the need to review related saved images, snapshots, backups, volumes, public IPs, and Add-on IPs. Before deleting or changing a node, check whether you still need its saved images. --- ## Related Resources | Resource | Use it for | | ---------------------------------------------------------------------- | ---------------------------------------------------------------- | | [Manage Nodes](/docs/myaccount/node/manage) | Main node management overview. | | [Node Snapshots](/docs/myaccount/node/features/snapshots) | Point-in-time copies of node disks and attached volumes. | | [Node Encryption](/docs/myaccount/node/features/encryption) | Understand how encrypted nodes affect image management. | | [Action Availability](/docs/myaccount/node/manage/action-availability) | Check why image actions are hidden, disabled, or rejected. | | [Create Images](/docs/myaccount/node/features/images) | Full saved-image workflow, including saved-image management. | | [Create a node](/docs/myaccount/node/getting-started/create-node) | Launch a new node from an OS, marketplace image, or saved image. | ---