Backup and recovery concepts
Disk space shortages, hardware failures, and system crashes might corrupt Helix Server files.
Versioned files | Checkpoints and journals |
Database |
||||
---|---|---|---|---|---|---|
Versioned files The By default, the versioned files for a given depot are located in a tree of directories beneath this subdirectory. For an alternative location, see The server.depot.root configurable section of Set a depot location. |
The checkpoint
|
The database |
||||
On a regular schedule, make backups of the versioned files, checkpoints, and truncated (numbered) journals. Always back up the versioned files with the standard operating system backup commands after checkpointing. It is good practice to keep one month of checkpoint and journal files available. |
Do NOT use your operating system backup utilities to back up the db.* files because such utilities often lock files and interfere with Helix Server operations and performance. |
Anti-virus software
We understand and respect that each organization has its own requirements and policies about anti-virus software.
Consider whether your organization might prefer to use anti-virus software on client machines rather than on the server machine running Helix Core Server. Anti-virus software might:
-
lock metadata files and thereby interfere with normal Helix Server operation
-
degrade server performance by competing for system resources.
If your organization determines that anti-virus software must be used on the server machine running Helix Core Server, consider whether it is feasible to exclude the scanning of db.* metadata files and live scan operations.