Deprecated
-
This product is deprecated in this release. This functionality is now available using block-level backup.
-
New installations for this product are not supported in this release. Upgrade is supported to perform restores only. For instructions on transitioning from Image Level to block-level backups, see Transitioning from Image Level to Block-Level Backups.
See Deprecated Features, Products, and Platforms for information on deprecated products.
The following requirements are for the Image Level agent:
Note: For details about the operating systems and applications supported by the Image Level Agent, see Image Level - Application Support.
Operating System |
Operating System Version |
Architecture |
---|---|---|
AIX |
AIX 7.1 64-bit |
PowerPC (including IBM System p) |
AIX 6.1 TL 02 SP00 or higher, 64-bit |
PowerPC (including IBM System p) |
|
Linux |
Debian |
|
Debian 5.x with kernel 2.6.26-2 |
|
|
Debian 5.x with kernel 2.6.26.19-2 |
x64 |
|
Debian 4.x with kernel 2.6.18-686 |
|
|
Debian 4.x with kernel 2.6.18-6 |
x64 |
|
Red Hat Enterprise Linux |
||
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-71 |
|
|
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-71 |
x64 |
|
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-279 (Update 3) |
x64 |
|
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-279 (Update 3) |
|
|
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-220 (Update 2) |
x64 |
|
Red Hat Enterprise Linux 6 Advanced Platform with kernel 2.6.32-220 (Update 2) |
|
|
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-92 (Update 2) |
x64 |
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-308 (Update 8) |
x64 |
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-308 (Update 8) |
|
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-274 (Update 7) |
|
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-274 (Update 7) |
x64 |
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-238 (Update 6) |
x64 |
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-238 (Update 6) |
|
|
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-194 (Update 5) |
x64 |
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-164 (Update 4) |
x64 |
|
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-128 (Update 3) |
x64 |
|
Red Hat Enterprise Linux 5 Advanced Platform with kernel 2.6.18-128 (Update 3) |
|
|
SuSE Linux (SLES) |
||
SuSE Linux 11 Enterprise Server with kernel 2.6.32.12-0.7 (Update 1) |
|
|
SuSE Linux 11 Enterprise Server with kernel 2.6.32.12-0.7 (Update 1) |
x64 |
|
SuSE Linux 11 Enterprise Server with kernel 2.6.27.19-5 |
x64 |
|
SuSE Linux 11 Enterprise Server with kernel 2.6.27.19-5 |
|
|
SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.54.5 (Update 3) |
x64 |
|
SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.54.5 (Update 3) |
|
|
SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.21 (Update 2) |
x64 |
|
SuSE Linux 10 Enterprise Server with kernel 2.6.16.60-0.21 (Update 2) |
|
|
SuSE Linux 10 Enterprise Server with kernel 2.6.16.46-0.12 (Update 1) |
|
|
SuSE Linux 10 Enterprise Server with kernel 2.6.16.46-0.12 (Update 1) |
x64 |
|
Solaris |
Solaris 10.x with a minimum of SunOS (Sparc) Patch 119963-14 and 119689-06 |
UltraSPARC-II or more recent recommended |
Windows |
Windows 2012 |
|
Microsoft Windows Server 2012 R2 Editions |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2012 Editions |
All Windows-compatible processors are supported |
|
Windows 2008 |
||
Microsoft Windows Server 2008 R2 Editions Server Core installations are not supported. |
All Windows-compatible processors are supported |
|
Microsoft Windows Server 2008 32-bit and x64 Editions Server Core installations are not supported. |
All Windows-compatible processors are supported |
|
Windows Vista |
||
Microsoft Windows Vista 32-bit and x64 Editions |
All Windows-compatible processors are supported |
|
Windows XP |
||
Microsoft Windows XP Professional Edition 32-bit with a minimum of Service Pack 3 |
All Windows-compatible processors are supported |
Cluster Support
You can install the software on a cluster, if clustering is supported by the operating system. For information about supported cluster types, see Support for Cluster Configuration.
Hard Drive
Image Level on UNIX
1 GB minimum disk space for software installation.
10 GB of free disk space is required for job result directory.
1 GB of free disk space is required for log directory.
Image Level on Windows
1 GB minimum disk space for software installation.
10 GB of free disk space is required for job result directory.
500 MB of free disk space is required for log directory.
AIX LPAR/WPAR
Data protection on Logical Partitioning (LPAR) and Workload Partitioning (WPAR) is supported.
Miscellaneous
The File System iDataAgent will be automatically installed during installation of this software, if it is not already installed. For System Requirements and install information specific to the File System iDataAgents, refer to:
On Solaris computers, the operating system must have been installed with at least the user level software option selected.
.NET Framework
.NET Framework 4.0 is automatically installed. Note that .NET Framework 4.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 an 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.
Microsoft Visual C++
The following Redistributable Packages are installed automatically. Note that the Redistributable Package can co-exist with other versions of this software.
Microsoft Visual C++ 2010 Redistributable Package
Supported UNIX File Systems and Restore Types
The following table lists the file systems and restore types supported for each supported operating system:
File System |
Operating System |
CXBF |
Checksum |
Back Up Data Blocks Only |
Volume Restore |
File Restore |
|
CXBF |
Checksum |
||||||
Unix File System (UFS) Includes read-only partitions on Unix, as long as the production server and backup host are configured as the same computer |
Solaris |
X |
X |
X |
X |
||
Extended 2 File System (ext2) |
Linux |
X |
X |
X |
X |
X |
|
Extended 3 File System (ext3) |
Linux |
X |
X |
X |
X |
X |
|
RAW volumes |
Linux Solaris |
X |
X |
||||
Reiser File System (reiserfs) |
Linux |
X |
X |
X |
|||
VERITAS File System (VxFS) |
AIX |
X |
X |
||||
VERITAS File System (VxFS) |
Solaris |
X |
X |
||||
Veritas Volume Manager (VxVM) |
Solaris |
X |
X |
X |
X |
||
Journal File System (JFS2) |
AIX |
X |
X |
X |
X |
X |
X |
'X' File System (XFS) |
Linux |
X |
X |
X |
Notes
-
The Unix File System snapshots cannot be backed up by non-CXBF backup jobs. The Unix QSnap® (cxbf) driver does not support volumes created by Solaris Volume Manager.
-
On AIX clients, Data Blocks Only backups are supported for full backups only.
-
The Image Level iDataAgent on Unix can perform a File Level Restore only when the OS of the Client computer and the MediaAgent are the same.
For a complete listing of applications supported for each operating system, see Image Level - Application Support.
Supported Windows File System Types
Backed up File System Type |
File-Level Restore Destination |
Volume-Level Restore Destination |
|||||
---|---|---|---|---|---|---|---|
RAW |
FAT |
NTFS |
RAW |
FAT |
NTFS |
ReFS |
|
RAW |
|||||||
FAT |
|||||||
NTFS |
|||||||
ReFS |
Notes
-
For Windows, when volumes are backed up using the Image Level agent, sharing attributes for volumes and folders are not retained.
For Windows, file-level restores require the MediaAgent Index Cache to reside on an NTFS partition. In the case of a MediaAgent whose Index Cache resides on a FAT partition, use volume-level restores.
DISCLAIMER
Certain third-party software and service releases (together, “Releases”) may not be supported by Commvault. You are solely responsible for ensuring Commvault’s products and services are compatible with any such Releases.