5.7
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 Windows Server 2008 R2
- Install the .NET Framework
- Configuring the Database Components of the VCM Collector
- Install SQL Server on the VCM Collector
- Verify and Configure the SQL Server Properties
- Verify Matching SQL Server and Computer Names
- Verify the SQL Server Agent Service Account is a sysadmin
- Verify that the SQL Server Agent Service Starts Automatically
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- 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
- Verify that the SQL Server Agent Service Starts Automatically
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Combined VCM Collector and Web Server
- Three-Tier Split Installation
- Configuring a Three-Tier Split Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Configure the VCM Database Server
- 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
- Verify that the SQL Server Agent Service Starts Automatically
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Web Server
- Configure the VCM Collector
- 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.7
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier toVCM 5.7
- 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
- Linux, UNIX, and Mac OS Agent Files
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- Linux and UNIX 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
n
Simple Recovery. The VCM database settings are set to Simple by default. The transaction log retains
enough information to recover the database to a known good state when the server restarts.
Transaction log backups are not allowed and point-in-time recovery is not available. Simple recovery
causes the transaction log file to grow. SQL Server is in Auto Truncate mode, so the log file periodically
rolls over as data moves from the log file to the data file.
n
Bulk Logged Recovery. The transaction log retains all normal transaction information and discards
transactions that result from a bulk operation. VCM uses the IROWSETFASTLOAD interface extensively,
which is bulk logged.
n
Full Recovery. The transaction log retains all information until it is purged through the SQL Server
LOG backup operation, which the database administrator uses to perform point-in-time recovery. Full
recovery allows incremental backups of the database. Do not use point-in-time recovery, because
certain factors in VCM weaken the point-in-time recovery model. If you implement Full Recovery, you
must set up scheduled daily backups of the transaction log. The log files will continue to grow and
accumulate changes until you back them up. A Full Recovery database that does not have scheduled
backups can fill its disk and stop the system.
Configure Database Recovery Settings
SQL Server supports several database recovery models to control transaction log maintenance. Set a
specific recovery model for each database.
The VCM database settings are set to Simple by default. If you change the VCM database recovery setting
to Full, you must manage your own log backups.
Prerequisites
n
Understand the database recovery models. See "Database Recovery Models" on the previous page.
Procedure
1. Click Start.
2. Select All Programs > Microsoft SQL Server {version} > SQL Server Management Studio.
3. Expand the SQL instance.
4. Expand Databases.
5. Right-click VCM and select Properties.
6. Click Options.
7. In the Recovery model drop-down, select the recovery model and click OK.
What to do next
Create a maintenance plan for SQL Server. See "Create a Maintenance Plan for SQL Server" below.
Create a Maintenance Plan for SQL Server
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.
The maintenance plan uses the automated maintenance functions on SQL Server servers that host the
VCM database.
vCenter Configuration Manager Advanced Installation Guide
156
VMware, Inc.