5.6
Table Of Contents
- VMware vCenter Configuration Manager Advanced Installation Guide
- Contents
- About This Book
- Achieving a Successful VCM Installation
- Hardware Requirements for Collector Machines
- Software and Operating System Requirements for Collector Machines
- Preparing for Installation
- System Prerequisites to Install VCM
- Configure Resources to Install VCM on a Virtual Machine
- Secure Communications Certificates
- Single-Tier Server Installation
- Configure a Single-Tier Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Install the .NET Framework
- Configuring the Database Components of the VCM Collector
- Configure the Web Components
- Configure SSRS on the VCM Collector
- Configure the VCM Collector Components
- Two-Tier Split Installation
- Configuring a Two-Tier Split Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Configuring the VCM Database Server
- Disable the Firewall or Add an Exception for SQL Server Port 1433
- Install SQL Server on the Database Server
- Verify and Configure the SQL Server Properties
- Verify Matching SQL Server and Computer Names
- Verify the SQL Server Agent Service Account is a sysadmin
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Combined VCM Collector and Web Server
- Three-Tier Split Installation
- Installing VCM
- Configuring SQL Server for VCM
- Upgrading or Migrating VCM
- Upgrading VCM and Components
- Upgrading Virtual Environments Collections
- Migrating VCM
- Prerequisites to Migrate VCM
- Migrate Only Your Database
- Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment
- Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier...
- How to Recover Your Collector Machine if the Migration is not Successful
- Maintaining VCM After Installation
- Hardware and Operating System Requirements for VCM Managed Machines
- VCM Agent Support on Non-English Windows Platforms
- VCM Managed Machine Requirements
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- UNIX and Linux Patch Assessment and Deployment Requirements
- Support for VMware Cloud Infrastructure
- vCenter Operations Manager Integration Features
- FIPS Requirements
- Agent Sizing Information
- Hardware and Software Requirements for the Operating System Provisioning Server
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Index
Maintaining VCM After Installation
14
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 Managerto Install VCM" on page 117.
n
Understand the database recovery models. See "Database Recovery Models" on page 152.
Procedure
1. "Customize VCM and Component-Specific Settings" on page 150
Customize the general VCM settings and the component-specific settings for your environment.
2. "Configure Database File Growth" on page 152
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 153
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 2008 R2" 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.
150