In the following article we all review our solution modules and the options for high availability and backup.
ControlUp's Cloud Solution:
The Entire Solution has High-Availability since most configurations and Insights Data are saved in the Cloud.
ControlUp Real Time Console:
Backup: For saving Personal’s user configuration such as Draft SBAs, Columns views, credentials set etc.
You should backup the folder: C:\Users\<user>\AppData\Roaming\ControlUp.
High Availability: The Console is by design has high availability feature by storing all configuration in the cloud or local directory services on the on-premise server.
Backup: For saving the monitor's settings, backup folder -C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming
High Availability: Install 2 Monitors, select the Primary Monitor, once the Primary fails, the 2nd monitor will automatically take over.
ControlUp's On-Premises Solution:
ControlUp On-Premises Server:
Backup: Since the ControlUp server machine stores the LDS & IIS in addition to the CU server service, the only way to fully back it up is to create an image (using MS built in tool, Acronis or any other software).
High Availability: We recommend using a Network Load Balancer with PVS, You can read more about it here.
ControlUp's SQL DB:
Backup: Use Microsoft’s recommendations on Backup SQL DB from Here.
High Availability: Use Microsoft’s recommendations on how to make it HA from Here.
ControlUp's On-Premsies Console + Monitor:
Same as Online mode, backup the relevant folders is a must.
IOP (Insights On-Premises):
Backup: Backing up the Activity Files folder (It has to be a SMB share) will be enough for recreating the Historical Reporting, so if the Share is backed up regularly it is good, other solution could be using DFS or even Robocopy it to a location that is backed up on a regular basis.
High Availability: Create an Image of the IOP machine or just install IOP on a fresh machine and check our KB afterwards - Adding Insights On-Premises IOP Module