Repository Physical Backup
In event of a problem, you must have a valid and recoverable data backup.
A physical backup consists of copying the files of a repository from their original location to another one.
Data is stored at HOPEX environment level. Data to be backed up varies according to repository server type.
Backup frequencies
For a HOPEX environment used by an active project, HOPEX recommends:
• daily backup of the environment
• backup before any major data update
Example: system database customization, data reprocessing, CP/RP update of HOPEX data.
• that you keep:
• daily backups of the last 30 days
• monthly backups of the last 12 months
Whatever your repository server type, MEGA recommends cold backup (no MEGA user should be connected).
In SQL server type mode, hot backup is possible.Elements to be backed up
Identify environments that require regular backup.
Example: design environment.
From the environment folder, you must back up complete folders:
• Db
• SysDb
• Mega_usr
For repositories in format:
• GBMS
Db and SysDb folders contain all EMA, .EMB, .EMS and EMV files of the system database and repositories.
The daily physical backup should include at least the .EMB, .EMS and .EMA files of the GBMS repository.• RDBMS
Db and SysDb folders contain an .EMV file and (respectively) an .EMO .EMQ .EMY file that points to other folders that you must back up:
• for Oracle:
system database and repository schemas.
• for SQL Server:
system database and repository databases.
GBMS format repository recommendations
To obtain a valid backup, ensure that files are not accessible during backup:
1. Access environment options.
2. In the tree, select the Options\Repository folder.
3. In the right pane, for option Authorize dispatch for the environment, select "Prohibit".
Elements that can be excluded from the backup file
To save space and time it is not necessary to back up the complete content of the environment folder. You need not back up for example folders that contain:
• user work files
These files are contained in the SysDb\USER and Db\USER folders.
• work files linked to the Administration application
These files are contained in the SysDb\WORK and Db\WORK folders.
• lock files:
• Systemdb.Lock contained in SysDb folder
• RepositoryName.Lock contained in Db\<RepositoryName> folder
Other elements to be backed up
MEGA recommends that you back up folders concerning:
• configuration:
the Cfg folder (in the HOPEX installation directory) containing the megasite.ini configuration file.
• licenses:
the file containing licenses (.Must or .ELF).
(Optional) You can back up folders concerning:
• your java customization:
lib_usr folder (in the java folder of the HOPEX installation directory)
• your installation customization:
Mega_Usr folder
• your delivered data
in the HOPEX installation directory, the following folders:
• Document, which contains shared documents
• Intranet, which contains the Web sites generated
• Approve, which contains detached documents.
Elements that could be useful to back up
You may need to back up:
• private workspaces in progress
• technical data modifications in progress
To back up private workspaces in progress:
copy the "RepositoryName.Transactions" folder in the repository folders tree.The USER and WORK folders contain the work documents of users.To back up technical data modifications in progress: