MEGA Administration : Administrator Guide : Managing Repositories : Managing Repositories : Managing logfiles
   
Managing logfiles
At repository creation, by default:
• the backup logfile is enabled (value Enabled).
• the repository log is not enabled (value Disabled).
Backup logfile
The repository is configured so that changes made by users are saved simultaneously in the repository and/or in a specific file called the backup logfile.
Backup logfile process
When opening a private workspace, the backup logfile process is as follows:
 
Step
User A...
Result
1
...connects to MEGA.
The MEGA workspace opens.
XXX.MGL logfile is created in folder \Db\RepositoryName\RepositoryName.Private Workspaces
of the environment directory.
2
...dispatches work.
XXX.MGL logfile is consolidated (*):
under YYYY-MM-DD_hh.mm.ss_XXX.mgl name
in "\Db\RepositoryName\RepositoryName.Log\ folder
...discards work.
There is no copy of XXX.MGL logfile.
3
...reconnects to MEGA.
A new private workspace opens.
XXX.MGL logfile of folder
RepositoryName.Transactions is reinitialized
XXX: Code of User A
YYYY-MM-DD: dispatch date (year-month-day)
hh.mm.ss: dispatch time (hour.minute.second)
(*): Consolidation consists of search and deletion of useless commands. For example:
When an object is created then deleted, the information is not saved in the consolidated logfile.
When a comment is created, then modified several times, only the final modification is saved in the consolidated logfile.
*To avoid overloading the RepositoryName.Transactions directory, MEGA recommends that you regularly archive the old logfiles.
Modifications made by a user to the system repository are logged in the same way.
If you have a problem
In the event of a problem on the repository, you can restore the last repository backup and import backup logfiles saved in the RepositoryName.Log folder from this backup up to time of the problem.
*It is highly recommended that you synchronize backup logfile archiving with repository backup.
Dispatched modifications are logged in a new repository log.
In the event of a problem on a user private workspace, you can copy the user backup logfile saved in the RepositoryName.Log folder, delete the current private workspace and import the backup logfile in a new private workspace.
Enabling the repository log
By default, the repository log is disabled for a GBMS repository and enabled for an RDBMS repository.
To keep a history of the actions performed on the repository after dispatch, you must activate the repository log.
*Enabling the repository log generates a large volume of objects. This volume can adversely affect MEGA performance, particularly at dispatches. It is not recommended with a GBMS repository.
To enable the repository log:
1. Open the Properties dialog box of the repository.
*See "Consulting and Modifying Repository Properties".
The repository properties dialog box opens.
2. Click Repository Log line and select Enabled.
The repository log is enabled.
The repository log lists all modifications made in the repository. It gives users a better understanding of actions dispatched in the repository from private workspaces.
Each time an action is executed, an occurrence of Change Item is created.
*A ChangeItem is a MetaClass corresponding to a change made in a MEGA repository.
A repository log comprises MEGA occurrences. These occurrences can be handled using MEGA APIs.
*See "Viewing the Repository Update Log".