Installation guide

Maintaining VCM After Installation

Perform routine maintenance on your VCM configuration management database to keep VCM running

smoothly and performing efficiently. Maintenance includes configuring settings specific to your

environment, configuring the database file growth and recovery settings, creating a maintenance plan,

and incorporating the database into your backup and disaster recovery plans.

Prerequisites

n Install VCM. See "Use Installation Managerto Install VCM" on page116.

n Understand the database recovery models. See "Database Recovery Models" on page153.

Procedure

1. "Customize VCM and Component-Specific Settings" below

Customize the general VCM settings and the component-specific settings for your environment.

2. "Configure Database File Growth" on page153

Configure the autogrowth properties of the VCM database and log file to restrict the file growth from

affecting VCM performance.

3. "Configure Database Recovery Settings" on page154

SQL Server supports several database recovery models to control transaction log maintenance. Set a

specific recovery model for each database.

4. "Create a Maintenance Plan for SQL Server" on page154

To ensure that VCM runs at peak performance and requires little operator intervention during its

lifecycle, you must set up a routine maintenance plan. VCM relies heavily on its SQL databases for

operation.

5. "Incorporate the VCM Database into Your Backup and Disaster Recovery Plans" on page156

Consider your VCM database as any other SQL database in your environment and incorporate the

database into your corporate strategy for backup and disaster recovery.

Customize VCM and Component-Specific Settings

Customize the general VCM settings and the component-specific settings for your environment. You can

customize general settings for the VCM Collector, customer information, database, input or output

directories, VCM Remote, the VCM installer, auditing, and operating system patching. You can customize

specific settings for installed components.

VMware, Inc.

151