[Update: March 26, 2019]
This page describes the Archive function for optimal data storage.
The Archive function provides an optimal space for data storage not involving frequent content changes; for example, disk images or backup data which are templates for when creating a server.
The archive function provides my archive, which enables the user to freely perform creation and deletion, as well as public archive, which is provided by SAKURA internet with each type of OS, etc., already installed. Both types of archives can be used similarly for reference at times such as when creating a server. However, in the case of a public archive, it is not possible for the user to create, delete, or change contents. (It is possible to copy the public archive to a disk, change the contents on a connected server, and then store the contents in my archive.
The public archive is mainly envisioned for use when creating a new server. The archive is provided with CentOS, Ubuntu, etc., already installed. For details, please refer to Public archive .
In addition to archive, the Disk function makes it possible to store data on SAKURA Cloud. It is used by connecting to a server. Since it is not possible to connect to a server and use data, archive is a less expensive option for storing data.
A comparison of each function is as follows.
|Appropriate usage||Block storage for connection to the server||Data storage without input or output via direct connection to the server|
|Connection to server||Possible||Not possible|
|Items which can be specified as source when creating a new archive||Disk in the same zone
My archive in the same zone
|Disk in the same zone
My archive in the same zone
My archive in a different zone
Disk of SAKURA VPS with the same member ID
|Example of monthly usage fees||20GB: Monthly fees from JPY 432 (Ishikari Zone No. 1/SSD Plan)||20GB: Monthly fees from JPY 216|
|Data upload/download via FTP||Not possible||Possible|
|Copy from other zone/SAKURA VPS disk||Not possible||Possible|
Mutual copying of data is possible between the disk and archive. Therefore, use is possible depending on the intended purpose while supplementing the disadvantages of the disk and archive.
Procedures for creating a new archive are as follows.
Click [Archive] under the [Storage] category on the left-hand side of the control panel.
Clicking [Archive] displays a list of archives that have already been created in the currently selected zone.
To create a new archive, click the [Add] button at the top-right of the list screen. The archive creation form is displayed. Enter the required information in the form.
|Archive source (*)||You can create a blank archive; in other words, an archive without any contents. Also, by specifying the source, you can create an archive which already contains data.
*For details, please refer to the following “Archive source” item.
|Archive size (*)||Set the capacity for the archive being created. The fee chart at the top of the form changes depending on the capacity.
*Only displayed if [Blank] is selected for the archive source. For options other than [Blank], an appropriate archive size is set automatically depending on the source capacity.
|Name||Specify the name of the archive. The entered name is displayed on the archive list screen.|
|Description/tag/icon||Similar to other resources, you can sort archives into easy-to-understand categories depending on purpose and usage.
*For information on tags, refer to the Tag function page. For information on icons, please refer to the Icon page.
Required items are denoted by an asterisk (*).
When the archive source is set to the default [Blank], the archive is created without any contents. (After creation, images can be stored via FTP upload or the copy function.) However, by selecting [Disk], [Archive], or [VPS Disk], you can create an archive that already stores the disk image of the specified source when creation is complete.
When [Disk] is selected¶
From the pop-up menu, you can select a list of disks which exist in the selected zone.
At the same time as archive creation, the disk image at the time that creation starts is created in the archive.
The disk image at the time that archive creation is executed is saved. However, if the disk write operation is currently being executed, there are cases in which a disk image containing incomplete data is acquired. We recommend temporarily stopping the server, or targeting a disk which is not connected to a server.
When [Archive] is selected¶
When [Archive] is selected, you can use the zone transferring function. Therefore, the radio button for zone selection is additionally displayed. By selecting other arbitrary zones in addition to the current zone, you can select an archive from the selected zone from the pop-up menu. This function makes it possible to temporarily save the disk as an archive in another zone, and to specify that archive as the source in the transfer destination zone. This enables you to transfer data of disks and archives among zones.
When [VPS Disk] is selected¶
If a contract for SAKURA VPS exists for the currently logged in member ID, you can select a list of contracted VPS servers from the pop-up menu. The disk image of the server selected here is saved in the archive. This is convenient when you want to migrate the server from SAKURA VPS to SAKURA Cloud.
Depending on factors such as the VPS server disk size and congestion, several hours may be required from copying from the VPS disk until the completion of creation.
After entering required items in the form, start creation by clicking the [Create] button. Operations after clicking the [Create] button will differ depending on the type of source selected in the form for creating a new one. Please perform additional procedures and checks as follows.
When [Blank] is selected for the source¶
Data is not transferred, so creation is normally finished in about one minute. After creation is finished, connection information is displayed for uploading via FTP. You can upload the disk image or other information saved on your computer.
The upload method is the same as for an ISO image. For details, please refer to ISO image upload on the ISO image page.
When a source other than [Blank] is selected¶
Data copy from the source starts. The active status on the archive list screen changes to [Creating] or [Transferring].
When the source is an archive from another zone or a VPS disk, the active status changes to [Transferring] and the estimated time until completion is not displayed.
Similar to the public archive provided by SAKURA Cloud, you can rewrite to the disk by specifying the archive created by the customer as the source when creating a disk or performing reinstallation.
Even in the case of an archive created by the customer, it is possible to change network information or passwords and write to the disk as long as the OS supports the disk modification function. However, please note that warranties do not apply to any archive other than the public archive provided by SAKURA Cloud.
Even when Create a new disk , you can specify my archive for the disk source and create a new disk to which the contents of an arbitrary archive are written.
Even for the :ref:`OS reinstall <os-reinstall>`operation which involves overwriting the existing disk which already has data written to it, you can overwrite with contents from an archive created by the customer by specifying my archive for the disk source.
When the disk targeted for reinstallation is connected to the server, you must first Turn off power to the server before performing the reinstallation.
Procedures for deleting an archive that has already been created are as follows.
It is not possible to recover an archive that has been deleted. Be very careful when deleting an archive.
Insert a check into the checkbox of the archive that you want to delete and then click [Delete].
Check that a list of the archives targeted for deletion is displayed at the confirmation screen. If there are no problems, click [Delete].
- The disk contents at the time that archive creation was started are saved as the archive.
- There is no encryption processing for the archive. Copying from the source is performed at the block level. Therefore, if the target disk is encrypted at the file system level, the encrypted contents will be saved as the archive.