> CommCell Console > Backup and Restore Agents > Snapshot Management > Solutions > IRM > Getting Started

IntelliSnap Recovery Manager (IRM) - System Requirements

IRM server should follow these system requirements:

Configuration

Details

Computer / Processor

  • x64 capable CPU minimum required 5

  • Allocate multiple virtual CPUs to a virtual machine, if the anticipated SQL Server workload can take advantage of all the virtual CPUs

Memory

  • 8 GB RAM minimum required / 32 GB RAM recommended

  • Virtual Memory should be set to twice the amount of available physical memory. Memory page sharing and memory ballooning must be enabled on the virtual machine

Hard Disk

  • 2.5 GB of log disk space for installing the software and future data growth

  • 2.2 GB of temp space on the drive on which the Operating System and temp directory resided (This space is used for temporary files copied during the installation or upgrade of the Microsoft SQL Server and CommServe software)

  • 1.5 GB of permanently available disk space on a local or mapped network drive for CommServe Disaster Recovery

  • 100GB of index cache space is required locally to temporarily store the index data

  • SQL Data files and log files must reside on different disks (different VMFS). It is recommended to place the log files on RAID 1+0 or RAID 1 disks

Disk Library

1TB of disk storage is required for the Disk Library to store the Index:

  • Network Attached Storage

    • Exclusive 10 GigE port

    • 7200 rpm SAS spindles

  • Direct Attached Storage

    • SAS (6GB HBA) / FC (8GB HBA) / iSCSI (Exclusive 10GigE)

    • 7200 rpm SAS or SATA

    • Minimum RAID-5 with 7 spindles each

    • Dedicated Storage Adapters

Operating System

  • Windows Server 2008 (x64 editions) and 2008 R2 1 2 5

  • Windows Server 2012 and 2012 R2
  1. Core Editions are not supported.
    2. Hyper-V Editions are not supported. However the CommServe may be installed within a Virtual Machine
    3. Make sure to use the VMXNET virtual network adapter and separate virtual switches, each connected to its own physical network adapter
    4. No DHCP support for the CommServe
    5. IA64 is not supported

Storage Arrays Supported By IRM

For Supported Storage Arrays by IRM, see IntelliSnap Support.

Note that the NetApp SnapVault/SnapMirror feature requires the NetApp Snap Management license.

Agents Supported by IRM

The following agents are supported by IRM.

Agents

Supported Versions

Cluster Support

Notes

File System Agent

  • Windows Server 2003

  • Windows Server 2008

  • Windows Server 2008 R2

  • Windows Server 2012

  • Windows Server 2012 R2

  • Microsoft

  • Non-Microsoft

  • 1.5 GB Recommended for Software

  • 1 GB for log growth

  • 1 GB of temp space for install or upgrade

  • Non-Microsoft Cluster supports VERITAS Cluster and HP Scalable NAS/PolyServe Cluster

Microsoft SQL Server

  • Microsoft SQL Server 2005 Editions

  • Microsoft SQL Server 2008 Editions

  • Microsoft SQL Server 2008 R2 Editions

  • Microsoft SQL Server 2012 Editions

  • Microsoft

  • Non-Microsoft

  • 170 MB minimum of hard disk space for software/ 498 MB recommended

  • 50 MB of additional hard disk space for log file growth

  • 724 MB of temp space required for install or upgrade (where the temp folder resides)

  • Microsoft Cluster supports Geo-Dispersed Cluster

  • Non-Microsoft Cluster supports VERITAS Cluster and HP Scalable NAS/PolyServe Cluster

Microsoft Exchange Server

  • Microsoft Exchange 2007 64-bit Server

  • Microsoft Exchange 2010 64-bit Server

  • Microsoft Exchange 2013 64-bit Server

  • Microsoft

  • Non-Microsoft

  • 114 MB minimum of hard disk space for software/ 498 MB recommended

  • 50 MB of additional hard disk space for log file growth

  • 726 MB of temp space required for install or upgrade (where the temp folder resides)

  • Microsoft Cluster supports Geo-Dispersed Cluster

  • Non-Microsoft Cluster supports VERITAS Cluster

Virtual Server

VMware vSphere 4 and Up
Offline Mining Support

Agents

Supported Versions

Notes

SharePoint Document

MOSS 2007

WSS v3.0

SharePoint 2010 Foundation

SharePoint Server 2010

Exchange Mailbox

Microsoft Exchange 2007 64-bit Server

Microsoft Exchange 2010 64-bit Server

Microsoft Exchange 2013 64-bit Server

Support is for Mailbox-level recovery for Snapshots of Exchange Database

Supported Configuration

The IRM CommCell components are supported in a physical and virtual deployment assuming the recommended requirements are met for resource allocation in both configurations. However, the storage environment and storage connectivity options utilized in the managed deployment will determine the requirement for a physical or virtual IRM CommCell configuration.

IRM requires snapshots to be mounted after successful creation to complete the indexing activities. This enables CommCell to provide a stream lined recovery mechanism for all storage arrays under management. These snapshots can be mounted back to the original host that created them (the production host) or they may leverage a proxy server (off host) to offload this operation to. The CommCell is typically a feasible off host option for executing this indexing operation. However there are a few details to keep in mind:

  1. IRM does not currently support creating or mounting snapshots of Fibre Channel physical RDMs.

  2. IRM cannot mount snapshots of Fibre Channel devices from a physical server to a virtual machine.

  3. If a Fibre Channel device is being snapped and the CommCell is virtual, the production host, or an alternate physical server with array masking and access defined must be used.

  4. An alternate physical server or the production host will need to be used for processing ESEUtil consistency checks for Exchange Databases with Fibre Channel devices.

  5. iSCSI configurations are supported for both snapshot creation and mounting from a physical RDM.

  6. iSCSI snapshots from a physical host device may also be direct mounted to a virtual machine and is supported.

×

Loading...