Operating System
|
Processor
|
Unix
|
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 RISC |
HP-UX
HP-UX 11.00 32-bit and 64-bit with OS patch PHCO26960 (contact Hewlett
Packard to obtain the patch)HP-UX 11.11 32-bit and 64-bit with OS
patch PHCO29328 (contact Hewlett Packard to obtain the patch)
HP-UX 11.23
64-bit
|
PA RISC |
Linux
Red Hat Linux AS 2.1 32-bit with kernel RH 2.4.9-e.3 and glibc 2.2.4-26 |
Intel Pentium or compatible minimum required |
Solaris
Solaris 7 32-bit and 64-bit with Service Packs 106300-17,
106327-16 and 106950-21Solaris 8 32-bit and 64-bit with Service Packs 108434-09, 108435-09,
and 109147-20
Solaris 9 32-bit and 64-bit with Service Packs 111711-02 and
111712-02
Solaris 10 64-bit |
Sun Sparc5 or higher recommended |
Tru64
Tru64 OSF1 Release 5.1B-3
Tru64 OSF1 Release 5.1B-4
|
Compaq® (DEC) AlphaServer DS Series computer or higher
recommended |
NetWare
|
NetWare 6.0 with Support Pack 5 |
Intel Pentium or compatible minimum required |
|
Media Explorer is installed on a NetWare server using a Novell
client computer with Novell Client 4.9 on one of the following operating systems: Microsoft Windows 2000 Professional with Service Pack 2, 3
or 4
Microsoft Windows 2000 Server with Service Pack 2, 3 or 4
Microsoft Windows 2000 Advanced Server with Service Pack 2,
3 or 4
Microsoft Windows XP Professional
Microsoft Windows Server 2003 Enterprise 32-bit Edition up to Service
Pack 1
|
Windows
|
Windows 2000
Microsoft Windows 2000 Professional with Service Pack 2, 3 or 4Microsoft Windows 2000 Server with Service Pack 2, 3 or 4
Microsoft Windows 2000 Advanced Server with Service Pack 2, 3 or 4
Microsoft Windows 2000 Datacenter Server |
Intel Pentium or compatible minimum required |
Windows XP
Microsoft Windows XP Professional 32-bit Edition with
Service Pack 1 or 2 |
Intel Pentium or compatible minimum required |
Microsoft Windows XP Professional x64 Edition* with Service Pack 2 or
higher |
x64 |
Windows Server 2003
Microsoft Windows Server 2003 Standard 32-bit Edition
up to Service Pack 1Microsoft Windows Server 2003 Enterprise 32-bit Edition up to Service
Pack 1
|
Intel Pentium or compatible minimum required |
Microsoft Windows Server 2003 Standard x64* Edition
up to Service Pack 1 Microsoft Windows Server 2003 Enterprise x64* Edition up to Service
Pack 1
|
x64 |
* Media Explorer is a 32-bit component that can be installed on x64
platform. |
Hard Disk
50 MB of additional hard disk space for the Media Explorer
installation files and log growth
Sufficient space for the Catalog database (based on your cataloging
needs)
Sufficient space for the data you want to recover |
Peripherals
DVD-ROM driveNetwork Interface Card |
Miscellaneous
Media Explorer must be installed on a computer that has the same operating
system as that of the client for which the data was backed up.
The appropriate application software (e.g., Oracle, Lotus Notes,
etc.) must be installed on the client computer for which the data is
being recovered.
- Note that an Exchange database may be restored to a computer other than
the computer from which the data originated and subsequently copied back
to the Exchange Server provided the data has not changed and the appropriate
commands are executed.
The following media requirements apply:
- All necessary tape, optical, and magnetic media volumes required
to complete the data recovery operation must be available.
- For tape and optical libraries, the correct drivers must be loaded.
For HP-UX and Tru64 platforms, system drivers are used for the
appropriate tape libraries.
- Direct physical access to the media device must be available. (i.e.,
a locally attached tape library/drive tapes, or a mapped local drive on
which magnetic library archives are stored)
- For NetWare recovery scenarios, both the NetWare server and
Novell client computer running Media Explorer must have dedicated
tape drives attached.
Note that a single tape drive may be shared
between the NetWare server and Novell client computer as long as the
drive is alternated between the two computers as appropriate.
- For data stored on magnetic volumes using a NetWare or Unix
MediaAgent, a separate file transfer tool (such as FTP for Unix)
must be use
Note that all of the platforms stated above may not be supported by this Agent.
For information on the list of supported platforms, refer to the System
Requirements specific to this Agent.
For information on the Agents supported by Media Explorer, see
Media Explorer - Support.
.NET Framework 2.0 is automatically installed. Note that .NET
Framework 2.0 can co-exist with other versions of this software.
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":
- 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) |
- 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]#
- Execute the policy module. Use the
following command:
[root]# restorecon -R /opt/<software
installation directory>
SELinux is now configured to work
with this application.
|