Volumes Documentation (Hide Help)Knowledgebase object #1007
Before any Groups or Machines can be added to the network, volumes must be made here. If a Jentu representative has imported existing images into the server, you can use the 'already exists' option to preclude running a create command on the server.
Jentu uses thin provisioning on its storage, and allows creating volumes which are larger than the entire server's storage allows for, but this is not a recommended mode of operation. Jentu best practices dictate that small volumes are safer volumes.
The 'alias' field allows administrators to assign a human-readable nickname for volumes, which will be displayed in place of its ServerID in areas where the volume is referenced (Groups page and Add Group dialogue)
High Availability in Jentu v1.2, all volumes and groups are sent to every slave when replication occurs, so care should be taken with respect to determining how much storage to provision, as very large volumes will take longer to replicate. In the event that a group inflates past reasonable replication amounta, the experimental Group Optimization procedure allows the reorganization of server filesystem, reducing the group to 8 Kilobytes and increasing the size of the volume.
As of Jentu v2.0, replication upgrades bring new logic that does away with the old method of brute force destroy and repopulate. Instead of deleting all objects from the secondary node, they are compared and transferred when they are different, or do not exist in the destination.Advanced
High Availability has many features including thin replication, slave node promotion, replication checksums and more. Contact a Jentu representative and ask if Advanced
High Availability is available for your network.