EntraPass Database Backup Checklist

01

Why the database deserves its own plan

EntraPass is designed to centralize users, doors, events, and multi-site access activity. Losing or damaging that configuration can turn a server problem into a much larger operational event.

A strong backup routine protects against hardware failure, operating-system problems, accidental changes, failed upgrades, and the simple fact that an old local backup may not be available when the server is unavailable.

02

A useful weekly backup checklist

Use a consistent schedule and assign a responsible person or support provider. Keep the procedure documented for the exact EntraPass edition and environment.

• Create the backup using the appropriate EntraPass procedure for the installed version.
• Copy the completed backup away from the EntraPass server.
• Use a protected cloud or offsite destination with access limited to authorized personnel.
• Confirm that the file was created, has a plausible size, and can be retrieved.
• Record the backup date, EntraPass edition and version, and server name.
• Keep more than one recovery point when policy and storage allow.

03

Before an upgrade or migration

Create a fresh backup immediately before major changes—even if the weekly job recently completed. Record licensing information, connected workstations, controller communications, integrations, and the current server configuration.

Do not treat a copied program folder as a verified application database backup. The safest process is version-specific, documented, and tested with a recovery plan.

04

How a support plan helps

Silver, Gold, and Diamond support plans include a weekly cloud backup of the customer’s EntraPass database. This adds an off-server recovery copy to the customer’s own local protection and change-control process.