Agent Guidance System Backup
There are two elements of a Agent Guidance System that will typically need to be backed up: the website(s), and the Microsoft SQL Server database. The Redis database does not store persistent data, and doesn't need a backup scheme.
The Agent Guidance System does not include any type of automatic backup or rollback facility internally.
If no manual configuration changes have been made to the Agent Guidance System outside of the Agent Guidance website GUI, then there are no website elements that require backup.
For example, if configuration changes have been made to either the Agent Guidance website's IIS config file (\\wwwroot\web.config), or to the global custom JavaScript file (\\wwwroot\lib\custom.js) file, then these will require backup. If any customisations have been deployed to the Agent Guidance website, these will need specific consideration.
Please consult your Agent Guidance vendor if in doubt.
In the below file locations, the \wwwroot\ folder refers to the high-level Agent Guidance website folder on your IIS Server, which can be identified from the IIS Site location path. The wwwroot folder is within the Agent Guidance instance folder created during the installation routine at the specified location.
|
Item To Backup
|
Path
|
|
Website IIS config file (web.config)
|
[Agent Guidance Instance Install Location]\wwwroot\web.config
|
|
Global Script Custom JavaScript File (custom.js)
|
[Agent Guidance Instance Install Location]\wwwroot\lib\custom.js
|
|
Global Script Custom Stylesheet (script.custom.css)
|
[Agent Guidance Instance Install Location]\wwwroot\stylesheets\script.custom.css
|
During install, a
custom.js file is created rather than
custom.js, and it is inactive until the is removed. Details on usage of the Global Custom JavaScript File can be found in our
Custom.Js Knowledge Base article.
If any standalone or supporting files have been added to the Agent Guidance installation location, for example custom webpages to be used as
Desktop Tabs, then these will also require backup.
Microsoft SQL Server Backup
The Agent Guidance Microsoft SQL Server database will need regular backing up, as per any other Microsoft SQL Server database.
We recommend that Production systems are run in Full transaction logging mode, with Development and Testing systems run in Simple transaction logging mode. The method and frequency varies by business need and resources availability, as does the requirement of storing backups off server, alternative SAN or off site.
We recommend Production system backups schedules are configured within the range shown below:
|
Highly Resilient
|
Minimal Resource Usage
|
-
-
Differential Database: Hourly
-
Transaction Logs: 15 minutes
|
|