An XA/XD Site stores information in 3 DBs
- Site DB
- Config Logging DB
- Monitoring DB
Site DB contains the following information
- Site configuration settings
- Published resource information
- Active session information
- Policies configured within Studio
- Site Administrator Permissions
Config Logging DB contains historical information of:
- Site configuration changes
- Administrator activities (who/where/which/status)
Monitoring DB collects
- Session and connection info (can be reviewed in Citrix Director)
- Data leveraged by Director.
Separation
- Separation is recommended in case that you would like to store historical records of more than 7 days (size considerations).
- Site should be on one separate DB Server while the other 2 on another server or even on separate servers as well.
- If Separation is considered, this has to be done as soon as the Site is created. After move, data in initial DB will not be imported in new DB.
- Admins can tailor de backup method and frequency separately
- Decreases corruption risks.
- Improves Site DB performance.
- Individual DB Sizing. Monitoring DB is normally the largest while Config logging is the smallest.
Separation instructions
- Go to configuration in Studio
- Highlight the Logging DB and select „change database”
- Enter the new DB location and select ok (if DB does not already exist, it will be created, just like setting it up for the first time. Ofc, SQL permissions should exist)
DATABASE CRITICALITY
Failure impact is different for each of the 3 Dbses, with Site DB being the most important.
- SiteDB Failure = production impact
- Users cannot start new sessions or reconnect to existing ones.
- Connection Leasing or Local host cache feature provides temp solution, allowing users to broker apps and desktop that were recently launched.
- Administrators will not be able to make changes through Studio nor make use of the Director functionality
- Config DB Logging Failure = no production impact
- Changes made to site will not be tracked.
- If logging is mandatory, administrators will not be able to perform any changes to the Site
- Monitoring DB Failure = no production impact
- Administrators cannot view any historical data
- Director will not be able to be used since it is heavily reliant on Monitoring DB.