Administrator Guide

Table 30. Data Consistency Runbooks
Subsystem Detection and Recovery Child Runbooks
Virtual Machine Provider
(VMProvider)
Detection: Test-VmCloudsDataConsistency
Detects and reports inconsistencies between the Windows Azure Pack,
SPF, and VMM database components, that is, objects associated with the
VM Cloud Resource Provider. This runbook can detect the following
issues:
For VMM:
• "Object not found" for cloud, hardware prole, VM network, VM
template, and user role
• "Out of sync" for user role quota, user role network settings, and user
role virtual machine permissions
• Other – Logical networks not added to the cloud.
For SPF:
• "Object not found" for the Gallery item, stamp, and tenant
• "Out of sync" for tenant status
NOTE: Out of sync indicates that the properties in the
component are out of sync with the properties that are set on
the plan, subscription, or add-on.
Recovery: Repair-VmCloudsDataConsistency
Tries to automatically recover issues with plans, add-ons, and
subscriptions. Also reports issues that the runbook cannot x, where
manual recovery may be required.
NOTE
: There is an extra data consistency runbook that is not called by the Invoke-DataConsistency runbook. This is the
SyncVMCloudsWithFabric runbook. It refreshes fabric objects such as VMM hosts, clusters, library shares, virtual machines, and
so on, to bring the VMM database to a consistent state with the current state of the underlying fabric. After a fabric sync
completes, the runbook syncs VMM with Operations Manager. Typically, you should not have to run this runbook because VMM
includes refreshers that do this automatically. If you run this runbook,
be aware that it aects performance, and it can take
several hours to complete , depending on the number of VMs. You would run this only if you restored the VMM or Operations
Manager database, and issues were not automatically xed by the VMM refresher.
How to use the data consistency runbooks
This section describes the recommended way to run the detection and recovery runbooks.
You can run the Invoke-DataConsistency runbook, both detection and recovery, when there is live trac on the system. However, you
must rst run a script to reset the passwords across the system. This procedure requires downtime of the whole stamp.
Depending on the output of the detection process, you must either run the Invoke-DataConsistency runbook again with the repair option
enabled, and/or perform extra manual steps.
1 Create a shared folder for the output record. Before you begin, make sure that a shared folder exists that you can specify as the
location to store the output report. You must grant the < Prex >System account Read and Write permissions to the share.
a Create a folder on the Console VM, such as DCOutput .
b Right-click the folder, and then click Properties.
c Click the Sharing tab, and then click Advanced Sharing.
d Select the Share this folder check box, and then click Permissions.
e Click Add, enter the account < Prex >System, and then click OK.
f Click the account that you just added, and then under Allow, select the Change check box.
Operations
97