Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Unified Communications Analytics 8.8.3 - 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

Step 4b: Restore the storage data to a new installation

Use this procedure to restore a database to a new installation.

When you restore data from a snapshot, there is intensive processor and I/O activity on the node that is being restored. You run the backup batch file locally on the server on which the Storage Engine resides.

To restore a snapshot backup file in a new installation
1
Install UC Analytics. For information about the criteria that the new installation must meet, see Supported scenarios .
If you have a distributed installation, you must specify the same number of Storage Engines as were installed when the backup was performed.
2
Stop the UC Analytics services on all the servers in the deployment in the following order:
•
Data Engine
•
Query Engine
•
Storage Engine
3
Navigate to the folder that contains the backup and restore script files.
4
Open the command prompt and enter:
restore.bat
5
Restart all the UC Analytics services in the following order:
a
Storage Engine.
b
Query Engine
c
Data Engine

Scheduling the backup batch file to run automatically

You can use the Windows task scheduler to run the backup batch file automatically on a regular basis. For information about configuring the backup and restore batch files, see Backing up and restoring your data using scripts .

 
* 
IMPORTANT: The restore.bat file should only be run manually.
To set up a weekly schedule for backup
1
Start the Windows Task Scheduler.
2
Find and click the task folder in the console tree under which you want to create a folder.
a
If you want to create a sub-folder in the root task folder, click the Task Scheduler Library folder.
b
In the Actions pane, click New Folder.
c
In the Enter name of the new folder dialog box, type the name of folder.
d
Click OK.
3
In the Actions Pane, click Create Task.
4
Step through the details to establish the new schedule with the following settings:
•
On the Triggers tab, set the schedule a trigger for once a week.
•
Point the scheduled task to the backup.bat file provided by UC Analytics.
•
Ensure that you configure the task to run at the highest level.
Using the -force parameter

In the backup.bat file, the parameter -force is useful if you have scheduled the batch file to run automatically as part of a scheduled task. If a backup file of the same name is found in the backup directory path, -force causes the script to overwrite the file without issuing a prompt saying that a duplicate file name has been detected.

If you are running the script manually, you might want to remove the -force parameter.

Performing a manual backup of the storage folder before upgrade

Before you upgrade UC Analytics, it is recommended that you perform a manual backup of your storage folder. If you have multiple Storage Engines deployed, you must take a backup of each storage folder on each server.

To perform a manual backup of the storage folder
1
Stop the following UC Analytics services:
•
UC Analytics Query Engine
•
UC Analytics Storage Engine
2
Navigate to the UC Analytics storage folder. By default, the directory is located in the following path:
C:\Program Files\<VendorName>\UC Analytics\Storage
3
Use a compression utility to compress the Storage folder, such as to a zipped file format.
4
Copy the compressed file to a separate location.
 
* 
NOTE: It may take several hours to complete the manual copy.

This type of backup copy is different from the backup script. The backup script copies only the collected data, data source configuration, and Admin settings. The backup script does not copy the Cassandra system files. To back up all of the database, you must copy the entire storage folder.

Moving your storage location

You can move the location of your UC Analytics storage database within the same computer. When you move the database, you must also change a number of places that point to the database.​

To move the storage directory and configure the cassandra.yaml file for the new location
1
Stop the following UC Analytics services:
•
UC Analytics Query Engine
•
UC Analytics Storage Engine
2
Navigate to the UC Analytics installation folder. By default, the installation directory is located in the following path:
C:\Program Files\Quest\UC Analytics\
3
Move the directory named Storage to the new location.
4
Navigate to the following directory:
C:\Program Files\Quest\UC Analytics\Storage Engine\conf
5
Open the following text file for editing:
cassandra.yaml
6
Locate the following text in the file:
C:\Program Files\Quest\UC Analytics\Storage
You will find this text in three locations related to the data, the commitlog, and the saved_caches. Note that this path name uses forward slashes, not back slashes.
7
In the three locations, change the path name to the new location you selected in Step 3.
8
Locate the following file in the Configuration directory:
C:\Program Files\Quest\UC Analytics\Configuration\DeploymentConfiguration.txt
9
In the Configuration.txt file, locate the following parameter:
"Settings":[{"Key":"StorageEnginePhysicalMemory","Value":"8192"},{"Key":"StorageDirectoryPath","Value":"C:\\Program Files\\Quest\\UC Analytics\\Storage"},
10
Change {"Key":"StorageDirectoryPath","Value":"C:\\Program Files\\Quest\\UC Analytics\\Storage"} to reflect the new path for the storage location.
11
Start the Query Engine and Storage Engine services.
* 
TIP: If User Account Control (UAC) is on when you perform the procedure, UAC file virtualization might be active when you try to update DeploymentConfiguration.txt and cassandra.yaml files. As a result, the actual files in Program Files are not updated. In this case, you might have to temporarily disable UAC to update the files.
Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation