6.3
Table Of Contents
- vRealize Operations Manager Customization and Administration Guide
- Contents
- About Customization and Administration
- Configuring Users and Groups
- Customizing How vRealize Operations Manager Displays Your Data
- Customizing How vRealize Operations Manager Monitors Your Environment
- Defining Alerts in vRealize Operations Manager
- Object Relationship Hierarchies for Alert Definitions
- Alert Definition Best Practices
- Understanding Negative Symptoms for Alerts
- Create an Alert Definition for Department Objects
- Add Description and Base Object to Alert Definition
- Add a Virtual Machine CPU Usage Symptom to the Alert Definition
- Add a Host Memory Usage Symptom to the Alert Definition
- Add Recommendations to the Alert Definition
- Create a Custom Accounting Department Group
- Create a Policy for the Accounting Alert
- Configure Notifications for the Department Alert
- Create a Dashboard to Monitor Department Objects
- Defining Symptoms for Alerts
- Viewing Actions
- Defining Recommendations for Alert Definitions
- Creating and Managing Alert Notifications
- List of Outbound Plug-Ins
- Add Outbound Notification Plug-Ins
- Add a Standard Email Plug-In for Outbound Alerts
- Add a REST Plug-In for Outbound Alerts
- Add a Log File Plug-In for Outbound Alerts
- Add a Network Share Plug-In for vRealize Operations Manager Reports
- Add an SNMP Trap Plug-In for Outbound Alerts
- Add a Smarts Service Assurance Manager Notification Plug-In for Outbound Alerts
- Filtering Log File Outbound Messages With the TextFilter.xml File
- Configuring Notifications
- Defining Compliance Standards
- Operational Policies
- Managing and Administering Policies for vRealize Operations Manager
- Policy Decisions and Objectives
- Default Policy in vRealize Operations Manager
- Custom Policies
- Policies Provided with vRealize Operations Manager
- User Scenario: Create a Custom Operational Policy for a vSphere Production Environment
- User Scenario: Create an Operational Policy for Production vCenter Server Datastore Objects
- Create a Group Type for Your Datastore Objects
- Create an Object Group for Your Datastore Objects
- Create Your Policy and Select a Base Policy
- Override the Analysis Settings for the Datastore Objects
- Enable Disk Space Attributes for Datastore Objects
- Override Alert and Symptom Definitions for Datastore Objects
- Apply Your Datastore Policy to Your Datastore Objects Group
- Create a Dashboard for Disk Use of Your Datastore Objects
- Using the Monitoring Policy Workspace to Create and Modify Operational Policies
- Policy Workspace in vRealize Operations Manager
- Super Metrics in vRealize Operations Manager
- Customizing Icons
- Managing Objects in Your Environment
- Configuring Object Relationships
- Customizing How Endpoint Operations Management Monitors Operating Systems
- Modifying Global Settings
- Defining Alerts in vRealize Operations Manager
- Maintaining and Expanding vRealize Operations Manager
- Cluster and Node Maintenance
- Logging
- Passwords and Certificates
- How To Preserve Customized Content
- Backup and Restore
- OPS-CLI Command-Line Tool
- Index
Disable Quiescing
Before you backup your vRealize Operations Manager multi-node cluster by using vSphere Data Protection,
disable quiescing of the le system.
Procedure
1 Log in to the ESXi host with an SSH session, and power o all nodes.
2 Navigate to the /vmfs/volumes/virtual_machine_datastore/ virtual_machine/ directory, and open the
virtual_machine.vmx le for editing.
3 Set the disk.EnableUUID parameter to false.
You may have to add the disk.EnableUUID parameter to the virtual_machine.vmx le.
4 Save and close the le.
5 Power on all nodes.
6 Open a console session to the virtual machine, and log in to each node.
7 Navigate to the /etc/vmware-tools directory, and open the tools.conf le for editing.
If you cannot locate the tools.conf le, run the vi tools.conf command to create a le.
8 Add these parameters to the le.
[vmbackup]
enableSyncDriver = false
This runs a synchronization operation before the snapshot, and does not run a freeze on the le system.
9 Save and close the le.
What to do next
Backup your vRealize Operations Manager multi-node cluster by using vSphere Data Protection.
Back Up vRealize Operations Manager By Using vSphere Data Protection
You can use vSphere Data Protection to associate the backup of a vRealize Operations Manager multi-node
cluster with a backup schedule and retention policies.
Be aware of these guidelines when you back up vRealize Operations Manager systems.
n
Use a resolvable host name and a static IP address for all nodes.
n
Back up the entire virtual machine. You must back up all VMDK les that are part of the virtual
appliance.
n
Do not stop the cluster while performing the backup.
n
Do not perform backup while dynamic threshold (DT) calculations are running because this might lead
to performance issues or loss of nodes.
You are not required to delete any snapshots, however, be aware that vSphere Data Protection deletes all
existing snapshots at the time of backup.
Prerequisites
n
“Disable Quiescing,” on page 135.
n
Verify that all nodes are powered on and are accessible while the backup is taking place.
n
Deploy and congure the vSphere Data Protection appliance. See the vSphere Data Protection
Administration Guide.
Chapter 4 Maintaining and Expanding vRealize Operations Manager
VMware, Inc. 135