Scope |
||||||||||
|
||||||||||
Release |
||||||||||
| 8.0.0 | ||||||||||
Description |
||||||||||
The DBMaintenance utility can be used to perform the following periodic
maintenance tasks on the CommServe database:
|
||||||||||
Usage |
||||||||||
|
Using the Utility: 1. Copy the Executable to <Galaxy Install Directory>\Base on CommServe. 2. It is recommended that Galaxy Services are stopped before running this tool. 3. From a command prompt run: DBMaintenance to get a list of options. It is highly recommended (but not absolutely necessary) that Galaxy services are stopped while performing database maintenance. The first time this tool is ever run, a '-full' maintenance is recommended. A '-full' maintenance is recommended every 6 months thereafter. A '-recommended' maintenance is recommended every 4-6 weeks. Please note that database maintenance can take half an hour or even longer to execute depending on database size. Notes: ====== A '-full' maintenance will check the database for inconsistencies, reindex all tables and shrink the database. A '-recommended' maintenance will check the database for inconsistencies and will reindex the tables which are the largest and most often accessed/modified. A shrinkdatase is not performed. Shrinking the database is not recommended on a regular basis - for this reason do not perform a '-full' maintenance regularly. If you would like to reindex all tables, there is a '-reindexall' option that can be used. Combining this with he -checkdb option will have desired effect. If using dbmaintancetool on a cluster, the -S -U and -P options must be specified. (see section about connection parameters). Maintenance Usage examples: =========================== To perform full maintenance - run the following from the command line: dbmaintenance -full To perform recommended maintenance - run the following from the command line: dbmaintenance -recommended To reindex just the archchunkmapping table - run the following from the command line: dbmaintenance -reindex archchunkmapping Other options for maintenance ============================= * Connection parameters (not needed most of the time, but required on a cluster) If run on a Commserve without any connection parameters, the tool will autodetect the database instance, and will get the logon information from the encrypted data in the registry. You can alternatively supply the instance name to connect to and the username and password, but this will not be needed in the majority of the cases. Example: dbmaintenance -S SERVER1\COMMVAULTQINETIX -U sa -P somepwd -recommended -S specifies the server or instance name -U the sql username -P the password. * Custom maintenance parameters Instead of the two maintenance schedules outlined above ('-full' and '-recommended'), it is also possible to specify which type of maintenance you would like to have performed. Here is a list of options: -checkdb Performs a database integrety check -reindexall Reindexes all tables -reindexrecommended Reindexes largest and most often used tables -reindex <table[,table,...]> Reindexes specified table(s) (seperate with commas) -shrinkdb Shrink database. Note: Only perform a -shrinkdb if a lot of free space has become available or it has been a long time since the last maintenance. Running the tool without any parameters will give a full list of supported parameters. Options for troubleshooting =========================== NOTE: Please only use these options if customer support has asked you to use them. PREREQUISITE: To use this, SQL Server Agent (which is a service installed with but different to the sql server service) must be running. In case of lock timeouts/database deadlocks during normal Commserve operations, customer support of your product vendor may ask you to initiate a lock detection job. This generates additional diagnostic data and will actively scan the database every 20 seconds for any blocking queries that may eventually lead to database locktimeouts or deadlocks. Your product vendor can then use this information to figure out which queries are the cause of the problem. To initiate a lock detection job, use the following parameter: -startdblockdetect This will configure and start a SQL Job which will scan for queries that block each other every 20 seconds. The job will disable itself after 5 days of starting it. To stop, use the following option (note, it stops automatically after 5 calendar days) -stopdblockdetect To determine whether any lock timeout data is present in the database, use: - dblockdetectstatus Note that this may come back with data even if you never had any lock detection jobs running. The Commserver software will automatically also log diagnostic information after it encounters a database lock timeout or a deadlock, but what it logs is after the fact so will not catch everything whereas when actively looking for locking queries we actually catch them while the locks are happening. |
||||||||||
History |
||||||||||
|
||||||||||
Disclaimer of Warranties |
||||||||||
|
CommVault provides software tools and utilities on an "as is" basis, as a courtesy and convenience to its users, and they may be changed from time to time without notice. These tools and utilities are provided without express, implied, or statutory warranties of any kind. You assume full risk and responsibility for the selection, possession, performance and proper installation and use of the software tools and utilities, and for verifying the results obtained there from. Your use of CommVault software tools and utilities indicates your unconditional acceptance of the above disclaimer. |
||||||||||