System Requirements - Data Classification Enabler for Unix

The following requirements are for Data Classification:

Operating System

Processor

AIX

AIX 7.1

Power PC (Includes IBM System p)

AIX 6.1

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

HP-UX

HP-UX 11i v3 (11.31)

Intel Itanium

HP-UX 11i v2 (11.23)

HP-UX 11i v3 (11.31)

PA-RISC

HP-UX 11i v2 (11.23)

Linux

Red Hat Enterprise Linux

Red Hat Enterprise Linux AS/ES 4.0 (Update 5)

Intel Pentium or compatible minimum required

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

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-42 (Update 4)

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

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)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update 4)
 

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

  
 

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-238 (Update 6)

  

Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-71

Red Hat Enterprise Linux AS/ES 4.0 (Update 5)

x64

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

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-42 (Update 4)

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

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)

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update 4)
 

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

  
 

Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-238 (Update 6)

  
 

Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-71

  

Red Hat Enterprise Linux/CentOS

Red Hat Enterprise Linux/CentOS 5 Advanced Platform with glibc 2.5.x

Intel Pentium or compatible minimum required

Red Hat Enterprise Linux/CentOS 5 Advanced Platform with glibc 2.5.x

x64

SuSE Linux

SuSE Linux 11 Enterprise Server with kernel 2.6.27.19-5

Intel Pentium or compatible minimum required

SuSE Linux 11 Enterprise Server with kernel 2.6.32.12-0.7 (Update 1)

SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.54.5 (Patch Level 3)

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.46-0.12 (Patch Level 1)

SuSE Linux 11 Enterprise Server with kernel 2.6.27.19-5

x64
 

SuSE Linux 11 Enterprise Server with kernel 2.6.32.12-0.7 (Update 1)

  

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.46-0.12 (Patch Level 1)

Solaris

Solaris 9 with a minimum of Service Packs 111711-02

Sun Sparc5 or higher recommended

Solaris 8 [Extended Support]

Solaris 10.x

Solaris 10.x

x64

Windows

Windows 7

Microsoft Windows 7 32-bit and x64 Editions

All Windows-compatible processors supported

Windows Server 2003

Microsoft Windows Server 2003 32-bit and x64 Editions with a minimum of Service Pack 1

Windows Server 2008

Microsoft Windows Server 2008 32-bit and x64 Editions*

*Core Editions not supported

Windows Vista

Microsoft Windows Vista 32-bit and x64 Editions

Windows XP

Microsoft Windows XP Professional 32-bit and x64 Editions

Cluster Support

The software can be installed on a Cluster if clustering is supported by the above-mentioned operating systems.

Hard Drive
For Windows, the meta database of each NTFS volume is located at the C:\System Volume Information\Bull Calypso\Data Classification directory and it is named named as dc_<instance_number>.db. It takes 15 MB for every 100,000 files/folders on that volume with the default Indexes.

The metafiles (databases) created by Data Classification usually consume about 5% of the total space on the hard disk. Depending on the type of data and folder layout, the metafiles may consume additional space.

Memory
8 MB plus an additional 8-13 MB for each NTFS volume minimum required.

SRM Support

See System Requirements - SRM Windows File System Agent

Peripherals
DVD-ROM drive
Network Interface Card

Miscellaneous

Network

TCP/IP Services configured on the computer.

Services

Task Scheduler services configured on the computer.

Unix File System Types Support

The Data Classification Enabler on Unix supports the following file system types:

Supported File System(s)

Platform Associated with the Enabler
Enhanced Journal File System (JFS2) AIX
Extended 2 File System (ext2) Linux
Extended 3 File System (ext3) Linux
Extended 4 File System (ext4) Linux
Reiser File System (ReiserFS) Linux
Unix File System (UFS) HP-UX, Solaris
VERITAS File System (VxFS), AIX, HP-UX, Solaris
Journal File System (JFS) AIX
'X' File System (XFS) Linux
Zettabyte File System (ZFS) Solaris
The Data Classification Enabler will not monitor the following File Systems automatically:
  • For Linux : Reiser File System (ReiserFS), Extended 4 File System (ext4)
  • For AIX : Journal File System (JFS)

Use the following command to add the above file systems into monitoring:

./dccmd -add-fstype <fstype>

Example: ./dccmd -add-fstype jfs -- ./dccmd -add-fstype reiserfs

Microsoft Visual C++

Microsoft Visual C++ 2008 Redistributable Package is automatically installed. Note that Visual C++ 2008 Redistributable Package can co-exist with other versions of this software.

.NET Framework

.NET Framework 2.0 is automatically installed. Note that .NET Framework 2.0 can co-exist with other versions of this software.

SELinux

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.

DISCLAIMER

Minor revisions and/or service packs that are released by application and operating system vendors are supported by our software but may not be individually listed in our System Requirements. We will provide information on any known caveat for the revisions and/or service packs. In some cases, these revisions and/or service packs affect the working of our software. Changes to the behavior of our software resulting from an application or operating system revision/service pack may be beyond our control. The older releases of our software may not support the platforms supported in the current release. However, we will make every effort to correct the behavior in the current or future releases when necessary. Please contact your Software Provider for any problem with 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