Chat now with support
Chat with Support

Unified Communications Analytics 8.6 - Deployment Guide

Prerequisites for your installation Installing UC Analytics Configuring UC Analytics Adding data sources for Active Directory or Azure Active Directory Adding data sources, chargeback costs, and thresholds for Exchange and Exchange Online
Permissions needed to collect Exchange on-premises or hybrid data Permissions needed to collect from native Exchange Online Creating an Exchange Configuration data source Creating an Exchange Tracking Logs data source Creating an Exchange Mailbox Contents data source Do I need both Exchange Tracking Logs and Exchange Mailbox Contents collections? Creating an Exchange IIS Logs data source Creating an Exchange Mailbox Content Summary data source Creating an Exchange Calendar data source Creating an Exchange Public Folders data source Adding Exchange Online hybrid data sources for hybrid Office 365 Adding Exchange Online data sources for native Office 365 Setting chargeback costs for Exchange Setting thresholds for Exchange metrics Omitting words when filtering by subject or body
Adding data sources, chargeback costs, and thresholds for Skype for Business/Lync Adding data sources, chargeback, and thresholds for Cisco Managing which insights can seen by users Configuring and managing subscriptions Making changes to your deployment Appendix A:Configuring Impersonation Appendix B:Configuring the Skype for Business or Lync Server Appendix C:Configuring IIS Log Files to capture ActiveSync or OWA events Appendix D:PowerShell cmdlets used by data sources Appendix E:Custom configurations and backup and recovery options Appendix F: Questions and answers about configuration

Supported scenarios

The following scenarios are supported by the backup and restore scripts:

For example, any of the following installations could be backed up and interchangeably restored:

All your configuration and collected data is backed up when you run the backup script. When you run the restore script, the configuration and collected data are restored to the state when backup was created.

The backup process saves data from all the tables in the \Storage\data\Doradus folder and creates a separate subdirectory for each saved table. Each snapshot directory contains numerous files of data captured at the time of the snapshot. The backup process also saves configuration data from the \Storage\data\System folder.

The batch file then copies the snapshot data created to the backup folder (named based on the current date and time), then removes the snapshot directories from the original Storage folder.

About the backup and restore batch files

In the UC Analytics installation path, there is a folder named Storage Engine Backup Scripts. By default, the directory is located in the following path:

The folder contains two batch files:

The folder also contains several PowerShell script files:

To use the scripts, copy all the files to the folder on each server that hosts the UC Analytics Storage Engine. If you have multiple storage nodes, you must run the script on each node. All nodes must be in the same time zone.

Prerequisites

To run the backup and restore batch files, you must have PowerShell 3.0 or later installed on the server that hosts the UC Analytics Storage Engine.

To run the backup.bat file to create the backup, all the UC Analytic services must be running.

For deployments with multiple storage nodes, the scripts must be run on each node. All nodes must be within the same time zone.

The prerequisites for running the restore.bat differ depending whether you are restoring to the existing installation or to a new installation.

Step 1: Edit the backup.bat file parameters for your installation

After you have copied all the backup and restore files to the server that hosts the UC Analytics Storage Engine, you must edit the backup.bat file to specify the parameters for your environment.

The backup.bat file looks as follows:

-storageEngineDirectoryPath "C:\Program Files\Quest\UC Analytics\Storage Engine\bin" -storageDirectoryPath "C:\Program Files\Quest\UC Analytics\Storage" -backupDirectoryPath "c:\UCA\backup" -backupLabel "label" -portNumber 7299 -numberOfBackupCopies 2 -force

The parameters that you can edit are as follows:

storageEngineDirectoryPath

C:\Program Files\Quest\UC Analytics\Storage Engine\bin

Shows the location of the storage engine. If you installed using the default values, you can leave this parameter as shown.

storageDirectoryPath

C:\Program Files\Quest\UC Analytics\Storage

Shows the location of the storage folder. If you installed using the default values, you can leave this parameter as shown.

backupDirectoryPath

c:\UCA\backup

Enter the path and folder name for the folder to which you want to copy the backup files.

You can enter a UNC path if you are copying the backup files to a different server or share.

backupLabel

label

Enter a unique name to identify the storage folder and server that contains the Storage Engine data that you want to back up.

For example, you could enter Store1Server1.

portNumber

7299

Port used by the Cassandra nodetool.

numberOfBackupCopies

2

Enter the number of backup copies that will be retained at any one time. The backup folders are date-stamped so if you are retaining two copies, the two newest folders are kept and any older copies are removed.

Related Documents