5.6

Table Of Contents
What to do next
n
Configure the SQL Server settings to tune your VCM database in SQL Server Management Studio,
including the VCM database file growth and database recovery. See "Maintaining VCM After
Installation" on page 113.
n
Log in to VCM.
How to Recover Your Collector Machine if the Migration is not Successful
If the migration to VCM 5.6 failed, you must perform several steps to recover your VCM Collector
machine. Before you attempt another migration to VCM 5.6, contact VMware Technical Support to
identify what caused the migration to fail and answer any questions about the migration procedures.
Prerequisites
n
Identify the available migration options. See "Migrating VCM" on page 101.
n
Understand the scenarios to migrate your VCM environment to VCM 5.6. See "Upgrading or Migrating
VCM" on page 91.
n
Understand the prerequisites to migrate your VCM environment to VCM 5.6. See "Prerequisites to
Migrate VCM" on page 101.
n
Understand how to attach a SQL server database in SQL Server Management Studio. See the Microsoft
MSDN Library.
Procedure
1. On your VCM Collector, reinstall the software that was installed before you started the migration.
Install the software in the order listed.
a. SQL Server 2005
b. SQL Server Reporting Services, 32-bit version
c. SQL Server 2005 SP3
d. VMware VCM 5.3, EMC Ionix SCM 5.0 or later, or Configuresoft ECM 4.11.1 or later
2. Use SQLServer Management Studio Object Explorer to connect the databases from your backed up
copies.
3. Recopy the files to the CMFILES$ share.
What to do next
Configure the SQL Server settings to tune your VCM database in SQL Server Management Studio,
including the VCM database file growth and database recovery. See "Maintaining VCM After Installation"
on page 113.
Upgrading or Migrating VCM
VMware, Inc.
111