September 2020: Closure of old plan environment at Ishikari Zone No. 1



In conjunction with the start of provision for the new plan in Ishikari Zone No. 1 in September 2018, we continue to provide the old plan environment with limited functionality. However, we forecast that it will become difficult to maintain a certain level of quality when providing the old plan environment to customers. These quality issues will arise due to factors such as increased maintenance and longer time required to recover from malfunctions, caused by exceeding the usable lifespan of server/storage facilities and deterioration of said facilities. Therefore, we have decided to close the old plan environment in September 2020, which will make nine years since opening of the zone.
This page provides a detailed schedule until closure and information on procedures for migrating from an old plan environment to a new plan environment, including cases performed using the existing environment such as IP addresses, etc. We apologize for the inconvenience to customers who use the Ishikari Zone No. 1 old plan environment. Please read the related information and respond as appropriate.

Target resource

Resources targeted for migration are as follows.

  • Ishikari Zone No. 1: Old plan server
  • Ishikari Zone No. 1: Old plan disk


Old plan servers and disks are displayed as [Old Plan] at each list screen of the control panel.


(When all resources operate using the new plan, the new plan/old plan display is omitted. In that case, more procedures are unnecessary.)

  • Ishikari Zone No. 1: All appliances for VPC routers, load balancers, and NFS that were created on or before September 27, 2018


Unlike servers and disks, [Old Plan] is not displayed at the control panel for appliances. Please identify old plan appliances by checking the creation date.



The following is the plan schedule until closure.


This is the forecasted schedule at the current time. The schedule is subject to change due to various circumstances. We will contact customers who are using the Ishikari Zone No. 1 old plan as necessary regarding any changes.

July 31, 2019

On this date, the following operations will no longer be possible using the old plan.

  • Create new server
  • Create new disks
  • Changing from one old plan to another old plan


From August 1, 2019, creation of servers and disks in Ishikari Zone No. 1 will only be possible via the new plan environment. Also, when changing the plan, it will only be possible to change to the new plan.

Furthermore, from this date, sequential migration work to the new plan environment will start for the following appliances:

  • VPC router
  • Load balancer
  • NFS



Depending on the type of appliance and plan, the start date for appliance migration work, the work required by the customers, and the length of service stoppage at the time of migration may differ. We will contact each customer individually once we have decided on a migration schedule.

September 30, 2020

As of this date, we will stop all provision of services for the old plan. Servers in the old plan environment will be stopped and it will no longer be possible to access the network or console.
Disks will be deleted. Data will be deleted using a safe method which makes recovery impossible.


Recovery of the deleted server IP address and deleted resources (disk data, etc.) will not be possible. We ask that customers perform migration work by this date.

How to migrate servers and disks to the new plan

If you wish to continue using servers and disks in the old plan even after the date of closure for the old plan, you must perform migration work to the new plan. This section explains detailed migration procedures for these items.


You can update from an old plan to the new plan without changing the IP address for the NIC connected to the shared network via operations at the control panel. Also, you can continue to use functions such as Packet filter in the new environment in the same way as they were used in the old environment.



The 20GB Standard (HDD) Plan that was provided in the old plan environment is not provided in the new plan. Instead, please use the 20GB SSD Plan, which provides superior performance compared to the 20GB Standard Plan at the same price.

Migrate by using disk copy to copy contents to the new plan disk which will be newly created. Select the target old plan disk and then click the [Copy] button at the top-right of the screen. Select [Disk] for the copy destination and then click the [Next] button.

The copy destination disk settings screen is displayed. Use the generation selection radio buttons at the top of the screen and select [New Plan]. Confirm that the disk which you want to migrate is selected as the source disk and that the same capacity is selected for disk size. Next, click the [Create] button.


Furthermore, conversion to the new plan is performed automatically after operations for OS reinstall. Please also update to the new plan for the generation of connected servers.


After temporarily stopping the server for the old plan, you can migrate to the new plan by executing Change plan . Select [New Plan] for the change destination plan. (You can also update to specifications differing from the old plan at the same time as migrating.)


