Back up and restore IBM SmartCloud Entry
To protect your IBM SmartCloud Entry data, you must back up critical files in case the server enters an undesired state. Before you back up your data, determine the circumstances in which you intend to restore your data.
Backing up server data for recovery
There are two kinds of data to back up. The first set of data is for server configuration and the second set of data is used by the database. When you consider what data to back up, review both sets of data.
Note: This procedure backs up IBM SmartCloud Entry only. It does not back up the underlying virtualization managers, such as VMware vCenter or storage devices.
1. Stop the IBM SmartCloud Entry server to ensure that the backup data is complete.
2. Back up the following configuration files.
v The .SCE31 folder.
v In the installation folder: skc.ini
Note: If any values are changed in this file, you must back up the updated file after you change default values.
A copy of all these files is required to ensure a complete backup.
Backing up database data for recovery
All of the database data that is related to IBM SmartCloud Entry users, such as projects, networks, instances, images, are stored in the database. The backup procedure is different depending on the database that is being used.
1. Stop the IBM SmartCloud Entry server to ensure that the backup data is complete.
2. Follow the instructions that pertain to your specific database.
Derby database
If you are using the Derby database, backup the .SCE31/database folder that stores all the database data.
DB2 database
If DB2 is configured, backup the database in the DB2 server. For more information about how to back up the DB2 server, see the DB2 Information Center.
Note: Ensure that the information referenced matches the version of DB2 that you are using.
If not, reference the appropriate support documentation for similar information.
Restoring the server
To restore a backup of the server and the Derby database, copy all the saved files back to the original server. After the copy is complete, start the IBM SmartCloud Entry server.
If you are using the DB2 database, there are some extra steps.
1. Ensure the path that is specified in the database.properties configuration file, by the property database.db2.path, is correct.
© Copyright IBM Corp. 2013 149
# If db2 then the path to the DB2 dtatbase needs to be provided. This will be ignored for derby.
#database.db2.path=//localhost:50000/cfs:.
Essentially, creating a backup of the entire home folder and skc.ini file ensures a complete backup of the IBM SmartCloud Entry server. Copying the files back to their original location restores the data.
Considerations for backing up a IBM SmartCloud Entry appliance
To back up a IBM SmartCloud Entry appliance, use the existing snapshot or capture capabilities that are provided by the underlying virtualization manager. First, ensure that all services are turned off before you attempt to take a snapshot of either Hyper-V or VMware. If you are using KVM, the process depends on your existing infrastructure. For example, if SAN storage is being used, use the FlashCopy® function to take a snapshot of the appliance disks.
Important: There is a limitation to be aware of when you use this best practice. Any incremental data that occurs after backing up the IBM SmartCloud Entry server is lost after you restore the server.
Therefore, some functions might not work as expected. For example, consider the circumstance where you create an instance after you complete a capture, and then you restore the server. The IP address that was assigned to the instance (after the backing up) is still available in the IP address pool. It might be assigned to another instance.
Using the screen command
The screen command can be used to start or shut down the IBM SmartCloud Entry server or to access the OSGI console when the server is up and running when running Linux.
For example, enter screen and then run the command to start the server. After the server is started, type ctrl+a, then d to disconnect and leave the IBM SmartCloud Entry server running,
To get back to the IBM SmartCloud Entry OSGI prompt to perform other actions, such as enabling additional logging, enter screen -r.
Using the nohup command
On AIX or Linux, if you start a process from the command line and then log off, the processes you started are generally terminated, even if you spawn them as background processes, because each process is sent a hang up signal (SIGHUP). The nohup command allows you to start a process with the hang up signal disabled so that the process is not ended when you log off.
The nohup command is used frequently for starting services, such as ssh daemon or DB2 instances.
For example, to start IBM SmartCloud Entry as a background service, run the following command:
nohup /opt/ibm/SCE24/skc -nosplash < /dev/null > /dev/null &
The options in this command include the following:
-nosplash
Prevents the process from displaying a splash screen.
< /dev/null
Disconnects the process from terminal input. This option can prevent the process from entering a stopped state as can sometimes happen when started from the command line on AIX. This option is not needed when starting the command from a shell script.
> /dev/null
Redirects the OSGI console output. For example, you might want to redirect the output to a log file.
& Runs the command as a background process.
Deploying 500 virtual servers to a VMControl cloud in a 24 hour period
If you plan to deploy more than 500 virtual servers to an IBM Systems Director VMControl cloud in IBM SmartCloud Entry within a 24 hour period, you must update the deployment.properties file in the home directory.
Complete the following steps to update the deployment.properties file so that only one lscustomization call is completed during the deployment request.
1. Locate the deployment.properties file for IBM SmartCloud Entry. By default, the deployment.properties file is in the /root/.SCE31/deployment.properties path.
2. Edit the deployment.properties file so that the
com.ibm.cfs.deployment.static.appliance.customizationsetting is true. See the following example:
#True to use the set of static customization properties that are configured for an appliance. The only
#way to get updated properties from the cloud when this is true is for the administrator to configure
#the appliance. Note that the static properties are stored in the locale of the initial requester
#which may not match the current user. When this is false, the default, the customization properties
#are retrieved from the cloud on each deployment.
com.ibm.cfs.deployment.static.appliance.customization=true
3. After you make the update to the com.ibm.cfs.deployment.static.appliance.customization setting, restart IBM SmartCloud Entry to enable the setting.
Chapter 15. Best practices for using IBM SmartCloud Entry 151