Symantec Enterprise Vault Technical Note. Administering the Monitoring database. Windows

Transcription

1 Symantec Enterprise Vault Technical Note Administering the Monitoring database Windows December 2006

2 Symantec Enterprise Vault Administering the Monitoring database Copyright 2006 Symantec Corporation. All rights reserved. Symantec Enterprise Vault 7.0 Symantec, the Symantec logo, and Enterprise Vault are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THIS DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID, SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software and commercial computer software documentation as defined in FAR Sections and DFARS Section Symantec Corporation Stevens Creek Blvd. Cupertino, CA

3 Contents Maintaining the Monitoring database... 5 Moving the Monitoring database... 6 Preparation... 6 Moving the database... 6 Restoring the Monitoring database... 7

4 4 Contents

5 Administering the Monitoring database This Technical Note provides supplementary information on how to administer the Enterprise Vault Monitoring database. Maintaining the Monitoring database This section provides additional information for the Enterprise Vault Backup Procedures and Day-to-day Administration chapters of the Administrator s Guide. The Monitoring database is an SQL database containing the data gathered by the Enterprise Vault Monitoring agents. This data is used by Enterprise Vault Operations Manager, and in some of the reports generated by Enterprise Vault Reporting. The initial sizes of the Monitoring database and transaction log device are 100 megabytes and 80 megabytes respectively, making a total initial disk space requirement of 180 megabytes. Ensure that there is adequate space for the database to grow as data is added. The Monitoring database is set up as follows: Item Database name Login name Data Device name Log Device name Details EnterpriseVaultMonitoring Vault Service account; Operations Manager account (OMWebUser); Reporting account (ReportingUser) EnterpriseVaultMonitoring_Data EnterpriseVaultMonitoring_Log

6 6 Administering the Monitoring database Moving the Monitoring database Back up the Monitoring database as part of a planned backup procedure. A suggested backup regime for the Monitoring database is: Back up the database and truncate the transaction log twice per month. Back up the transaction log weekly. For more information on backing up the Monitoring database, see Backing up the Monitoring database in the Enterprise Vault Backup Procedures chapter of the Administrator s Guide. Moving the Monitoring database This section provides additional information for the Day-to-day Administration chapter of the Administrator s Guide. You can move the Monitoring database between SQL Server instances. This is useful for reconfiguration and disaster recovery. Preparation Before you move the Monitoring database to another SQL Server, you must perform the following preparatory steps. Moving the database To prepare for moving the Monitoring database 1 Replicate or restore the EnterpriseVaultMonitoring database to the new SQL Server. To replicate the database you can use the Copy Database Wizard provided by SQL Enterprise Manager. 2 Ensure that the Vault Service account has the required permissions to access the new database. 3 Ensure that the new SQL Server is running. To move the Monitoring database 1 Connect to the SQL server hosting the EnterpriseVaultMonitoring database, using SQL Enterprise Manager or SQL Query Analyzer, or a similar tool. 2 Enter and run the following SQL commands: USE EnterpriseVaultDirectory UPDATE MonitoringSettings SET SQLServer = <New_SQL_Server> where <New_SQL_Server> is the name of the new SQL server.

7 Administering the Monitoring database Restoring the Monitoring database 7 Restoring the Monitoring database This section provides supplementary information for the Recovery chapter of the Administrator s Guide. The following procedures describe: Restoring the Monitoring database to the server that previously hosted it. Restoring the Monitoring database to a different SQL server machine. You can use this procedure if the original machine is unavailable, for example if you cannot recover it. To restore the Monitoring database to the server that previously hosted it 1 On the SQL Server machine that used to host the Monitoring database, start SQL Enterprise Manager by clicking Start > Programs > Microsoft SQL Server >Enterprise Manager. 2 Expand the view until you see the Databases container, and then select it. 3 On the Tools menu, click Restore Database. 4 In the Restore database dialog box, select EnterpriseVaultMonitoring in the Restore as database box. 5 Next to Restore, click From device, and then click Select Devices. The Choose Restore Devices dialog box appears. 6 Click Add. 7 In the Choose Restore Destination dialog box, select the backup file from which to restore, and then click OK. 8 Click OK to close the Choose Restore Destination dialog box, and then click OK again to close the Choose Restore Devices dialog box. 9 In the Restore database dialog box, ensure that the options Restore backup set and Database - complete are selected. 10 Select the Options tab, and then select Leave database operational. No additional transaction logs can be restored. 11 Click OK to start the restoration. To restore the Monitoring database to a different SQL server machine 1 Ensure the new SQL server machine contains the same folder structure on the same drive as the original SQL server machine where the Monitoring database previously existed. The Monitoring database must be restored to the same location on the new machine that it occupied on the original machine.

8 8 Administering the Monitoring database Restoring the Monitoring database 2 On the new SQL Server machine, start SQL Enterprise Manager by clicking Start > Programs > Microsoft SQL Server >Enterprise Manager. 3 Expand the view until you see the Databases container, and then select it. 4 On the Tools menu, click Restore Database. 5 In the Restore database dialog box, enter EnterpriseVaultMonitoring in the Restore as database box. 6 Next to Restore, click From device, and then click Select Devices. The Choose Restore Devices dialog box appears. 7 Click Add. 8 In the Choose Restore Destination dialog box, select the backup file from which to restore, and then click OK. 9 Click OK to close the Choose Restore Destination dialog box, and then click OK again to close the Choose Restore Devices dialog box. 10 In the Restore database dialog box, ensure that the options Restore backup set and Database - complete are selected. 11 Select the Options tab, and then select Leave database operational. No additional transaction logs can be restored. 12 Click OK to start the restoration. 13 When the restoration has completed, click OK to close the success message. 14 Connect to the SQL server using SQL Enterprise Manager or SQL Query Analyzer, or a similar tool. 15 Enter and run the following SQL commands: USE EnterpriseVaultDirectory UPDATE MonitoringSettings SET SQLServer = <New_SQL_Server> where <New_SQL_Server> is the name of the new SQL server.