LiveVault Information: V7.7 System Requirements

Operating System

• Microsoft Windows Server 2012

• Microsoft Windows Server 2008, 32-bit and 64-bit

• Microsoft Windows Server 2008 R2

• Microsoft Windows Server 2003 32-bit and 64-bit SP1 and higher.

• Microsoft Windows Small Business Server 2003 Premium 32-bit and 64-bit SP 1 and higher

• VMware ESX 2.5.3, 3.0, 3.5, 4.1 and 5. Supported operating systems above running as Guests.

• HyperV Supported operating systems above running as Guest operating systems.

• Windows Server 2008 32-bit and 64-bit

• Windows Server 2008 R2

• Windows Server 2003 32-bit and 64-bit R2 Service Pack 1 or higher

File System

• NTFS on Windows 2003, Windows 2008, Windows 2008 R2 and Windows 2012.

• Resilient File System (ReFS) on Windows 2012.

• NTFS on Windows 2012.

• Volumes optimized for data deduplication on Windows 2012.

For more information on Windows 2012, ReFS and data deduplication, refer to your Windows documentation.

Additional RAM

128 MB of free memory under normal load.

Available Disk Space for Snapshot Cache

15% to 20% free space to allow proper Volume Shadow Copy Service (VSS) function and prevent excessive fragmentation.

CloudRecover recommends that VSS be configured to use a maximum size limit rather than be allowed to use unlimited shadow copy storage on the volume(s). By default, the maximum size use limit is 10% of the drive(s) where the snapshots are stored. Adjust the settings accordingly.

For more information on configuring VSS snapshot limits, refer to your Windows documentation.

CloudRecover recommends you to select a location other than your root drive for the backup database files during installation of the agent software.

The backup database files can grow to consume a lot of space, depending on the number of backup policies you create and the amount of data you are backing up. Optimally, the volume for the data directory should  have at least 5 GB free disk space.

CloudRecover recommends you install the data directory to a NTFS or ReFS formatted volume on Windows Server 2012.

• Microsoft SQL Server 2012 Standalone on all operating systems supported by Microsoft.

• Microsoft SQL Server 2012 Enterprise AlwaysOn Availability Groups on all operating systems supported by Microsoft. Primary and secondary replicas.

• Microsoft SQL Server 2008 R2 32-bit and 64-bit on Microsoft Windows 2003, Microsoft Windows 2008 and Microsoft Windows 2008 R2

• Microsoft SQL Server 2008 32-bit and 64-bit on Microsoft Windows 2003, Microsoft Windows 2008 and Microsoft Windows 2008 R2

• Microsoft SQL Server 2005 32-bit and 64-bit on Microsoft Windows 2003, Microsoft Windows 2008 and Microsoft Windows 2008 R2

• Microsoft Exchange 2010 SP1 Standalone on all operating systems supported by Microsoft.

• Microsoft Exchange 2010 SP1 DAG  on all operating systems supported by Microsoft.

• Microsoft Exchange 2007 SP2/SP3 Standalone on Microsoft Windows 2003 SP1 or higher or Windows 2008 64-bit.

• Microsoft Exchange 2007 SP2/SP3 CCR on Microsoft Windows 2003 SP1 or higher or Windows 2008 64-bit.

• Microsoft Exchange 2003 SP2 on Microsoft Windows 2003 SP1 or higher

• Microsoft Exchange 2003 SP2 on Windows Small Business Server 2003 SP1 or higher.

• Microsoft Data Protection Manager (DPM) 2010 (English-only)

• Microsoft Data Protection Manager (DPM) 2007 SP1 (English-only)

A CIFS Collector Agent computer must meet all of the following requirements to protect NAS devices and CIFS share data:

• Windows Server 2008 R2 operating system.

• Windows Server 2012 operating system.

• 4 GB RAM or higher.

• Dedicated, single use, server. No other applications should be installed on the CIFS collector agent computer. The file system and system state of a CIFS collector agent cannot be protected by CloudRecover Backup and Recovery Service  as it is acting as a collector for NAS device and CIFS share data.

• Standalone server. Clustered servers are not supported as CIFS collector agents.

  Note: The CIFS Collector Agent can be a virtual machine as long the virtual hardware and storage meet all of the system requirements above.

