System Requirements - QSnap

The following requirements are for QSnap and the Unix File System iDataAgent:

The QSnap software is supported for use with a variety of different Agents. However, not all Agents support QSnap with all operating system vendors listed below. See Snapshot Engines - Support for information on supported operating system vendors for QSnap with each Agent.

Operating System

Processor

AIX

AIX 5.2 32-bit and 64-bit with technology level 10 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

AIX 5.3 32-bit and 64-bit with technology level 6 (or higher) and runtime library xlC.rte 8.0.0.0 or higher

AIX 6.1 64-bit

Power PC (Includes IBM System p)

Linux

Red Hat Enterprise Linux

Red Hat Enterprise Linux AS 3.0 with kernel 2.4.21-15 (Update 2)

Red Hat Enterprise Linux AS 3.0 with kernel RH 2.4.21-47 (Update 8)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-34 (Update 3)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-42 (Update 4)

Red Hat Enterprise Linux AS 4.0 with kernel-2.6.9-55 (Update 5)

Red Hat Enterprise Linux AS 4.0 with kernel-2.6.9-67 (Update 6)

Red Hat Enterprise Linux AS 4.0 with kernel 2.6.9-78 (Update 7)

Red Hat Enterprise Linux 5 Advanced Platform 5.0 with kernel 2.6.18-8.el5

Red Hat Enterprise Linux 5 Advanced Platform 5.0 with kernel 2.6.18-53.el5 (Update 1)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-92 (Update 2)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-128 (Update 3)

SuSE Linux

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.191-smp (Patch Level 2)

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.244 (Patch Level 3)

SuSE Linux 9.0 Enterprise Server with kernel 2.6.5-7.308 (Patch Level 4)

SuSE Linux 10 Enterprise Server Edition with kernel 2.6.16.21-0.8

SuSE Linux 10 Enterprise Server Edition with kernel 2.6.16.46-0.12

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.21 (Patch Level 2)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.34 (Update 2)

Intel Pentium or compatible minimum required

Solaris

 Solaris 8

Solaris 9 

Solaris 10

Sun Sparc5 or higher recommended

Windows

Windows XP

Microsoft Windows XP Professional 32-bit Edition with Service Pack 1 or 2

Windows 2003

Microsoft Windows Small Business Server 2003 Premium 32-bit Edition up to Service Pack 2

Microsoft Windows Server 2003 Standard 32-bit Edition up to Service Pack 2

Microsoft Windows Server 2003 Enterprise 32-bit up to Service Pack 2

Microsoft Windows Server 2003 Enterprise x64 Edition up to Service Pack 2

Microsoft Windows Server 2003 Web Server 32-bit Edition up to Service Pack 2

Microsoft Windows Storage Server 2003 32-bit Edition up to Service Pack 2

Microsoft Windows Server 2003 Enterprise 64-bit Edition up to Service Pack 2

Windows Vista

Microsoft Windows Vista Ultimate 32-bit Edition

Microsoft Windows Vista Ultimate x64 Edition

Windows 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

Microsoft Windows Server 2008 R2 Editions*

*Core Editions not supported

All Windows-compatible processors supported

Cluster Support

See Clustering - Support

Memory

Unix

16 MB RAM minimum required beyond the requirements of the operating system and running applications

Swap space = 2*RAM size

Windows

32 MB RAM minimum required beyond the requirements of the operating system and running applications. Additional memory used when a snapshot is created, varying by File System activity and the amount of data being backed up.

Hard Disk

Unix

225 MB minimum of hard disk space for software

100 MB of additional hard disk space for log file growth

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

Windows

99 MB minimum of hard disk space for software/ 99 MB recommended

100 MB of additional hard disk space for log file growth

100 MB of temp space or more on the source volume(s) to create snapshots and keep snapshot specific data

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

Peripherals

DVD-ROM drive

Network Interface Card

Miscellaneous

Unix

TCP/IP Services configured on the computer.

The operating system must have been installed with at least the user level software option selected

If you have SELinux enabled on the client computer, create the SELinux policy module as a root user before performing a backup. The SELinux Development package must be installed on the client.

To create SELinux policy module, perform the following steps as user "root":

  1. Create the following files in the /usr/share/selinux/devel directory:
File Name Content of the file
<directory>/<file_name>.te

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.te

 

 The content of the file should be as follows:

policy_module(<name>,<version>)

##############################

where:

<name> is the name of the policy module. You can give any unique name to the policy module, such as a process or application name.

<version> is the version of the policy module. It can be any number, such as 1.0.0.

For Example: While creating a policy module for the backup_IDA application, you can use the following content.

policy_module(backup_IDA,1.0.0)
<directory>/<file_name>.fc

where:

<directory> is /usr/share/selinux/devel

<file_name> is the name of the Unix file, created to save the policy module statement. It is a good idea to use the same name for policy module and the file.

For example: When you are creating a policy module for backup_IDA application, you can use the following file name: backup_IDA.fc

 

 The content of the file should be as follows:

Note that the following list of files is not exhaustive. If the process fails to launch, check /var/log/messages. Also, if required, add it to the following list of files.

/opt/<software installation directory>/Base/libCTreeWrapper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libCVMAGuiImplgso -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2locale.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2osse.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDb2Sbt.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libdb2trcapi.so.1 -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libDrDatabase.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libIndexing.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

/opt/<software installation directory>/Base/libSnooper.so -- gen_context(system_u:object_r:texrel_shlib_t,s0)

 
  1. Create the policy file from command line. Use the following command. Ensure that you give the following commands in the /usr/share/selinux/devel directory.

[root]# make backup_IDA.pp

Compiling targeted backup_IDA module

/usr/bin/checkmodule: loading policy configuration from tmp/backup_IDA.tmp

/usr/bin/checkmodule: policy configuration loaded

/usr/bin/checkmodule: writing binary representation (version 6) to tmp/backup_IDA.mod

Creating targeted backup_IDA.pp policy package

rm tmp/backup_IDA.mod tmp/backup_IDA.mod.fc

[root]# semodule -i backup_IDA.pp

[root]#

  1. Execute the policy module. Use the following command:

[root]# restorecon -R /opt/<software installation directory>

SELinux is now configured to work with this application.

Windows

TCP/IP Services configured on the computer.

Notes on Linux Installations

If you are installing the software on a computer running Red Hat Linux version 5, you must first enter the following command into the /etc/rc.d/rc.sysinit file.

/etc/init.d/cxbf start

This command should be entered before the local non-root file systems are checked.

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors may, in some cases, affect the working of our software. Although we may list such revisions and/or service packs as “supported” in our System Requirements, changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. However, we will make every effort to correct such disruption as quickly as possible. When in doubt, please contact your software provider to ensure support for a specific application or operating system.

Additional considerations regarding minimum requirements and End of Life policies from application and operating system vendors are also applicable.