Previous Topic: About Auto ArchiveNext Topic: Configuring Non-Interactive Authentication for Auto Archive


Database Move and Backup Strategy Flowchart

You can perform both event collection and reporting on each CA User Activity Reporting Module server or you can dedicate different servers to collection and reporting. If you dedicate servers to collection, then automating hourly moves from collection servers to a reporting server is required; otherwise, it is not applicable. If you have no dedicated server roles, interpret the flowchart references "from reporting to remote storage" as "from a non-dedicated CA User Activity Reporting Module to remote storage."

A backup strategy implies having two copies of each database, where one is considered the backup. You can achieve this goal with or without auto archiving to a remote storage server. The backup strategy with auto archive results in the original databases on the remote storage server and the backups in an off-site location. The backup strategy without auto archive results in the original databases on the CA User Activity Reporting Module server and the backups on a remote storage server. Whether you can store the original databases on the CA User Activity Reporting Module where they were initially archived depends on the available space for long-term storage and storage policies. If these criteria are met, the decision rests on personal preference.

Criteria for auto archiving to a reporting server and decision to automate move to storage server or perform manual copy to storage.

More information:

Manually Backing Up Archived Databases

LMArchiveā€“Backup/Restore Tracking

Event Log Store Settings in the Basic Environment

Configuring Non-Interactive Authentication for Auto Archive