Getting Started with AIM
This topic provides a step-by-step guide through a basic configuration of AIM. After performing the steps below, you will be ready to replicate data from a source server to a remote (destination) server. However, be sure to review all topics in the AIM chapter for a complete understanding of the feature.
The AIM GUIs, where configuration and monitoring are performed, are AIM Source Manager and AIM Destination Manager. The configuration of AIM relationships are performed in the SANmanager AIM tab.
Before you begin:
-
Refer to About AIM for an overview of how the product works and other important information.
-
Ensure that you have reviewed these important topics for information: AIM Pre-Installation Notes and all topics in the Planning an AIM Configuration section in the AIM Chapter.
-
The AIM software option should be installed on all source and destination servers. During installation, you should have provided the location of the buffers and the assignment as source, destination, or both. Refer to AIM Buffers for important information.
-
The administrator may want to set up a dedicated user account for AIM. A new account must have Administrator Privilege (with password) and Log On as Service Privilege set in order to use AIM. AIM services on both AIM source and destination servers must use the same logon account and password.
-
During SANsymphony installation, default AIM source and destination buffers (shared as AimBuffer) are automatically created in the location of the SANsymphony files (default location is C:Program Files (x86)DataCore SoftwareSANsymphonyAIM). These AIM buffers on the boot drive cannot be used. You must recreate new AIM buffers on local drives and move the AIM buffers to the new location. Refer to AIM Buffers to create new buffers that meet your particular needs, then refer to Changing Source Buffer Settings and Changing Destination Buffer Settings for instructions.
WARNING: Do not use the AIM buffers that were created on the C: during installation.
Follow the steps below, in order, to perform a basic configuration of AIM. Be sure to refer to the associated configuration topics for additional instructions.
Step |
Process |
Topics |
1 |
Use SANmanager to create virtual volumes (as needed) and assign the virtual volumes to be used as either source or destination candidates for AIM sets. | |
2 |
Use SANmanager to create AIM groups (This is an optional step for the AIM source if the AIM set will be part of a designated group.) | |
3 |
If you already have your source virtual volumes mapped to application servers and in use, skip this step; otherwise, map the source virtual volumes to application servers for use, as appropriate. The data written to mapped virtual volumes is the source of your AIM transfer. |
If necessary, refer to Mapping Virtual Volumes to Application Servers. |
4 |
Select and set up your data transfer mode. | |
5 |
Use AIM Source Manager to configure the destination server and assign the data transfer mode. | |
6 |
Use AIM Source Manager to create the AIM sets, during which specific destination volumes are assigned to specific source volumes. | |
7 |
Use the AIM Source Manager to synchronize the data on source and destination virtual volumes. | |
8 |
Use the AIM Source Manager to set up services and commands. |