Total Pageviews

Log locations for VMware vRealize Automation 7.x

Log locations for VMware vRealize Automation 7.x

A full log bundle containing all vRealize Automation 7.x logs (with the exception of Guest Agent and Application Services logs) can be obtained from the vRealize Automation Appliance Management website under the Cluster tab.

Server Log location Log Purpose
vRealize Automation Appliance /storage/log/vmware/vcac/vcac-config.log vRealize Automation Appliance configuration logs
vRealize Automation Appliance /storage/log/vmware/vcac/telemetry.log vRealize Automation telemetry log
vRealize Automation Appliance /storage/log/vmware/vco/configuration/catalina.out vRealize Orchestrator Configuration log
vRealize Automation Appliance /storage/log/vmware/vco/configuration/controlcenter.log vRealize Orchestrator Control Center log
vRealize Automation Appliance /storage/log/vmware/vco/app-server/server.log vRealize Orchestrator Server log
vRealize Automation Appliance /storage/log/vmware/horizon/connector.log vIDM connector request log
vRealize Automation Appliance /storage/log/vmware/horizon/catalina.log vIDM Server log
vRealize Automation Appliance /storage/log/vmware/horizon/horizon.log vIDM Server log
vRealize Automation Appliance /storage/log/vmware/vcac/catalina.out vRealize Automation Server log
vRealize Automation Appliance /var/log/vmware/horizon/horizon.log vRA 7.2 horizon log
vRealize Automation Appliance /var/log/vmware/horizon/connector.log vRA 7.2 connector request log
vRealize Automation Appliance /storage/db/pgdata/pg_log/postgresql.csv vPostgres Log
vRealize Automation Appliance /opt/vmware/var/log/vami/vami.log Appliance Management and upgrade logs
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Agents\agent_name\logs\file Plug-in logs example: CPI61, nsx, VC50, VC51Agent, VC51TPM, vc51withTPM, VC55Agent, vc55u, VDIAgent
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Distributed Execution Manager\DEMOR\Logs\DEMOR_All Distributed Execution Manager logs
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Distributed Execution Manager\DEMWR\Logs\DEMWR_All Distributed Execution Worker logs
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Server\Logs Manager Service logs
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Server\ConfigTool\Log\vCACConfiguration-date Repository Configuration logs
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Data\Logs\nothing_today IIS Access logs (usually empty, but can be expected)
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\Logs\Repository Repository logs
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Server\Website\Logs\Web_Admin_All Web Admin logs
IaaS Windows Server C:\inetpub\logs IIS logs
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Web API\Logs\Elmah WAPI website logs (6.2.x)
IaaS Windows Server C:\Program Files (x86)\VMware\vCAC\Management Agent\Logs Management Agent logs
Windows Guest Agent Connection Log C:\VRMGuestAgent\axis2\logs\gugent-axis.log Connection logs showing status of connection to vRA Management Service server
Windows Guest Agent Log C:\VRMGuestAgent\GuestAgent.log All Guest Agent actions (post successful connection)
Linux Guest Agent Connection Log /usr/share/gugent/axis2/logs/gugent-axis.log Connection logs showing status of connection to vRA Management Service server
Linux Guest Agent Log /usr/share/gugent/GuestAgent.log All Guest Agent actions (post successful connection)
Windows Application Services Agent logs c:\opt\vmware-appdirector\agent\logs\agent_bootstrap.log Windows logs for the Software Provisioning agent.
Linux Application Services Agent logs /opt/vmware-appdirector/agent/logs/agent_bootstrap.log Linux logs for the Software Provisioning agent.
Linux Software Agent Logs /opt/vmware-appdirector/agent/logs/darwin-agent<date>.log Linux logs for the Software agent.
Windows Software Agent Logs c:\opt\vmware-appdirector\agent\logs\darwin-agent<date>.log Windows logs for Software agent.

Enable Automatic Manager Service Failover in vRA7.5


Enable Automatic Manager Service Failover in vRA7.5



Automatic Manager Service failover is disabled by default if you install or upgrade the Manager Service with the standard vRealize Automation Windows installer.
To enable automatic Manager Service failover after running the standard Windows installer, take the following steps. 

Procedure
  1. Log in as root to a console session on the vRealize Automation appliance. 
  2. Navigate to the following directory. 
/usr/lib/vcac/tools/vami/commands
  1. Enter the following command.
python ./manager-service-automatic-failover ENABLE 

Results
If you need to disable automatic failover throughout an IaaS deployment, enter the following command instead. 

python ./manager-service-automatic-failover DISABLE

What's New in VMware vRealize Automation 7.6


What's New
The vRealize Automation 7.6 release includes resolved issues and these new capabilities.

