When ExaBR backs up a vServer using LVM-based snapshots, it uses the swap space of the vServer to take the snapshot. However, if ExaBR finds enough free space in the default Volume Group (VolGroup00) it does not use the swap space of the vServer. This appendix describes how to increase the size of the default Volume Group (VolGroup00) of a guest vServer to ensure that ExaBR uses the unused space of the default Volume Group for the snapshot, and not the swap space of the vServer.
Note:
The procedure described in this chapter is relevant to vServers created by using the EECS 2.0.6 Guest Base Template only. Do not use this procedure to modify the disks of vServers creating using a Guest Base Template that is earlier than EECS version 2.0.6.You can increase the size of the Volume Group, by performing the following tasks:
Create a volume.
Attach the volume to the vServer.
Format and add the volume to the default Volume Group of the vServer.
To create a volume, complete the following steps:
Log in to the Exalogic Control BUI as a Cloud User.
From the left navigation pane, click vDC Management.
Under vDC Accounts, click the name of your account, such as Dept1.
The vDC Account dashboard is displayed.
Click Storage on the top navigation bar.
Click the Volumes tab.
Under Volumes, click the + icon.
In the Volume Name field, enter a name for the volume. For example, Volume1.
In the Description field, enter a short description.
Click Next.
Do not select the Shared option.
Set the size of the volume in GB. Oracle recommends setting the size of the volume to at least 2 GB.
Click Next.
The Volume Summary screen is displayed.
Review the summary, and click Finish to create the volume in your account.
You can attach a volume to a vServer as follows:
Log in to the Exalogic Control BUI as a Cloud User.
From the left navigation pane, click vDC Management.
Under vDC Accounts, expand the name of your account, such as Dept1.
All the vServers in the account are displayed.
Select the vServer (for example, vserver2) to which you wish to attach a volume.
The vserver2 dashboard is displayed.
From the actions pane on the right, click Stop vServer. Wait till the job succeeds in the jobs pane.
From the actions pane on the right, click Attach vServer Volumes.
The Attach vServer Volumes wizard is displayed.
Select the volume you wish to attach to vserver2.
Click the right arrow icon.
Click Next.
The confirmation screen is displayed.
Click Finish. Wait till the job succeeds in the jobs pane.
From the actions pane on the right, click the Start vServer button to restart the vServer.
Format the volume on the vServer, by doing the following:
Log in to the vServer as the root user.
Examine the current partitioning by running the following command:
# df -h
The following is an example of the output of this command:
Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 5.1G 3.3G 1.6G 68% / /dev/xvda1 99M 23M 71M 25% /boot tmpfs 4.0G 0 4.0G 0% /dev/shm
Examine the available physical volumes on the vServer by running the following command:
# cat /proc/partitions
major minor #blocks name
202 0 6145024 xvda
202 1 104391 xvda1
202 2 6040440 xvda2
253 0 5505024 dm-0
253 1 524288 dm-1
202 16 104857600 xvdb
/dev/xvdb is the newly attached volume.
Run the fdisk command, as shown in the following example:
Note:
The user input required at various stages while running thefdisk command is indicated by bold text.# fdisk /dev/xvdb Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. The number of cylinders for this disk is set to 13054. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) Command (m for help): p Disk /dev/xvdb: 107.3 GB, 107374182400 bytes 255 heads, 63 sectors/track, 13054 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-13054, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-13054, default 13054): Using default value 13054 Command (m for help): t Selected partition 1 Hex code (type L to list codes): 8e Changed system type of partition 1 to 8e (Linux LVM) Command (m for help): p Disk /dev/xvdb: 107.3 GB, 107374182400 bytes 255 heads, 63 sectors/track, 13054 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/xvdb1 1 13054 104856223+ 8e Linux LVM Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks.
Create a physical volume:
# pvcreate /dev/xvdb1 Writing physical volume data to disk "/dev/xvdb1" Physical volume "/dev/xvdb1" successfully created
Extend the volume group VolGroup00 with the physical volume /dev/xvdb1:
# vgextend VolGroup00 /dev/xvdb1 Volume group "VolGroup00" successfully extended
Verify that the volume group was extended successfully, by running the following command:
# vgs
VG #PV #LV #SN Attr VSize VFree
VolGroup00 2 2 0 wz--n- 7.5G 3.6G
The amount of free space appears under the VFree column.