Secure Global Desktop 4.40 Administration Guide > SGD Servers, Arrays, and Load Balancing > Backing Up and Restoring an SGD Installation
This page describes how to back up an SGD installation so that you can repair SGD in the event that a component or an entire installation becomes damaged. Before using the procedures on this page, it is helpful if you are familiar with the layout of the SGD installation.
This page includes the following topics:
To be able to restore an SGD installation or to be able to repair some individual SGD components, you need a full backup.
While making the backup, do not run any command-line tools or use the SGD Administration Console. It is also best if you shut down the SGD server while making the backup. However, if this is not possible, do it when the server is least loaded.
To back up SGD:
tarantella archive command.
SGD also uses the following configuration files which only need to be backed up if you are using them and you have modified them:
/etc/ttaprinter.conffile - this contains the lpr defaults
/var/ace/datafiles - these contain RSA SecurID settings
For the purposes of restoring a damaged installation, SGD can be divided up into the following components:
The binaries, scripts and template files are only modified as part of an installation, patch or custom engineering work. These do not change very often.
You can restore these files from a backup or another installation, as follows:
The Login Scripts control the interaction between SGD and the application servers (for example, by logging a user in).
How you recover login scripts depends on whether or not you are using customized login scripts.
If you are not using customized login scripts, you can restore these files
from another installation, a backup, or from the
If you are using customized login scripts, you must only restore these files from a backup.
The login scripts are in the
Server configuration covers all the properties for an SGD server that are not shared with the other SGD servers in the array, such as the server DNS name and server tuning.
As this configuration is unique to a particular SGD host, it must only be restored from a backup taken from that host.
The server-specific configuration is in the
If you are using SGD security services, you must restore the following:
Global configuration covers all the properties that are the same for all the SGD servers in the array, for example the names of the other array members.
To restore the global configuration for an SGD server, you must only restore from a backup of the primary.
The global configuration is in the
The local repository (formerly called ENS) is shared across all SGD servers in the array. This is the organizational hierarchy that contains all the information about users, applications and application servers. This information changes very regularly.
Restore the local repository from the backup of the primary SGD server.
The local repository is in the
By default, SGD archives its log files each week at 4am on Sunday using a cron job.
If the root user's crontab becomes corrupt or the archiving does not take place,
tarantella setup to restore the default setting,
or change the time and day that the archiving takes place.
The log files are archived under the
When you install SGD, it configures an SGD printer queue.
If the print queue is not present, you can restore it using either of the following methods:
The printer queue is in the
The configuration of the SGD Web Server, web services and the webtop is unique to a particular SGD host and must only be restored from a backup taken from that host.
The configuration for the SGD Web Server is in the
You might also have web server password files, which can be stored in other locations.
The configuration for SGD web services is in the
The files used for the webtop are in the
If you are unable to restore a damaged SGD component or you are unsure about the extent of the damage to your system, you must do a full restore of your SGD installation. To do a full restore, you must have a full backup.
To do a full restore:
# tarantella uninstall --purge
Note If this fails, you might have to manually remove the SGD package.
rpm -e tta command on Linux platforms and
pkgrm tta command on Solaris Operating System platforms.
# rm -rf /opt/tarantella
This installs the printer queue, rc scripts and package database.
# rm -rf /opt/tarantella
Note Make sure you restore from the server's backup and check the DNS name of the host has not changed.
Copyright © 1997-2007 Sun Microsystems, Inc. All rights reserved.