The SnapshotCM server manages the SnapshotCM archive and database files where project files and attributes are stored. You only need one SnapshotCM server to support all users in your organization.

Performance

The SnapshotCM server minimizes use of network resources, and optimizes database access so that users don't have to wait. As more users or files are added, user machines will not require upgrades.

The SnapshotCM server takes advantage of system resources so large customers can obtain best performance by dedicating a fast machine with significant memory and a high-speed file system to their SnapshotCM server. Smaller customers will obtain good performance from a shared system.

Administration

The SnapshotCM server requires minimal administration to perform backups.

Requirements

The SnapshotCM server uses TCP/IP for client communications. No special hardware is required, other than local disk for archive and database files.

Supported Platforms

The SnapshotCM server is available for Unix and Windows NT/2000 or newer systems.

Disk Space

The SnapshotCM server manages the archive and database files. The archive files consist of your file revisions, typically stored in RCS. Larger files may be compressed or stored as is by SnapshotCM. The size of the archive files is, of course, dependent on your files.

The database files store all other information about your projects. Their size is also somewhat data dependent. For example, longer history comments take more space than shorter ones. As a rough guide, each file or directory takes about 200 bytes, and each revision takes about 140 bytes plus 1.5 * the size of the comment text. Snapshots require space for all file or directory attributes that are unique to a snapshot, perhaps an additional 200 to 400 bytes per file.

An example server managing 100 snapshots, 5000 files and directories in 30,000 revisions has a 10 MB database, plus 141 MB in the archive. As you might expect, the biggest variable is your data.