EVS migration within a server farm (HNAS server only)
Server Farm Migration is designed to move EVSs between live HNAS systems in order to allow for growth and to move server load between systems at the EVS level. Both systems must be online and functional. Server Farm Migration not only moves the storage but also the EVS settings from the system registry.
Migration within a server farm is supported under the following conditions:
- When the source EVS is online.
- When both the source and destination servers are online.
- If the EVS does not contain any file systems that are linked into a CNS tree.
- When both the source and destination server have the same major firmware revision.
- There is no more than one EVS in a storage pool. EVS sharing is not supported with Server Farm Migration.
After migrating EVS between servers in a server farm, the assignment of tape drives and tape autochanger devices to EVS must be manually adjusted:
- Tape devices specifically assigned to a migrated EVS will have become unassigned.
- Tape devices assigned to “any EVS” on the source server will remain assigned to “any EVS” on the source server.
Tape devices must not be assigned to EVSs on more than one server.
While EVSs contain most of the settings required to support client storage access, some settings (for example, DNS, which is typically a cluster-wide setting) are functions of the server or cluster, not of the EVS itself. Therefore, when preparing to migrate an EVS from one server or cluster to another, verify in advance that the target server’s settings can properly support the EVS. To prepare a server or cluster to receive a new EVS, source server settings can be cloned.
Cloning server settings
Navigate to , select the target of the migration as the SMU's managed server, and click Clone Server Settings to display the Clone Server Settings page.
From the list, select the server/node currently hosting the EVS, and click next.
Select the settings to clone to the target server/node.
CautionSettings selected for cloning will overwrite the currently defined settings on the target server/node. To keep part of the existing configuration, do not clone the configuration items you want to keep.Click OK to initiate cloning.
After the target server/node has been prepared through server cloning, it is ready to receive the EVS migration.
Migrating an EVS within a server farm
Navigate to .
This page displays only if the currently managed server is a cluster node. Otherwise, clicking EVS Migrate will immediately launch the EVS Migration page.
Click Migrate an EVS from one system to a separate, independent system to display the EVS Migration page.
Click change to select a source server and source EVS.
From the Destination Server menu, select a target server.
Select the Test Only check box to test the migration before committing the change.
The test ensures that the EVS migration is possible.NoteWhen selecting a destination server for an EVS, note that both the source and destination server must be running the same major firmware revision.A message displays indicating if the operation succeeded or failed. If the operation failed, the message includes the reason for the failure.
Click Migrate to start the process.
NoteIf the source server is offline or does not function, migration will be performed using an existing backup and a warning is displayed.