The first backup option that will be demonstrated is a basic process of shutting down the TM1 server, saving the data, and running a backup of the data directory.
The advantage of this method is simplicity in the initial system configuration – no changes need to be made to the configuration file. Also data assurance is guaranteed, no one will be entering data while the system is down and the backup is executing. Additionally, audit logging can be enabled via the TM1 configuration file when using this method for backing up the TM1 system.
The disadvantage of this method is that the TM1 server must be taken offline and shutdown for a period of time. This may or may not be a problem; it will depend on the uptime requirements of each organization. Also, any data entered between backups may be lost if the data directory files become corrupt.
1. Shutdown the TM1 Server and respond "Yes" to the "Do you want to save changes" prompt. This will save any changed data in RAM to the data directory.
2. Backup all files in the TM1 Data Directory. There are a number of ways that this can be accomplished using various third-party products or operating system commands. There are also many ways to automate this process using third-party tools and schedulers. In MS-DOS a simple XCOPY command with the appropriate switches will copy all of the TM1 Data Directory files and sub-folders to another location (backup folder, drive, or other media).To verify the location of the TM1 Data Directory, view the TM1 Configuration File: tm1s.cfg.
The Data Directory will be listed next to the DataBaseDirectory item. This is the directory that should be backed up. Be sure to include all sub-directories in the backup.
For many organizations TM1 is a critical application that must be maintained as a 24x7 enterprise application. In these cases, it is not acceptable to shutdown the TM1 Server to perform a backup. TM1 provides organizations the ability to maintain 24x7 uptime and also perform regular backups of the Data Directory. Several changes will need to be made to the default settings of the TM1 Server configuration file (tm1s.cfg) in order to perform a live backup successfully.
The advantages of this method are ease of administration, 24x7 system uptime, and automation can be created within TM1 using Turbo Integrator and Chores. The disadvantages are that there is initial configuration that must be performed and the potential exists for lost data between "Saves" if the Data Directory files become corrupt.
The following steps must be performed in order to run backups from a Live TM1 Server:
1)
Modify the default TM1 Server Configuration file (tm1s.cfg).
a.
Point the Log Files to a location other than the Data Directory by inserting the "LoggingDirectory" parameter in the configuration file. By default, TM1 writes log files to the Data Directory. Since these files will be open and active while the TM1 Server is running, any attempt to back them up will result in a file sharing violation and may cause a backup process to fail.
b.
Verify that the AuditLogOn parameter is set to 'F'. This is the default setting, but if the AuditLogOn parameter is set to 'T' then, as in the case above with the transaction logs, open and active files will be in the Data Directory. Attempting a backup will cause a file sharing violation which may result in a backup failure.
Note the sample tm1s.cfg file below which has been modified to allow for live backups from the TM1 Server.
--
BI CENTRE
http://cognos8help.blogspot.com