• Data Directory Disk Space. The CIFS backup database files can grow to consume a lot of space, depending on the number of CIFS backup policies you create and the amount of data you are backing up. Optimally, the volume for the data directory should  have the larger of 1 percent of the CIFS data under protection or 10 GB free disk space.

  For example:

  • 1 TB or less protected data requires 10 GB of free space on the volume containing the data directory.

  • 2 TB protected data requires 20 GB of free space on the volume containing the data directory

• Domain member of the same domain as the NAS devices to be protected.

• Administrator role on the Collector Agent computer.

• Administrative privileges to access the volumes on the CIFS shares.

A Virtual Machine Collector computer must meet all of the following requirements to protect virtual machines:

• Windows Server 2008 R2 operating system.

• 4 GB RAM or higher.

• Dedicated server. No other applications should be installed on the Virtual Machine Collector computer. The file system and system state of a Virtual Machine Collector cannot be protected by CloudRecover Backup and Recovery Service as it is acting as a collector for virtual machine data.

• Note: The Virtual Machine Collector can be a virtual machine as long the virtual hardware, storage and network meet all of the system requirements.

• Data Directory Disk Space. The  backup database files can grow to consume a lot of space, depending on the number of virtual machine backup policies you create and the amount of data you are backing up. Optimally, the volume for the data directory should  have the larger of 1 percent of the virtual machine data under protection or 10 GB free disk space.

  For example:

  • 1 TB or less protected data requires 10 GB of free space on the volume containing the data directory.

  • 2 TB protected data requires 20 GB of free space on the volume containing the data directory

VMware  5.0 and 5.1.

Sufficient vSphere privileges to  create, manage and administer the following items in vSphere:

• Datastores

  • Allocate space

  • Browse datastore

  • Low level file operations

  • Remove file

  • Rename datastore

• Folder

  • Delete folder

  • Rename folder

• Global

  • Disable methods

  • Enable methods

  • Licenses

• Host

  • Configuration -> Maintenance

  • Inventory -> Add standalone host

• Network -> Assign network

• Resource

  • Assign virtual machine to resource pool

  • Remove resource pool

  • Rename resource pool

• Sessions -> validate session

• vApp

  • Delete

  • Rename

  • Add virtual machine

• Virtual machine

  • Revert to snapshot

  • Configuration

  • Answer question

  • Power off

  • Power on

  • Create new

  • Register

  • Remove

  • Unregister

  • Provisioning *

  • Create snapshot

  • Remove snapshot

For more information on user account privileges in VMware vCenter™, refer to your vCenter documentation

For VMware’s Changed Block Tracking (CBT) to identify disk sectors in use with the special "*" change ID, the following items are required:

• The virtual disk must be located on a VMFS volume, backed by SAN, iSCSI, or local disk. RDM is not VMFS.

• The virtual machine must have zero (0) snapshots when CBT is enabled, for a clean start.

For more information, refer to your VMware documentation.

For snapshot quiescence, the following item is required:

• VMware Tools installed on the virtual machines to be protected. For more information on installing VMware Tools, refer to your VMware vSphere documentation.

Due to differences in the hardware supplied by original equipment manufacturers (OEMs),  CloudRecover recommends that you configure backup to protect volume and folder data.

Do not configure backup to protect the System State and operating system volume.

Disaster recovery of Windows Storage Server is not supported or recommended.

To recover a Windows Storage Server computer, rebuild the computer with the assistance of your OEM, and then submit a restore request for the computer's data.

openSUSE Linux 10.0, 32-bit

Red Hat: ext2 and ext3

SUSE Linux ReiserFS

256 MB of free memory under normal load

1 TB recommended maximum data protected.

The guidelines above should provide acceptable performance and incident-free service in most environments, assuming capable hardware and fewer than 1 million files on the system. However, various factors can impact the actual backup performance, including the following:

• Disk throughput

• Number of files on the computer

• Number of files open during the file system scan

• Size of the files open during the file system scan

These and other factors, and your own tolerance for backup times should determine how much data you protect on a single server with the CloudRecover Backup and Recovery Service software.

Windows 2003 Server (32-bit)

Windows 2008 Server (32-bit)

To support the offline restore of data from clustered CloudRecover agents:

• The ORW must be installed on a system outside the cluster. It cannot be installed on any of the cluster nodes.

• The ORW uses the 32-bit agent to restore data on one of the clustered nodes.

• The clustered node the ORW restores to must have all cluster resources. You should shut down all the other nodes on the cluster. This will keep the resources with that node being restored.