Una primera aproximación al cálculo del error del método

Role Solutions Architect / Implementation Specialist

Description Execute the Swingframe migration itself with Open Migrator LM.

Task List  Perform Execution of Open Migrator LM Swingframe Migration, Testing, and Cutover

Perform

In this step, you physically and/or logically migrate assets from the current to the planned environment. After you complete the migration, you perform the tests documented in the Test Plan which is included in this TS Service Kit.

OM/LM for Windows Implementation Tips

The following list provides implementation tips for an OM/LM for Windows migration:

 OM/LM requires a system reboot to install and de-install the filter driver. Plan this to coincide with other system reboot activity if possible (for example, HBA, PowerPath, installations, and so on).

 The filter driver must be attached to each volume before migration. Depending on the state of the volume, OM/LM may require a reboot. If a reboot is necessary, OM/LM informs the user through a dialog box.

 EMC Engineering strongly recommends that you perform a reboot after attaching the filter to all source and target volumes before you start the migration.

 If the customer wants to abort the migration while it in progress, there is a cancel option for OM/LM that will stop the migration.

Note: You must format the destination volume before you reboot the system! If you do not format the destination volume, Windows will have to verify the entire volume during system initialization. This might take several hours, depending on the number of files and size of the volume.

 In the event that a volume has already been migrated and the customer wants to fall back to the original configuration after system reboot — applications must be halted.

Using Disk Manager, you can change the drive letter of the migrated volume to a temporary drive letter. Then you can re-assign the original disk volume to its original drive letter assignment.

 Do not use Terminal Server sessions to operate the OM/LM Microsoft Management Console (MMC).

 You must “Rescan disks and volumes” for disk changes any time you launch OM/LM MMC. This will ensure that OM/LM for Windows has the correct drive information. If you close out of the OM/LM MMC while a migration is going and later open the OM/LM MMC you must do a “Rescan disks and volumes” in order to get the correct migration percentages.

 When performing a migration with OM/LM for Windows on a newly created volume you will still receive a dialog box informing you that the destination is not empty. You must ensure that you have selected the correct destination volume. You will receive this error since there are hidden files that are created when formatting a volume in

Windows.

 It is important to hide columns in the OM/LM MMC before you run Parallel migrations. This improves performance.

OM/LM for UNIX/Linux Implementation Tips

The following list provides implementation tips for an OM/LM for UNIX migration:

 Use sessions to group together devices that logically go together (like databases and logs).

 If large amounts of devices must be migrated, consider dividing them up into sessions and running them serially (see more information on this in the “Planning and Design:

Best Practices” section of this document).

 Use the standard location/commands to find and view necessary logs on a UNIX host:

 OM/LM Logs: /var/EMCom/log

 System Logs: Sun: /var/adm/messages

 System Logs: HP: /var/adm/syslog/syslog.log

 System Logs: AIX: ^{errpt –a}

 System Logs: Linux /var/log

 The CLI operands -pause and -resume can be put in a cron job to pause a copy job during busy times and resume them during slow times (such as overnight).

 The CLI operand ^–tune is used to change the ceiling rate, which can be done prior to migrations or dynamically (during them).

 The CLI operand –restart should be used only after an error.

Note: After a reboot, OM/LM automatically runs and restarts any existing (unfinished) copy jobs.

 You must deactivate sessions before uninstalling the product.

 If you upgrade a Sun box from 32-bit to 64-bit, the bit is set at installation so you must do the following:

 Remove OM/LM first

 Migrate OS (32->64)

 Delete leftover files under /etc/opt/EMCom/properties

 Reinstall OM/LM after upgrade

Table 14 provides example CLI commands. Refer to the Open Migrator/LM CLI Product Guide for more details and more commands.

Table 14. Example CLI Commands Example CLI Command Information

stormigrate activate –session

<session_name>

Activates the session.

stormigrate copy –session

<session_name>

Starts copying of the session.

stormigrate create –session

<session_name> –file <filename>

Creates the session, using a file that lists all source and target devices pairs.

stormigrate query –session

<session_name> -i 30

Monitoring command, running at 30 second intervals.

Example CLI Command Information

stormigrate tune –ceiling N Throttle maximum bandwidth used by OM/LM

N = MBs/second of sessions (default is 1)

Monitor data rate of sessions.

stormigrate query –session omtest –i 30

symstat, iostat, sar, etc. as well

stormigrate tune –iosize N Used to change the transfer size used by OM/LM.

N = I/O transfer size in KBs (default is 64)

stormigrate verify –session

<session_name> –i 30

Returns when copying is completed.

Execute Migration Cutover, Testing, and Cleanup (User-determined