New Features and Enhancements
With vRA/vRO 7.6 VMware is making the Hybrid Cloud easy.
  • Install and configure
    • New VAMI UI summary page
    • New VAMI Additional cluster health alerts that are configurable
    • SNMP service - facilitates the monitoring of the vRA node resources such as CPU, Memory and many other. Configurable to actively monitor resources and send snmp trap when certain threshold is exceeded, API available

  • Upgrade enhancements:
    • Bug fixes and small enhancements
    • Upgrade will back up all configuration files
    • API improvements – fine grained progress reporting at API level
    • Upgrade flow is now more configurable - some of the steps could be configured for later execution

  • Custom Forms Enhancements - Providing a higher level of flexibility for customers wishing to customize and enhance their request forms in vRA
    • Datagrid Enhancements – Blueprint-defined disks are read-only, cell validation, and field refresh when rows are added, removed, or edited
    • Added dual list selector component
    • Added multiple selector component for complex objects
    • Added link component

You can get more information from here-vRealize Automation 7.6

What’s New in vRealize Automation 7.6 and vRealize Lifecycle Manager 2.1


Vmware announce the upcoming release of vRealize Automation 7.6 and vRealize Lifecycle Manager 2.1, which continue to refine and enhance ease of use of our Cloud Management Platform and its integration with the broader SDDC.

 

What’s new in vRealize Automation 7.6

In this release of vRealize Automation, we are enhancing the integration and management of VMware SDDC with our Cloud Management Platform (CMP).
  • NSX Integration – customers can now configure both NSX-T and NSX-V for different clusters on a single vCenter Server. We are also adding support for on-demand private networking.
  • vRealize Orchestrator User Experience – with this release we are enhancing the user experience for customers using the vRealize Orchestrator UI for workflow management. This includes additional functionality such as Design, Run, Content Management and Troubleshooting.


What’s new in vRealize Lifecycle Manager 2.1

In this release we continue with our vision to make the hybrid cloud easy, and more specifically, make the vRealize Suite management easier.  As a reminder, vRealize Suite Lifecycle Manager delivers lifecycle and content management for vRealize Suite. With this release, we are adding functionality across the different aspect of vRealize Suite Lifecycle Manager, including
  • VMware Validated Designs template installation
  • Granular deployment options
  • Multi-content capture
  • vIDM lifecycle management
  • Additional enhancements for better user experience

Guideline for Planning vRealize Automation Backup


In my last post, I covered the steps  to Automat vRA distributed deployment using vRSLCM.In this post I will describe about  Guidelines for Planning  vRealize Automation Backups. 

vRealize Automation Preparations for Backup 

  A system administrator backs up the full vRealize Automation installation on a regular basis. Plan the backup around efficiencies and periods of low activity.

  You can use several strategies, singly or in combination, to back up vRealize Automation system components. For virtual machines (VMs), you can use the Snapshot function to create snapshot images of critical components or use native tools like Veritas NetBackup and vSphere Data Protection. If a system failure occurs, you can use these images to restore components to their state when the images were created. Alternatively, and for non-virtual machine components, you can create copies of critical configuration files for system components, which can be used to restore these components to a customer configured state following reinstallation

vRealize Automation complete backup includes the following components  

  • IaaS components  

  1. Proxy Agents  

  2. DEM Workers 

  3. DEM Orchestrator  

  4. Manager Services  

  5. Web sites 


  •    vRealize Automation appliance
  • PostgreSQL database. Applicable only for legacy installations that do not use an embedded appliance database  
  • Infrastructure MSSQL database

    (Optional) Software load balancers

    (Optional) Load balancers that support your distributed deployment. Consult the vendor documentation for your load balancer for information about backup considerations

    Guidelines for Planning Backups


    Use the following guidelines to plan backups:

    When you back up a complete system, back up all instances of the vRealize Automation appliance and databases as near simultaneously as possible, preferably within seconds. 

    Minimize the number of active transactions before you begin a backup. Schedule your regular backup to when your system is least active. 

    Back up all databases at the same time.  
         
    When you back up the vRealize Automation appliance and the IaaS components, disable in-memory snapshots and quiesced snapshots. 

    Create a backup of instances of the vRealize Automation appliance and the IaaS components when you update certificates.


    vRealize Automation Backup Order 

    You must back up the VMs for vRealize Automation components in a specific order. 

    When you use backup tools to schedule backups for your vRealize Automation deployment, you must back up the components in the following order: 





    If you have multiple components on a VM, select the order considering the latter component on the VM from the list. 

    If vRealize Orchestrator is a standalone component, then it should be backed up in no particular order before vRealize Automation components. 


    I hope you have enjoyed reading my blog..Feel free to bookmark or post to your timeline for reference later!




   

 

 

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0

Deploy Windows VMs for vRealize Automation Installation using vRealize Suite Lifecycle Manager 2.0 In this post I am going to describe ...