Servers that have been migrated to the new plan cannot connect to disks which are connected to an old plan. If an old plan is being used by disks connected to the server which you want to migrate to the new plan, first migrate the disks to the new plan, or consider the migration method using the cloning function as explained in the next item.
Also, when reconnecting a disk after migration, please check the disk name and the disk resource ID, and perform connection in the same order (connect the disks from the smaller connection number in order) as before the migration work. (For connection procedures, please refer to :ref:``Connect/disconnect disk to/from server <disk-server-connect>` .)

When simultaneously updating server and disk to the new plan

You can simultaneously replicate the server and disk for an old plan to a new plan by using the cloning function for the old plan server and disk. For information on using the cloning function, please refer to Cloning function.


When using the cloning function, resources are created as temporary replications. Therefore, if an IP address has been assigned from a shared network, the current IP address will be changed. (There is no problem when using a unique IP address assigned to the customer; for example, in the case of router + switch.) If it is necessary to migrate to the new plan without changing the IP address that was assigned from a shared network, individually migrate the server and disk to the new plan without using the cloning function.
Also, if two or more NICs or two or more disks are connected, you must manually perform additional settings and copy disks individually for the second and subsequent NICs or disks.

For information on caution points when using the new plan, please refer to the New plan for Ishikari Zone No. 1 page.

NFS Appliances

You can use the cloning function to migrate NFS appliances to the new plan. Currently, NFS appliances which are newly created in Ishikari Zone No. 1 are created in the new plan environment. Disk contents can be migrated without any changes via Creation by specifying as a clone source for the NFS appliance being created in the old plan environment.


Similar to servers, the screen listing NFS appliances indicates whether appliances use the [New Plan] or [Old Plan]. NFS appliances displayed as [Old Plan] are targeted for migration.

Tool for migration from old plan to new plan

In Offers on GitHub , SAKURA Cloud provides tools for easily migrating servers and disks created using an old plan to the new plan. By using this tool, you can easily migrate to a new plan with advantageous functions and prices, without the need to change network configuration.


If multiple servers are specified, parallel processing is performed. Please note that simultaneous processing will not be performed in the case of redundant configuration, etc.

Required environment

The following conditions must be satisfied in order to use the tool.

  • An API key possessing operating authority for the server targeted for migration must be issued.
  • It must be possible to use Linux, FreeBSD, Windows, MacOS or other CLI environment in which the migration tool operates. (Migration is not possible by running the tool in the server targeted for migration.)

Furthermore, the following items required for executing the tool must be prepared in advance:

  • API key (set of access token and access token secret)
  • Resource ID, name, tag, and other information of the server targeted for migration that will be specified when executing the tool


Downloading of tools

You can download the tool from Here . The end of the file name indicates the environment in which the tool operates (for example, “linux-amd64” indicates use in a 64-bit environment Linux). Please download the appropriate file.

The downloaded archive is a zip file. Use the unzip command or other method to expand the file.

Execution of tools

The body of the tool is cloud-plan-migrate inside the expanded directory. Here, specify the resource ID of the server targeted for migration as a parameter and then execute the tool.

$ cloud-plan-migrate <サーバのリソースID または名前>


If you want to migrate multiple servers, you can specify multiple resource IDs in the parameter. Furthermore, in addition to the resource ID, you can specify the server name. (If there are multiple servers with the same name, the tool will be executed for all servers. Please be careful when setting the terminal if the name uses multi-byte characters, such as in the Japanese language.)

Also, by using the --selector option and executing an arbitrary tag name in the parameter, you can perform batch execution for all servers to which that tag is assigned. If the old plan has a large amount of servers, you can easily execute the migration tool by assigning dedicated tags to the servers targeted for migration.

$ cloud-plan-migrate --selector <タグ名>

After execution, an entry prompt is displayed. Enter the token and secret here.

Your API AccessToken is not set
   Enter your token: <アクセストークンを入力>
Your API AccessTokenSecret is not set
   Eneter your secret: <アクセストークンシークレットを入力>

Using the tool to execute migration work

The tool automatically executes migration work after acquiring information on the target server, information on the API key, and other information required after the server. The main work executed by the tool is as follows.

  1. Shut down the server if it is running.
  2. Disconnect disks.
  3. Clone each disk and create a new plan disk.
  4. Connect disks.
  5. Change the server plan.
  6. Start server (Default: Enabled; can be set to “disabled” as an option).
  7. Delete old disks (Default: Disabled; enabled only when specified as an option).

During processing, the migration progress status for the target resource is displayed on the screen. Logs are successively output in a migrate-[yyyyMMdd-HHmmss].log format under the current directory.


An error will occur and migration work will not be performed if no disk is connected to the target server, or if even one server is included that has already been migrated to a new plan.

Other command options

In addition to the --selector option which was just introduced, you can also use the following command line options.

  • --token: Specify the API key (access token). You can also specify the environment variable SAKURACLOUD_ACCESS_TOKEN.
  • --secret: Specify the API key (access token secret). You can also specify the environment variable SAKURACLOUD_ACCESS_TOKEN_SECRET.
  • --disable-reboot: The server is not rebooted after plan migration is finished.
  • --cleanup-disk: Delete the old plan disk after plan migration is finished.
  • --assumeyes or -y: Omit confirmation before executing the migration work.


When the --token or --secret option is used, an entry prompt is not displayed after execution. However, in some cases, API key information may be displayed after the process being executed is confirmed by another user that is currently logged in. Please use while paying sufficient attention.
Also, if processing is executed with multiple servers specified, parallel processing is performed for the servers and power will be turned off simultaneously for a certain period of time. For servers with a redundant configuration, please perform migration work individually in order to prevent total stoppage of the service.


Q. What are the merits of migrating to the new plan?

Compared to the old plan, the new plan has the following features.

  • 同一性能プランにおいて値下げを行っています。


※料金についての詳細は サービスサイト を参照ください。

  • The following storage plans which were not provided can now be created similar to other zones.
    • SSD 40GB
    • SSD 1TB
    • SSD 2TB
    • SSD 4TB
    • Standard plan: 8TB
    • Standard plan: 12TB

Q. Approximately how much time does it take to copy a disk?

The amount of time is influenced by how busy we are when your inquiry is received. Estimated times are as follows.

  • 20GB plan: about 3 minutes
  • 100GB plan: about 10 minutes
  • 250GB plan: about 20 minutes
  • 500GB plan: about 40 minutes
  • 1TB plan: about 3 hours
  • 2TB plan: about 5 hours
  • 4TB plan: about 10 hours


Midday times are relatively free, so waiting time and execution time tend to be shorter.

Q. I currently use the 20GB Standard Plan. What plan should I migrate to?

We provide a 20GB SSD Plan which offers even higher performance at the same price. Please select the 20GB SSD Plan when copying a disk.

Q. Can I have SAKURA perform migration work on my behalf?

SAKURA internet will not perform migration work on behalf of customers.

Q. What will happen to remaining servers and disks after closure?

At the current time, we plan to delete remaining servers and disks.

Q. I use monthly license products. What should I do?

Please use the following contact information to inquire to our company regarding monthly license products. We will offset usage fees against the fees for the current month or the next month.

Q. I use Sophos UTM and Netwiser VE. What should I do?

We will provide information on migration procedures. Please contact our company’s customer support center.


Please send inquiries related to migration of old plans in Ishikari Zone No. 1 to the following customer service center.

SAKURA internet customer service center