Skip to content
CA Spectrum - 10.2 to 10.2.3
Documentation powered by DocOps

Operating Environment and Systems Setup

Last update February 20, 2018

Environment Areas of Focus

As with any memory-, CPU-, or disk-intensive, sophisticated application, CA Spectrum is susceptible to its operating environment. This environment breaks down broadly into the following categories:

Hardware

The minimum hardware requirements for the major CA Spectrum components are described in the respective installation sections. For large deployments with relatively low-cost system hardware resources, you can minimize the potential of exhausting physical resource capacity. We recommend the following hardware for a heavily loaded CA Spectrum Component:

SpectroSERVER or OneClick Server

  • Server-class, Intel-compatible or Sun hardware
  • 4 CPUs or cores running at 2 GHz or higher processor speeds
  • 16 GB (Minimum 8 GB), encompassing the following requirements:
    • 4 GB for major CA Spectrum processes
    • 2 GB for the OS
    • 2 GB for smaller CA Spectrum processes and other transient requirements
  • Locally attached disk subsystem
  • Hardware RAID (levels 1/0, 5, or 1 recommended, in that order)
  • 50 GB of available disk space
  • Physical disk using SAS or SCSI technology. We recommend 10,000 RPM minimum. 
    For Fiber Channel, SAN, or other disk technologies, the performance characteristics of the locally attached disk subsystem recommendations must be met.

Spectrum Report Manager Server

The minimum hardware requirements for Spectrum Report Manager and SpectroSERVER or OneClick are the same, except for the available disk space. Given the historical data storage nature of Spectrum Report Manager, disk space is a major consideration. For more information, see Spectrum Report Manager.

Virtualization

In a virtual environment, you can share resources to maximize your return on hardware investment. However, CA Spectrum reacts to network conditions in real time. As a result, the product requires CPU resources, memory resources, and disk speeds to be running at optimal capacity. If any one of these resources is affected because of another virtual machine, CA Spectrum performance is affected. Therefore, we recommend running CA Spectrum with CPU and memory resources that are dedicated 100 percent of the time. If you are using a storage area network, use the performance requirements that we recommend in the Hardware section.

 
Note: Do not run VMware VMotion on virtual machines (VMs) that are running CA Spectrum because CA Spectrum always requires dedicated resources. However, if you stop all CA Spectrum processes on VMs, you can run VMware VMotion on those VMs.

As a best practice for virtual machines that are used for CA Spectrum, dedicate system resources as specified in the Hardware section. For VMware environments, consider the following points:

  • Ensure that required resources are always available (reserved). Assign dedicated resource groups to the CA Spectrum virtual machines regardless of the state of other VMs that are running on the same server. Make resource group allocations according to the sizing information from the CA Spectrum Sizing Tool and the recommendations in this document.
  • Create specific RAID volumes or LUN with dedicated disks/spindles to the CA Spectrum system. These volumes help to avoid disk I/O contention with other applications that share the same RAID or storage array. Allocate large volumes of disks/spindles to the RAID volume or LUN. Larger volumes enable a greater I/O distribution and maximum read/write times for the CA Spectrum processes.
  • The VMware administrator can reserve memory and CPU resources within Clusters or Resources Pools, rather than making reservations on individual VMs.
  • On the SpectroSERVER hosts, lower CPU percent ready times were observed with two vCPUs than with four vCPUs. More vCPUs are not always better.
  • Disk access times of more than 10 (ms) noticeably affected performance on a SpectroSERVER with a significant load.
  • Do not allow the VM snapshots to continue for long periods of time. The delta implementation of snapshots can affect the SpectroSERVER performance.
  • The VM HBA assignments can also affect SpectroSERVER performance.

Basic Configuration for VMware

Set the following values from the Hardware tab on the Edit Settings dialog:

  • 2 vCPUs
  • Configured memory: 8 GB (The guest operating system assumes this value as the available physical memory)

Additional Configuration for VMware

If a VM contention affects the ESX server, set the following values from the Resources tab on the Edit Settings dialog:

  • Memory
    • Shares: High
    • Reservation: 2-4 GB (hardware-dependent; use with care)
    • Limit: Unlimited
  • CPU
    • Shares: High
    • Reservation: 0 ((hardware-dependent; use with care)
    • Limit: Unlimited

Note: When a VM is migrated (vMotion) in VMware, then the spectrumgtw probe picks the changes and sends to CA Spectrum. The changes are shown in the CA Spectrum hierarchy. The reflection time for the changes in CA Spectrum hierarchy is based on the frequency at which UIM vmware probe publishes the changes to CA UIM. This functionality is supported for both legacy integration and integration through spectrumgtw probe.

Operating System

The individual CA Spectrum processes cannot use more than 16 GB (Minimum 8 GB). However, it is best to run CA Spectrum on 64-bit variants of supported operating systems. On 64-bit variants, processes can take advantage of 16 GB (Minimum 8 GB) RAM.

Isolation

The ideal environment for the CA Spectrum servers is one in which they are not contending for resources with other processes. Moreover, avoid or thoroughly test some environments as they impact affect the performance of CA Spectrum. Such environments include Antivirus, Security software, and Backup utilities.

Also check for Automatic disk backups, operating-system backups, automatic antivirus scans, and network security scans, which affect the performance of CA Spectrum. These processes place temporary locks on files to which CA Spectrum needs constant access. Therefore, they can lead to crashes and performance issues. This guidance applies to any hardware or virtual machine where a SpectroSERVER, Archive Manager, or SRM database is deployed.

Perform automatic disk backups, operating-system backups, and operating-system updates only after gracefully shutting down all CA Spectrum processes.

Configure antivirus scans to skip the CA Spectrum root directory. If a scan of the CA Spectrum root directory is required, run it with all CA Spectrum processes gracefully stopped.

Was this helpful?

Please log in to post comments.

  1. Maik Seckler
    2017-03-20 03:03

    "The individual CA Spectrum processes cannot use more than 4 GB of RAM." That's not true anymore with Spectrum 10.

    1. Abhijit Das
      2017-03-21 06:42

      Hi Maik, Thank you for pointing this out. We're getting all the content on this page validated for accuracy, and will be making applicable updates shortly.

      Thank you, Team DocOps

      1. Maik Seckler
        2017-06-29 05:14

        Hi DocOps Team,

        what do you mean by "shortly"? The mentioned paragraph is still unchanged.

        1. Abhijit Das
          2017-06-30 08:10

          Hi Maik,

          Apologies for the delay.
          We've updated the paragraph after confirming with Engineering. Do let us know if further updates are needed.

          Thank you,
          Team DocOps

           

           

  2. KAREN BROOKS
    2017-06-04 10:33

    The link for spectrum report manager is incorrect

    1. KAREN BROOKS
      2017-06-04 10:46

      It does work - disregard.

  3. Abhijit Das
    2017-06-05 04:03

    Hi Karen,

    Thank you for following up your initial comment and confirming that the link works fine!

    Regards,
    Team DocOps

  4. Maik Seckler
    2018-08-09 03:20

    In section "https://docops.ca.com/ca-spectrum/10-2-3/en/administrating/spectroserver-performance-administration/set-user-preferences/evaluate-the-peformance-of-a-spectroserver#EvaluatethePeformanceofaSpectroSERVER-ThreadsandThreadLatency", it is mentioned that three or more CPUs can degrade performance. In this section, it is recommended to use 4 CPUs for a "heavily loaded" SpectroSERVER. Shouldn't it be 2 CPUs in that case? Please update either of the sections to make it coherent.