Total Secure Configuration

---

Use Instant Secure or Total Secure to manage the movement of database backups and journals.

The management user interface is tied into the Secure Console. Use the Secure Console to view essential setup information.

Secure management is separated into one server process and two client workstation processes. These are described below.

GTManagementDBService Application

This process is started with the Services (from the ServiceStarter application) on the primary and any secondary servers. It:

• Provides SDE messaging to enable for persist handling on any secondary server(s).
• Handles queuing of database backup info for all backup management settings.
• Handles queuing of journal switches for journal management settings.
• Audits the Instant Secure environment at specified intervals.

Note: The server maintains the settings queue of backups and the last journal number transferred. So that if the movement applications are not running when started these will transfer the correct instances.

GTManagementBackupCopier Application

When setup on another workstation, the application:

• Copies backups from the server to some specified root directory.
• Verifies the backup using jdbutil.
• Maintains a user definable number of saved backups.

GTManagementJournalCopier Application

When setup on another workstation, the application:

• Copies journal from the server to some specified root directory.
• Verifies the journal using jdbutil.

Separate processes were defined to handle the journal and the database movements to potentially handle for these concurrently.

Configuring Greentree Desktop Secure Management

To configure Greentree Desktop Secure Management:

1. Copy the Greentree Desktop \bin folder to the workstation.
2. Copy the .ini file from the primary server.
3. Create an icon pointing to the server database by referencing the server .ini file. For exampel:

   C:\yourpathworkstation\bin\jade.exe path=c:\yourpathserver\System ini=c:\yourpathworkstation\PRIMARY.ini schema=GreentreeManagementSchema app=GTManagementConsole server=MultiUser

4. Start the Management Console which points to the database server.

Greentree Secure maintains the management settings from in the Secure Console's Backup Management extension.

The settings are per workstation. It is expected that the workstation is a different computer than the database server.

Greentree handles running the copier processes connected to a secondary or a primary database server.

The settings table is if the settings are maintained. Create a new setting by clicking the New icon on the Management extension. Select the workstation from the combo box to view the setting for that workstation.

Settings

Workstation

The Windows name of the workstation.

Instant Secure DB Name

If within an SDE, you can select the database system the process is to be run from.

Active

If the setting is active or not. Only active settings are used for movement and register for any notifications.

Admin email to addresses

Warning and errors is sent to these addresses. Addresses must be delimited with a semi colon (;).”

Admin email from address

All warning or error emails are sent from this address.

Copy journals to

The folder if the journals are moved using a UNC path or mapped drive.

Verify journals in

This should point to the client version of the folder set in the Copy journals to field.

Expected journal interval (every)

The expected interval between journal archives. If this is not met, a warning is sent to the administrator email addresses.

Last journal movement at

This shows the last time a journal movement occurred.

This field is read only.

Copy backups to

The folder if the database backups are moved using a UNC path or mapped drive.

Verify backups in

This should point to the client version of the backups.

Expected backup interval (every)

The expected interval between backups. If this is not met, a warning is sent to the administrator email addresses.

No of backups to keep

The number of backups to keep. After a successful backup verification Greentree Desktop deletes any old backups to meet this number.

Last backup movement at

This shows the last time a backup movement occurred.

This field is read-only.

Archival Recovery

Archival recovery must be configured so the journals files are not deleted when the transactions have been applied to the database.

Mandatory

• Transaction log volume must be mirrored, and ideally duplexed (dual controller).
• Transaction logs must be on a separate physical disk subsystem or volume to that hosting database files.

Recommended

• Database files should be on a fault-tolerant disk system.
• Configure separate physical disk subsystem for disk-resident transaction log and database backups.

Relevant Initialisation parameters

The EnableArchivalRecovery parameter in the [PersistentDb] section of the JADE initialisation file is used to enable or disable the archival recovery option.

This parameter must be selected before the first archival backup is created, so that the control.dat database control file contained in the backup is initialised in the correct way.

The JournalArchiveDirectory parameter in the [PersistentDb] section of the JADE initialisation file specifies the fully qualified directory for the location of archived transaction journal files for recovery purposes. If you do not specify a value for this parameter, the JournalRootDirectory\archive directory is used.

The JournalCloseAction parameter in the [PersistentDb] section of the JADE initialisation file specifies when a journal file that is no longer required is closed and released. When the EnableArchivalRecovery parameter is set to the default value of false, the specified close action is ignored and unwanted journal files are removed. If you have not specified a directory in the JournalArchiveDirectory parameter, the \archive directory is a subdirectory of the directory specified in the JournalRootDirectory parameter.

How to Enable Archival Recovery for Total Secure

Archival recovery is enabled using settings in the database .ini file. The settings should only be updated when Greentree Desktop and it's services are shut down or stopped on the server. An online backup should be initiated immediately after making any changes to this section and before re-starting the services.

EnableArchivalRecovery=true

This must be set to true to enable archival recovery.

JournalRootDirectory=d:\system\archivelogs

This is the location the logs are stored (whether you are using archival recovery or not). This path should point to a drive that is different to the server path (though it must be on the same machine). For example, if Greentree Desktop is on driver C of the machine, point the log file to driver D of the same machine.

JournalMaxSize=6M

This is the maximum size the log file should get to before it creates a new one. The recommended setting is 12M, however in the event of a disk failure, this may represent a significant amount of data loss. An assessment about the file size should be made on a site by site basis.

JournalArchivalDirectory=e:\Gtree\Logs

This is the location Greentree Desktop will place the above log files into when the have reached the maximum size. These is used to roll the data forward from a backup in the event of a failure.

Note: You should include this location in the Windows backup policy as these files are not backed up by the online backup (only the current log is).

JournalCloseAction=Move

This setting determines what happens to the log files when they have reached their maximum size:

Note: If you turn archival recovery on when it has not been used previously, you must change the ini settings while Greentree Desktop is shut-down, and re-start Greentree Desktop before the new settings takes effect. The next backup taken will operate with archival recovery in use.

Archival Transaction Log File Backups

You must maintain backups of the archival transaction logs. Total Secure automates this process.

When archival recovery is in use, the database files from the last backup and all the archived transaction logs created since the last backup must be used in the recovery process. You should protect against media failure using Total Secure to copy logs to a different server, offsite backups of the backup and log files should also be done.

---