ActiveImage Protector Linux 4.0 Readme
Revised on January 22, 2014
Please read the following information contained in this document
before using ActiveImage Protector.
Table of Contents
System
Requirements
Precautions
before upgrading from earlier versions (3.0/3.1/3.5)
Limitations
and Precautions
Main Memory
1024MB is required. (2048MB or above is recommended.)
* 2048MB is required in recovery environment.
Hard Disk Space
150MB or above of available hard disk space is required at setup.
* In addition to the above, the following hard disk space is
required to reserve working space in "/var/opt". Normally, the
following working space is automatically reserved when installing
the product.
- 3% of the total volume size of the device, of
which an entry is added to "/etc/fstab", is required as working
area for the snapshot (also, the working area is used when
backing up with Deduplication enabled).
- 0.01% of the total volume size of the device, of
which an entry is added to "/etc/fstab", is required as working
area to create a bitmap for incremental backups.
DVD-ROM Drive
Required to install the product and boot up in the recovery
environment.
Linux Distributions
Red Hat Enterprise Linux
- Red Hat Enterprise Linux 6.0 - 6.5 (i386,
x86_64)
- Red Hat Enterprise Linux 5.0 - 5.10 (i386,
x86_64)
* Red Hat Enterprise Linux 4 is not supported.
CentOS
- CentOS 6.0 - 6.5 (i386, x86_64)
- CentOS 5.0 - 5.10 (i386, x86_64)
* CentOS 4 is not supported.
- When installing if you get the message "You do not have
permission", after remounting with the following command try again to
install the product.
# mount -o remount,exec <device name>
- When setting up this program and the following
modules are not set up in the environment, use the “yum” command
or “rpm” command to set up the RPM package corresponding to the
following:
libstdc++.i686, libuuid.i686, glibc.i686
- If your system environment does not support
Linux Ext4, backup of large capacity (over 2TB) disks is
supported. Use the “yum” command or “rpm” command to set up RPM
package corresponding to the following:
e4fsprogs
- Before launching the GUI, the following module
must be set up. Use the “yum” command or “rpm” command to set up
the RPM package corresponding to the following:
zlib.i686, libxcb.i686, libXrender.i686, libXext.i686,
libXau.i686, libX11.i686, libSM.i686, libICE.i686, glib2.i686,
freetype.i686, fontconfig.i686, expat.i686
- Since this product includes a loadable kernel
module, it may not run on the most recent kernel version
released after this product. Before beginning the installation
of this product or updating the kernel version, please refer to
the list of evaluated kernel versions from the following link.
http://www.netjapan.co.jp/e/faq/index.php?docid=2ee414ec91157585fb9c133d41b092c9
File System
Hot Imaging
Linux Ext2 / Linux Ext3 / Linux Ext4 / Linux Swap /
Linux LVM (volume group and logical volume) / Linux RAID
* For backup image files for the file system other
than the above, a full sector backup is created.
Back to Index
Upgrade Procedures
- If nstalling ActiveImage Protector 4.0 in an
environment in which version 3.x is installed, the earlier
version is automatically uninstalled. If selecting [Yes] to [Do
you want to keep current configuration?], the current settings
for the profiles and schedules are carried over. If selecting
[No], these settings are deleted.
- If uninstalling an earlier version before
installing the version 4, please use the installer for version 4
instead of the installer for an earlier version.
- After updating from an earlier version to
version 4, a restart of the computer is not required.
Inherit setting / profiles from the earlier version
(3.0/3.1/3.5)
-
In the event that the current settings with the earlier
version (3.0/3.1/3.5) are inherited to the upgraded version,
the settings and profiles are renamed to "*.ini.3x"
and saved. When upgraded to version 4, please take the
following procedures to inherit the settings and profiles from
the earlier version.
Inherit Settings
Use vi command to open "aip.ini.3x".
Copy parameters to inherit from the file and paste them to the
corresponding positions in "aip.ini".
Inherit Profiles
Rename "*.ini.3x" in
"/opt/NetJapan/profiles" to "*.ini" and run the
following command so that the differential backup profiles are
converted to incremental backup profiles.
# /opt/NetJapan/aipdif2inc
- The profiles for backup of LVM and "Do disk
based" backup cannot be used on their own. The profiles need to
be edited as follows in order to function with version 4.0.
- Launch GUI, select [Dashboard] - [Schedule] and
edit all appropriate schedule tasks.
- Launch CUI, open [Schedule Management] page in
Backup Wizard and select [Edit a schedule].
- Once the profiles and schedule setting files are
updated, they cannot be reverted back to work with the earlier
version.
Activation Information
The information used to activate the earlier version
(3.0/3.1/3.5) is inherited to version 4.
Compatibility between Recovery Environment and Backup Images
- In a recovery environment booted from recovery
DVD created with an earlier version (3.0/3.1/3.5), backup images
created with ActiveImage Protector 4.0 cannot be restored.
- The Recovery environment of version 4 supports
restore of backup images created with an earlier version.
The Restore Wizard provided with the GUI does not support the
restore of backup images created with an earlier version. In
this case, launch the terminal and run the following command to
use the Restore Wizard provided with CUI that the earlier
version supports.
#/opt/NetJapan/aiprestore_lvm_35
Back to Index
Basic Points
Backup
and Restore
Connect
to Remote Computer
- If the [Temporary Change Tracking] option by
default is selected for [Tracking Settings], the tracking
information is purged whenever the computer is restarted. After
rebooting system, the first scheduled backup is a full backup
instead of an incremental, if this option is enabled.
Thereafter, incremental backup files are created according to
the specified schedule, associated to the created full backup.
If you need to create incremental backup even after system
reboot, please select [Preference] - [Tracking] and [Persistent
change tracking] option. To select [Persistent change tracking]
option:
- Differential backup schedule created with an
earlier version and [Do disk based] backup cannot be used with
version 4. Since LVM backup procedures have been changed with
version 4, the backup schedule inherited from the earlier
version must be edited or recreated.
- The use of fdisk command in ActiveImage
Protector Linux Edition initializes the disks recognized as
uninitialized at the following timings.
In the event that a connected disk is used as RAW device and
unpartitioned, the data in the first sector may be changed. The
disks as such need to be partitioned so that by allocating a
partition to RAW device, you should be able to avoid data loss
from the first sector.
- When `aipcontrol diskinfo` is executed.
- Backup task is started.
- Restore Wizard is launched.
- GUI is launched.
- A Backup image cannot be restored to the disk of
which sector size is different from backup source.
- ActiveImage Protector supports up to the maximum
number of 31 disks per system.
Up to the maximum number of 24 volumes per disk are supported.
Top
of the topic
- When the working area for a snapshot is not
reserved during installation, please select [Preference] -
[Snapshot] and reserve snapshot working area.
In the event that snapshot working area is not reserved, backup
by taking a snapshot or with the Deduplication Compression
feature may fail.
- AIP supports backup of the maximum size of 15TB
volume.
For example, if a 20TB disk is partitioned into 10TB and 10TB
volumes, both disk based and volume based backup are supported.
However, if the 20TB disk is not partitioned, backup of 20TB
disk is not supported.
- Since loopback device provided by the OS is
used for backup, it is necessary to change the number of
loopback devices according to the number of volumes for backup
sources.
The number of loopback devices required for backup is the number
of backup source volumes + 2.
If necessary, please change the number of loopback devices
referring to the following.
For example, to change the number of loopback
devices to 16 when OS is booted up, please add the following
command to "/etc/rc.local".
MAKEDEV -m 16 /dev/loop
-
You may not be able to restore to volumes on Software RAID(mdraid) disks
configured with mdadm. In this case, use the following command to do the
restore from aipmng(CUI).
# aipmng --restore
- If the schedule is defined and applied within
five minutes or less before the first scheduled start time, the
first task will not be executed according to the schedule.
- If the machine is restarted while backup is
being executed, the machine does not resume the aborted backup
process. The same backup task will need to be restarted.
- In the event that the schedule settings are
edited and the destination to save the image files is changed,
the file name of the image file set created in the newly
specified destination may coincide with the already existing
image files saved in the previous destination.
The consistency and sequence of the created image files are
guaranteed for an image file set saved in a single destination.
- The contents in the destination disk to restore
LVM system disk are completely purged at the same time the
restore process is started.
If a destination volume already exists, backup of the existing
destination should be created before executing the restore
process.
- If a mounted volume is specified as a restore
destination for hot restore, this volume is not automatically
mounted when restored.
To use a restored volume, the volume needs to be manually
mounted after the restore process is completed.
Top
of the topic
To connect to a remote host using ActiveImage console, the
following settings need to be configured.
Remote Host (Managed)
- Please make sure Windows Firewall (iptables)
exception settings are configured for the following TCP/UDP
ports.
When installing the ActiveImage agent, select the [Set firewall
exception] option to automatically configure the exception
settings for the following ports.
- TCP port 48236 (to connect to a remote computer)
- UDP port 48238 (to connect to a remote computer)
- UDP port 48239 (to connect to a remote computer)
- UDP port 137 (to browse shared folders)
- If using the [system-config-firewall] (firewall
setting tool provided by GUI),
please manually configure the settings to open the following
TCP/UDP ports instead of using program's installer.
- TCP Port 48236
- UDP Port 48238
- UDP Port 48239
- UDP Port 137
ActiveImage console (Managing)
Windows Firewall (iptables) exception
settings need to be configured in the same manner as described
above for remote host.
Top
of the topic
Back to Table
of Contents
Back to Index