- 📙 Audit Monitor
- 🔎 EpicAuth 4.x for Hyperdrive
- 🔍 EpicAuth 3.x for Hyperspace
- 📗
EPCS Solution
- High-Level Product Description and Features
- 📂 Release Notes
- Product Guide
- 📁 Enrollment Guide
- 🗂️
Installation and Configuration
- Upgrading from prior versions
- System Requirements
- Software Requirements
- HealthCast EPCS Server Installation and Configuration
- HealthCast EPCS SAML certificate conversion and deployment
- HealthCast EPCS Install on Citrix
- HealthCast EPCS Install on Enrollment Workstation
- Server Configuration for EPCS
- Creating Reports for SSO Audit Monitor
- Obtaining Records and Reports
- Solution Architecture
- Troubleshooting
- 📕
ExactAccess ('XA')
- ExactAccess 4.14.1
- ExactAccess 4.14.3
- SnapApp Extension
- XA Server
- Installation and Upgrading
- First Time Installation
- Start Here
- Target System Requirements
- Configure Directory Service
- Manual Configuration
- Example Output
- Domain Controller Round Robin
- Domain Controller Settings
- Administrative Role
- Cache Memory
- ProxCard Server
- Local Record Count
- E-Mail Configuration
- Remote Authentication Server
- Testing your Installation
- Passthrough (ProxAuth)
- Upgrade
- Service Configuration
- First Time Installation
- XA Server Administration
- Server Release Notes
- Installation and Upgrading
- XA Client
- Installation and Upgrading
- Customizations
- Workflows
- Configuration
- Logoffcleanup
- ADPWR
- Logging Optimization
- ExactAccess 4.14.0
- XA Client Administration
- HCI Deploy Publisher
- Prior XA Client Releases
- Release 4.12.3 Client
- Release 4.12.0 Client
- Release 4.11.6 Client
- Release 4.11.x Client
- Release 4.11.0 Client
- Release 4.11.1 Client
- Release 4.11.2 Client
- Release 4.11.3 Client
- Release 4.11.5 Client
- Release 4.11.4 Client
- Release 4.11. Client
- Release 4.14.0 Client
- Release 4.12.4 Client
- Release 4.13.2 Client
- How To
- Troubleshooting
- 📒
LYNX Proxcard Management
- Release Notes
- Installation and Upgrades
- Lynx Product Overview
- Move Badge Data From a QAS SQL Database to a Lynx Database
- Installation Checklist
- Lynx Release 1.7.0
- Solution Architecture
- QwickACCESS Client Compatibility
- Configuration Overview
- Step 1: Edit and run the PowerShell script
- Step 2: Edit the INI file
- Step 3: Configure the SQL Login
- Step 4: Run the SQL script to create the database tables
- Step 5: Configure the Lynx Service ‘Log On As’ Account
- Test the Configuration
- Install/Upgrade/Uninstall
- Administration
- Troubleshooting
- 💳
QwickAccess ('QA')
- QA Product Guide
- QA Introduction
- QwickAccess for IGEL
- QwickACCESS to Windows
- QwickACCESS Server
- QwickAccess for Dell ThinOS
- QwickACCESS for HP ThinPro OS
- QwickACCESS to VDI for Windows
- Licensing
- QA Troubleshooting
- QA & Lynx How-To
- QA Product Guide
- 💡
FAQ
- Badge FAQs
- Badges Not Registered When Pointing to XA 4.11.x Server
- Ignore New Badge - Currently Processing an Existing Badge Tap
- Badge Reader is Not Processing Badges After Upgrading to Windows+10 v1809
- Badge Tap Fails After Installing or Upgrading XA Client
- No Response from Badge Tap on Thin Client Connected to VDI
- XA is Not Recognizing RDR-7012AKU When it's Plugged In
- XA Client FAQs
- XAdrivemapping.exe Produces An Access Violation Error (intermittent)
- Apps Launched From XA Fail to Start as Expected
- Invalid XA User Caused by Forward Slash in AD Object Name
- HP Laptops - Display Going Black on XA Login Screen (Conextant Flow.exe)
- User Receives Desktop Error - Parameter Width is Insufficient - After Upgrading to XA Server 4.11.x
- Logoffcleanup PowerShell Script Opening in Notepad
- xaDriveMapping.exe Causes High CPU Usage
- Known Issues
- Frequently Asked Questions (FAQ)
- FAQs and Troubleshooting
- FAQ for AD-PWR
- XA Server FAQ
- How to determine the number of unique users based on badge (prox) usage
- 4.x How to configure Logoff Cleanup
- Virus Scanning Exclusions
- How to assign XA Toolbar Favorites using Roles
- Remove all badge records older the X days
- How to Customize the user display name on the XA Toolbar and Privacy Shield
- FAQ #1 How to configure policies...
- FAQ #2: How to configure the RunAs Connector
- FAQ #3: How to enable logging for xaLogoffCleanup
- XA Server/SQL FAQ
- Administration FAQs
- Known Server Issues
- Troubleshooting Topics
- Logging Overrides
- Anti-virus Directory and Port Exclusion Recommendations
- Stored Badge Password Cleared in Under 120 Minutes
- Audit Data From Client Systems is Not Being Written to Audit Database
- Users Unable to Authenticate Using Remote Authentication
- XA Server Event Log Error - XADATALAYER.CLSUSERS.GetUserRoles Error - Access Denied
- Remote Authentication
- XA Server Logging
- XA Server Stops Responding to Client Requests
- XA Server Troubleshooting Checklist
- Windows Profiles on XA Server
- Anti-virus Directory and Port Exclusion Recommendations
- hciserverconfigure Error After Adding Domain to NT DS Configuration
- Manual Configuration
- XA ProxCard Administrator
- Epic Hyperdrive FAQs
- Badge FAQs
- 💡 Best Practices All Products
- Support Bulletins
- 📖 Glossary
Database Backup and Recovery Planning
- Updated on 27 Mar 2023
- 1 Minute to read
- Contributors
Database Backup and Recovery Planning
With a maintenance plan, SQL Server® can automatically perform functions such as checking database integrity and performing database backups. Two maintenance plans are needed to schedule both Full and Transaction Log backups.
Full Database Backup Plan
Create a maintenance plan to perform a full database backup with a recurring schedule (recommended once per week). Each of the following server services require database access and should be included in the maintenance plan:
- ExactAccess (SSO)server database: xadb
- auditSERVER database: xaaudit
- ProxCard server database: hcproxcard
- HCI Deploy server database: hcideploy
Transaction Log Backup Plan
Create a maintenance plan that will perform transaction log backups once per hour or at a frequency that fits your database recovery needs. Backing up the transaction log saves transactions that occur in between full database backups and will allow you to recover data up to the moment of the last transaction log backup. Scheduling these to occur more frequently may reduce data loss in the event of a failure.