VMware VCENTER CHARGEBACK 1.5 - API Manual do Utilizador Página 36

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 54
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 35
What to do next
After you have taken a backup of the database, you must purge the vCenter Chargeback Manager database.
See KB 1026068 (http://kb.vmware.com/kb/1026068) for further instructions.
If you are using a vCenter Chargeback Manager release prior to 1.6, and are using Oracle Database as a vCenter
Chargeback Manager database and Microsoft SQL Server database as the vCenter Server database, then follow
the instructions provided in KB 1032952 (http://kb.vmware.com/kb/1032952.)
You can also back up the relevant configuration files from the current vCenter Chargeback Manager
installation, so that you can restore the existing installation if the upgrade fails. See KB 1026796
(http://kb.vmware.com/kb/1026796) for further details.
Upgrade vCenter Chargeback Manager
You can upgrade an existing vCenter Chargeback Manager instance to a more recent version.
Prerequisites
Before you upgrade a standalone vCenter Chargeback Manager instance, stop the corresponding vCenter
Chargeback Manager service and the data collector services. If any vCenter Chargeback Manager related
service is running, the upgrade process fails.
For a cluster installation, you must upgrade each vCenter Chargeback Manager instance in the cluster. You
must first upgrade the instance that has the load balancer. Before upgrading the first instance of a cluster, you
must stop all the related services. When the first instance is upgraded, the corresponding vCenter Chargeback
Manager database is also upgraded. After the upgrade, the vCenter Chargeback Manager service and the
corresponding database, data collector, and load balancer services are automatically restarted.
NOTE You must upgrade all the instances in a cluster to ensure that the application functions correctly. A
cluster with multi-version vCenter Chargeback Manager instances might not function correctly.
Ensure that you are running the installer on the machine on which vCenter Chargeback Manager is installed.
If you run the installer from a shared location on the network, the installer might fail.
If the existing instance vCenter Chargeback Manager has a VMware Cloud Director Data Collector installed,
ensure that you provide the same VMware Cloud Director database details for the vCenter Chargeback
Manager instance during upgrade.
Procedure
1 Run the vCenter-CB.exe file.
The installation wizard is displayed.
2 Click Next on the Introduction screen.
3 Accept the end-user license agreement, and click Next.
When the installer detects an older version of vCenter Chargeback Manager, an Alert dialog box is
displayed.
4 Click Upgrade to 2.0.0.0 in the Alert dialog box.
5 If the vCenter Chargeback Manager database is an SQL Server database, the installer displays the Database
Configuration screen.
You can change the SQL Authentication Mode option on this screen.
a (Optional) Select Windows Authentication as the authentication type.
b Provide the Windows user account name in the form DomainName\UserName.
The user must have the Log on as a service permission.
vCenter Chargeback Manager Installation and Upgrade Guide
36 VMware, Inc.
Vista de página 35
1 2 ... 31 32 33 34 35 36 37 38 39 40 41 ... 53 54

Comentários a estes Manuais

Sem comentários