Notes about Traveller
Traveller configuration and operations are documented in the Traveller Help included with the Traveller product. A few notes regarding the use of Traveller-enabled virtual volumes and Traveller rollback virtual volumes in SANmanager are listed below:
-
Traveller-enabled virtual volumes (which are used as the basis of Traveller rollbacks) are created in SANmanager. In SANmanager, these virtual volumes are displayed as “Mirror w/Traveller” in the Virtual Volume Type column.
-
After the first Traveller rollback virtual volume is created, a volume is selected and a Traveller Mapstore is automatically created on the Traveller server. The Traveller Mapstore is identified in Virtual Volume tab, in the upper-right pane under the Virtual Volume column. Do not delete the Mapstore if you have rollbacks.
-
After Traveller rollback virtual volumes are created on the Traveller server and the configuration is applied, these rollbacks are automatically seen by SANmanager and identified as linear virtual volumes belonging to the Traveller server.
These linear virtual volumes are logical copies and should not be mirrored without performing a Full Copy and Split command on the Traveller server. Refer to Traveller Help for details on selecting a restoration method to ensure proper usage.
-
SANmanager does not permit a rollback virtual volume to be renamed.
-
SANmanager will manage (mirror, map, etc.) the rollback virtual volumes as any other virtual volume with a few exceptions. A Traveller rollback cannot be deleted in SANmanager, including removing or replacing the primary volume in the Traveller rollback virtual volume. Deleting the Traveller rollback can only be done on the Traveller server.
-
The Traveller volume in a Traveller-enabled virtual volume cannot be replaced; they can only be deleted and recreated.
-
Traveller-enabled virtual volumes cannot be split in SANmanager.
-
Traveller does not support virtual volumes with a logical size of greater than 2 TB.