Custom images are a useful tool for creating new servers with the same base configuration. It is also useful if you just need to set up a server similar to what you already have and wish to skip the hassle of configuring a new server from scratch.<\/p>\n\n\n\n

Imaging a server creates a new storage disk that is a 1:1 copy of the base server\u2019s storage. The custom image can then be used to deploy new servers with the same features and settings.<\/p>\n\n\n\n

Test hosting on UpCloud!<\/a><\/div>\n<\/div>\n\n\n\n

Before imaging<\/h2>\n\n\n\n
Before imaging a server, you should check through your server to make sure everything is working as expected. For servers running CentOS 6.7 or older and Ubuntu 12.04 or older, you should rename the current MAC address reference file to avoid extra reboots.<\/p>\n\n\n\n
sudo mv \/etc\/udev\/rules.d\/70-persistent-net.rules \/etc\/udev\/rules.d\/70-persistent-net.rules.old<\/pre>\n\n\n\n
The system will generate a new file again on the next reboot.<\/p>\n\n\n\n
Other servers with OSs different to those mentioned above, such as any newer Linux distribution or Windows Servers, do not need any special preparations for imaging.<\/p>\n\n\n\n
Creating custom image<\/h2>\n\n\n\n
Note that the source storage cannot be in use during imaging.<\/b><\/p>\n\n\n\n
To start imaging a server, log in to your UpCloud control panel<\/a> and shut down the server.<\/p>\n\n\n\n
Go to your Storage list<\/a>\u00a0and find the system device of the server you wish to image. Attached to<\/em> will indicate which server each storage belongs to.<\/p>\n\n\n\n
Click the Create custom image<\/em> button on the storage device you want to copy into a new image. Then give the custom image a name and click the Create<\/em> button.<\/p>\n\n\n\n
$\"Create$ <\/figure>\n\n\n\n
The process of image creation is quick but will vary depending on the size of the storage device. Once finished, you\u2019ll get a notification and the origin server can be started up again.<\/p>\n\n\n\n
$\"Successfully$ <\/figure>\n\n\n\n
Deploying custom image<\/h2>\n\n\n\n
You can find your custom images in your UpCloud control panel<\/a> under the Storage section. The custom images can be deployed straight from the list or you can find the images in the operating system selection on the deployment page.<\/p>\n\n\n\n
Deploy a new server using a custom image by clicking the Deploy button.<\/p>\n\n\n\n
$\"Deploy$ <\/figure>\n\n\n\n
This will open a new server deployment page with the custom image and associated location preselected.<\/p>\n\n\n\n
Pick the server configuration and give your new custom server a hostname, then click the Deploy<\/em> button when ready.<\/p>\n","protected":false},"featured_media":27208,"comment_status":"open","ping_status":"closed","template":"","community-category":[109,110],"class_list":["post-24658","tutorial","type-tutorial","status-publish","has-post-thumbnail","hentry","community-category-upcloud-services","community-category-storage"],"acf":[],"_links":{"self":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial\/24658","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/types\/tutorial"}],"replies":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/comments?post=24658"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media\/27208"}],"wp:attachment":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media?parent=24658"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/community-category?post=24658"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Before imaging<\/h2>\n\n\n\nBefore imaging a server, you should check through your server to make sure everything is working as expected. For servers running CentOS 6.7 or older and Ubuntu 12.04 or older, you should rename the current MAC address reference file to avoid extra reboots.<\/p>\n\n\n\n

Creating custom image<\/h2>\n\n\n\nNote that the source storage cannot be in use during imaging.<\/b><\/p>\n\n\n\n