3.7. Restore to Virtual Server(Red Hat Enterprise Linux 7 Restore in ECL 2.0)¶
Describes how to restore (restore) backup of Arcserve of Red Hat Enterprise Linux 7 virtual server created from the official template of Enterprise Cloud 2.0 environment to the virtual server of Enterprise Cloud 2.0 using Arcserve recovery media (LiveCD) I will.
3.7.1. Create restore destination volume¶
1.First of all, on the Enterprise Cloud 2.0 portal screen, create a volume with Red Hat Enterprise Linux 7 image to be restored.
Select「Virtual Serve」and「Volume」and Click「Create Volume」.
3.Enter / select the following and click on Create Volume.
- Volume Name：Enter your preferred name.
- Description：Enter if necessary.
- Volume Source：Official template equivalent to the OS type of the restoration source server
- Size(GB)：Choose a size equal to or larger than the size of the backup source.
- Zone／Group：Select according to the instance to be created.
4.On the Enterprise Cloud 2.0 portal screen, verify that the volume with the volume name created above is created in “Volume” under “Virtual Server”.
5.Disable this volume state.
Click “Edit Volume” of the created volume.
6.Uncheck “Bootable” and click Edit Volume.
3.7.2. Initialization of restore destination volume¶
1.Initialize the volume created above.
Create a CentOS instance for initialization work.(Since this CentOS instance is used only for initializing the volume created in the previous section, it is unnecessary after this work, so delete it.)。
「Virtual Server」and「Instance」and click「Create Instance」
2.Since the instance creation screen is displayed, fill in the setting items on each tab.
- Zone／Group：Select according to the created volume.
- Instance Name：Enter any instance name
- Flavor： Select from the tab(Since it is an instance used only for format, it may be the minimum configuration)
- Instance Boot Source：Choice ［Boot from image］
- Image Name：Official image(CentOS7.1)
Select the volume you created earlier.
Select the IP address to be set for this instance from the available logical network and set the IP address to the selected logical network.
5.After setting the above, click “Create Instance”.
On the portal screen “Virtual Server” - “Instance” screen, make sure the instance created above has been created.
6.If creation can be confirmed, start the instance and click on the instance name item to display the screen.
7.Enter the instance on the console screen of the instance.
8.On the console screen, execute “fdisk - l” and check the connected volume.
9.You can confirm that the volume is connected to /dev/vdb.
10.Initialize in ext3 format.「/sbin/mkfs.ext3 /dev/vdb」.
11.Shut down this instance if initialization is completed.
Please confirm that this CentOS instance has been shut down in “Virtual Server” - “Instance”.
After initialization, this instance becomes unnecessary, so delete it.
Click 「Delete Instance」on the CentOS server that was used for initialization.
12.Click 「Delete Instance」.
3.7.3. Image creation of recovery media¶
1.Create the Arcserve’s restore media (boot kit), which has been created based on another Arcserve’s function,
as an image on ECL2.0. At the Private Template/ISO on the ECL2.0 Portal screen,
which is placed in the Image Storage under the Virtual Server section, click [ Create Image ].
2.As the Create Image screen appears, enter the necessary setting items.
3.Enter and select the relevant information for the following items required and click [ Create Image ].
- Name: Enter if necessary.
- Image File: Select the Arcserve’s restore media (boot kit) which has been created with another Arcserve’s function).
- Format: Select “ISO – Optical Disk Image”.
3.7.4. Create a temporary instance for restore¶
1.Then, create a restore instance. (Please make sure that this restore instance is a temporal and created to deploy the restore image which has been created on the Arcserve for restoring. Therefore, it is different from that of the restore destination.)
An example of creating an instance from the Web portal when the instance for restoration is 1 volume is an example.
When restoring multiple volumes, please refer to the method below and create an instance for restoration.
2.Click Virtual Server - Instance - Create Instance.
3.Create Instance screen appears, enter necessary information for each tab.
In the Details tab, the items shown under the picture are specified.
- Zone/Group: Select an option suitable for the volume created.
- Instance Name: Enter if necessary.
- Flavor: Enter if necessary (as this instance will be used for restoring only, minimum configuration is required.)
- Instance Boot Source: Select “Boot from image”.
- mage Name: Select the Arcserve’s restore media (boot kit).
4.Enter necessary information in the Data Volume tab.
Select the volume created in advance (the restore destination volume).
5.Then, move to the Networking tab.
Select an IP address from the pull-down list of the Available Logical Networks that will be assigned to this instance,
and specify the IP address at the Selected Logical Networks.
6.Then, click [ Create Instance ].
Confirm that the instance created above is shown on the Instance screen, which is accessible from the Virtual Server section on the ECL2.0.
1.After confirming the instance has been created, launch the instance. Click its name so as the Instance screen to launch.
2.Via the Console tab, move to the Instance Details section.
3.As the Instance Details screen appears, the Arcserve’s bare metal recovery screen like the picture below will be displayed automatically.
4.Then, move to following screen. Pless Enter key after click on the screen.
5.Move to inputting command screen.
6.At this screen, configure IP address to the instance.
Make sure IP address is not used by using ifconfig command.
Following example shows that eth0 interface is available and not IP address is assigned.
7.Configure IP address to restore server (booting from restore media) by using ifconfig command.
In this exaple assign IP address to eth0.
8.After configuration, make sure the server can connect to server and backup data location on the same logical network.
9.Once you can verify accessibility, quit terminal by exit command.
10.Then move to previous screen and you need to verify the IP address assigned like below and the URL is displayed.
You should note this URL.
11.Open browser and access to the URL displayed above.
12.Click on [Restore] and select [Bare Metal Recovery(BMR)].
13.Click on [Next].
14.Select the backup data location. In this example, select “CIFS share”.
15.Input IP addrees of backup data storage and folder path.
※”￥” need to be input “/”
After input, click on “→”
16.Authentication to connect the server which store backup data will be required. You need to input username and password, then click on “OK”.
17.Once connection has been established, move back to previous screen. Then click [Next]
18.Select IP address of target server.
19.Click on [Next]
20.Configure each settings diplayed following screen.
- MAC/IP Address：IP address server of restore server
<Target Machine Settings>
- Host Name：Host Name you wish to set to restore server
- Network：Static IP
- IP Address：IP address set to restore server finally.
- Subnet mask：Subnet mask set to restore server finally.
- Default Gateway：Default Gateway set to restore server finally.
21.After input these value, click on [Next]
22.Select [Run Now] on “Set Start date and time”, then click on [Next].
23.Displayed Summary, then click on [Submit].
24.Move back to previous screen and make sure restore job created on [Job Status] tab.
Restore procedure will start.
In Arcserve UDP 6.5 update 1, when restoring BMR on Redhat 7.1 on ECL 2.0, it may fail with the following error.
“Disk driver available on target machine could not be found.” “Could not create disk layout for restore.”
Since a correction patch for this event is provided by Arcserve, please apply it by the following method.
25.Once restore completed, connection to management screen will be lost. Then click OK to exit.
Restore backup files to empty volume has been completed.
3.7.6. Create Instance¶
1.With this volume, create a new instance (restore server) based on the volume.
On the Instance screen of the Virtual Server section on ECL2.0, click [ ▼ ] shown next to “Start Instance” for showing the pull-down list.
2.From the pull-down list, select “Shut Off Instance”.
The temporal instance, which has been created just for this restoring action, will not be used anymore. So please delete it if necessary.
3.Click [ ▼ ] shown next to “Edit Volume” at the right-end of the Volume screen that controls the volume created above
(the volume restored on the Arcserve) so that the pull-down list appears. Select and click“Manage Attachments”.
4.As the Volume Attachments screen appears, select and click “Detach Volume” to disconnect with the volume.
※When the instance isn’t shut off, the volume cannot be detached.
5.Edit the volume created above (the volume restored on the Arcserve above.)Click [ Edit Volume ].
6.At the Edit Volume screen, check “Bootable” and click [ Edit Volume ].
7.Create a new instance (restore server).
As the Create Instance screen is displayed, enter necessary information for each tab.
8.The following items are required at the Details tab.
Enter and select relevant information for the following required items and click [ Create Instance ].
- Zone/Group: Select an option suitable for the volume created.
- Instance Name: Enter if necessary.
- Flavor: Enter if necessary (the resource size which you want to restore)
- Instance Boot Source: Select “Boot from volume”.
- Volume: Select the volume restored above.
9.Then, move to the Networking tab to configure further.
Select an IP address from the pull-down list of the Available Logical Networks that will be assigned to this instance, and specify the IP address at the Selected Logical Networks.
10.Then, click [ Create Instance ].
Confirm that the instance create above is shown on the Instances screen, which is accessible from the Virtual Server section on the ECL2.0.
11.Via the Console tab, move to the Instance Details section.
12.Confirm that the OS is running properly. Then, perform necessary configuration
There may be the case that IPaddress and routing settings take over from previous environment, Therefore please check configuration.
That’s all for restore.