Chatee ahora con Soporte
Chat con el soporte

Unified Communications Analytics 8.8.2 - 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 Exchange and Office 365 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:Backup and recovery options Appendix F:Custom configurations Appendix G: Questions and answers about UC Analytics

Backing up and restoring your data using scripts

UC Analytics provides two scripts (batch files) that allow you to back up data from your UC Analytics Storage Engine. The backup batch file uses the “snapshot” command that is included in the Cassandra nodetool utility.

When you run the backup script, you take a snapshot of all your stored data while the Storage Engine service is running. When you take a snapshot, you are backing up your data at a specific point in time.

NOTE: This will temporarily double the amount of data in your Storage directory while the batch file runs.
Supported scenarios
About the backup and restore batch files
Step 1: Edit the backup.bat file parameters for your installation
Step 2: Run the backup batch file
Step 3: Edit the restore batch file
Step 4a: Restore the storage data in an existing installation
Step 4b: Restore the storage data to a new installation

For information about creating a task to back up your data automatically, see Scheduling the backup batch file to run automatically .

Supported scenarios

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

•
You can back up an existing installation and restore to the same installation
•
You can back up an existing installation and restore to a new installation.The Data Engine and Query Engine roles installed in a new installation can be different than the original installation. However, the new installation must meet the following criteria:
•
have the same number of installed Storage Engines as the old installation
•
use the same time zone settings on all Storage Engines as the old installation. UC Analytics performs the backup using a date-related label.
•
have the same server name and IP address as the old installation in which the backup was created.

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

Scenario 1
Server A: All components - Web Site, Data Engine (Insights), Query Engine (Insights), Data Engine (collector role, Query Engine (Collector), Storage Engine.
Server B: Storage Engine
Scenario 2
Server A: Web Site, Data Engine (Insights), Query Engine (Insights), Storage Engine
Server B: Data Engine (Collector), Query Engine (Collector), Storage Engine
Scenario 3
Server A: Web Site, Data Engine (Insights), Data Engine (Collector), Storage Engine
Server B: Query Engine (Insights), Query Engine (Collector), Storage Engine
What is backed up by the backup script?

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:

C:\Program Files\Quest\UC Analytics\Storage Engine Backup Scripts

The folder contains two batch files:

•
backup.bat
•
restore.bat

The folder also contains several PowerShell script files:

•
BackupScript.ps1
•
PurgeScript.ps1
•
RestoreScript.ps1

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.

 
* 
IMPORTANT: On Windows Server 2016, you must open a cmd window as Administrator to run the scripts.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación