Refer to the most recent Technical Specifications for approved server environments. Both the application server and the search server are registered within the operating system with their respective configuration files, services, and other resources.
There are three commonly used methods for backing up the application and search servers:
- Using third-party tools to back up the entire file system, including any external partitions used by the operating system. This method ensures all configurations are retained, including Microsoft IIS websites, message queues, and registry values. This method allows for the easiest restoration process, but will require the largest backup time and storage requirements.
- Backing up specific files and folders within the two servers. This method will still store the minimum requirements for restoring a system, but requires less time and storage than backing up an entire file system. Recovering a system using this method will take longer and require additional configuration steps depending on the objects that are backed up. For instance, a drive failure or operating system corruption event would require reinstalling the application server and possibly the search server if only specific folders are backed up.
- Backing up entire systems can be easily accomplished if the application server is installed on a Virtual Machine (VM). Refer to the documentation for your VM host software for additional information on creating snapshots and backups.
A variety of third-party backup solutions are available. Consult your information technology department to determine if your organization has purchased licensed backup software. At a minimum, the following areas of the application server should be backed up (assuming the search server can be re-installed or re-indexed):
- The published content folder located at [Install Location]\Collaboration\WWW\uContent
- Any custom End User template folders located at [Install Location]\Collaboration\WWW\[applicationdirectory]