CAUTION:
Thin Image snapshot operations default to
Provisioned using floating device. In versions prior to 6.5, this
setting would automatically fallback to Fully provisioned if the
hardware storage device did not support floating devices. With the introduction of Cascade mode snapshots in version 6.5 (now the default mode), this
automatic fallback has been removed. Consequently:
- Data flows created in versions prior to 6.5 that contain Thin Image snapshot operations, with cascade mode is enabled, will now fail if the underlying hardware does not support floating device. These data flows must be manually reconfigured to use the correct provisioning type. Please note that if these data flows also contain replication operations, then these will be re-evaluated when the modified data flows are re-activated.
- Data flows created in versions prior to 6.5 that contain Thin Image snapshot operations, with cascade mode enabled, will now fail if the P-VOLs have any pre-existing non-cascade mode snapshots. If cascade mode is to remain enabled then any non-cascade mode snapshots must be deleted.
- For data flows created in version 6.5 or later, if the hardware storage device on which Thin Image snapshot operations are performed does not support Floating device and Cascade mode, then Thin Image operations will fail, unless the appropriate settings are selected in the respective data flows.
CAUTION:
- Refer to the Protector support matrices at https://www.hitachivantara.com/en-us/products/data-protection/data-instance-director.html#tech-specifications before attempting installation, to ensure that you understand the infrastructure requirements, available functionality and upgrade paths for your particular environment.
- If you intend to use Protector with Hitachi storage hardware then refer to the following before proceeding:
- Hitachi Block prerequisites
- Refer section "Generation 1 Hitachi Content Platform prerequisites" in User Guide.
Note:
When upgrading, it is highly recommended (and often necessary) to upgrade all nodes to the same version. The recommended order in which to upgraded is:
- Internet Connected Nodes. If ICNs are not upgraded first, they may not be able to be 'push upgraded' through the UI. ICNs may appear to go offline until the master is upgraded.
- Master Node(s).
- Clients acting as ISMs, controlling Hitachi Block and File storage devices.
- Clients acting as Data Destinations, such as Repositories.
- Clients acting as Data Sources, such as application servers.
Note:
- For a new installation, the Master node must be installed before any Client nodes.
- When installing a new Master, you must select the account to use for initial Protector log-on. This account must be a local OS account which is able to successfully log in to the machine. These credentials will be input to the Protector UI to enable the initial access control configuration to be performed.
- Read the release notes shipped with the installer to ensure that the currently installed version can be upgraded to the new version. It may be necessary to upgrade to an intermediate version first and perform additional actions prior to and after upgrading.
- You may need to create an exception in your anti-virus software when installing.
- DO NOT upgrade while replications are in the process of pairing. Any active replications must be in the paired state before upgrade is carried out.
- It is recommend that you perform an upgrade only after currently active backups have been completed.
- Before upgrading, unmount any mounted snapshots and replications.
- It is recommended to backup /protector folder to avoid any issue during OS upgrade.
- If you uninstall a Client node, you will need to delete it from the Nodes Inventory before subsequently reinstalling it. This ensures that the Master node regenerates new identifiers for that node. If you do not do this then the reinstalled Client will not be recognized.
- Operating System Specific Behaviour:
| OS | Note |
|---|---|
| Linux | We recommend that Linux source nodes have a Logical Volume Manager (LVM) on each volume group. |
| Linux and AIX |
Ensure you have execute permissions using the command chmod 755, before running the installer. A minimum of 10 GB of free space is required in the 'unused' portion of the volume that is to be backed up. This is in addition to the space required for the allocated storage area. For example, if 100 GB of usable storage is required, then the total disk size will be 110 GB (100 GB of usable storage and 10 GB of unused storage for snapshot administration). |
| AIX | It is only possible to install the Protector Client on an AIX node. |
All nodes that will participate in a backup data flow need to have Ops Center Protector installed. A node used only to access the web based user interface does not need to have any components installed on it.