Several features of the santricity LSI disk array Management Software

I. Snapshots

Snapshot volume
The Snapshot volume premium feature creates a logical point-in-time image of another
Volume. snapshot volume is a premium feature of the storage management software and
Must be enabled either by you or your storage vendor. (snapshot will pay for License)
Because the only data blocks that are physically stored in the snapshot repository volume
Are those that have changed since the time the snapshot volume was created, the snapshot
Volume uses less disk space than a full physical copy. (snapshot only needs to be stored from the first
Data changed since snapshot, so the physical capacity used by snapshot is less than that used by full replication)
Typically, you create a snapshot so that an application (for example, a backup application)
Can access the snapshot and read the data, while the base volume remains online and
User-accessible. When the backup is completed, the snapshot volume is no longer needed.
You can also create snapshots of a base volume and write data to the snapshot volumes
Perform testing and analysis. Before upgrading your database management system,
Example, you can use snapshot volumes to test different deployments. Then you can use
The performance data provided by the storage management software to help you decide
How to configure your Live Database System. (typically, you create a snapshot and then an application
-For example, it is a backup process. You can enter this snapshot to read data, and the basic volume is still online and accessible to users. When
After the backup process is complete, the snapshot volume is no longer needed.
You can also create a snapshot of the basic volume and write the data to the snapshot.
Test and analysis.
For example, before upgrading your database management system, you can use snapshot volumes to test different configurations. You can use the snapshot volume to test different configurations. Then you can help you configure your actual database system based on the performance of the storage management software .)
The maximum number of snapshot volumes allowed is one-half of the total volumes
Supported by your controller model, while the maximum number of snapshot volumes
Supported by a volume is four. (The number of snapshots supported by the system is half of the number of snapshots supported by your controller,
The maximum number of snapshots supported by a volume is 4)
Creating snapshot volumes
When a snapshot volume is created, the Controller suspends I/O activity to the base
Volume for a few seconds while it creates a physical volume, called the snapshot
Repository volume, in which to store the snapshot volume metadata and copy-on-write
Data. (when a snapshot volume is created, the Controller stops the I/o Activity of the basic volume for a while,
In this case, it will create a physical volume, which is called a snapshot warehouse volume to store the metadata of the snapshot volume.
And real-time read/write data)
Use the create snapshot volume Wizard to create snapshot volumes by defining the name
Of the snapshot and the name of its associated snapshot repository volume, and to specify
The capacity of the snapshot repository volume as a percentage of the capacity of the base
Volume.
(Create snapshot volume wizard is used to create a snapshot volume. By defining the snapshot name and its corresponding
The Snapshot warehouse volume name to determine, We need to specify the snapshot warehouse volume size, generally according to the size percentage of the basic volume .)
Either the simple path or Advanced path can be selected:
• Simple path-select this path to preview the preconfigured snapshot volume and
Snapshot repository volume parameters.

• Advanced Path-select this path to choose a free capacity or unconfigured capacity
Node on which to place the snapshot repository volume, and to change the snapshot
Repository volume parameters. You can choose the Advanced Path regardless
Whether free capacity or unconfigured capacity is selected.
When the snapshot repository volume nears a user-specified threshold, the storage
Management software provides a "Threshold Exceeded" notification. The threshold defined
Is a percentage of the snapshot repository volume's capacity and, by default, is set
50 percent. When this condition occurs, you can expand the capacity of the snapshot
Repository volume by using free capacity on the volume group. If you are out of free
Capacity on the volume group, you can add unconfigured capacity to the volume group
Expand the snapshot repository volume.

Discontinuing use of a snapshot volume
As long as a snapshot volume is enabled, storage array performance is affected by
Copy-on-Write activity to the associated snapshot repository volume. When you no longer
Need a snapshot volume, you can disable, reuse, or delete it:
• Disable-stops copy-on Write activity. Keeps the snapshot volume and snapshot
Repository volume intact.
• Reuse-creates a different point-in-time image of the same base volume. This action
Takes less time to configure than re-creating the snapshot volume.
• Delete-completely removes the snapshot volume and associated snapshot Repository
Volume. If you want to re-enable a snapshot volume, you must re-create it.

When a snapshot volume is activated, the disk array performance will be affected by the read/write activities of the related snapshot repository volume,
When you no longer need a snapshot volume, you can disable, reuse, or delete it.

Ii. dynamic volume resizing

Dynamic volume expansion (DVE) dynamic volume resizing
Caution increasing the capacity of a standard volume is only supported on
Certain operating systems-if volume capacity is increased on a host
Operating system that is unsupported, the expanded capacity is unusable, and
You cannot restore the original volume capacity. For information on
Supported operating systems, refer to the storage system product release
Notes shipped with the storage management software. (Note that only
Supported on some operating systems. If the volume capacity is expanded on an unsupported operating system
It cannot be used, and you cannot restore to the initial volume capacity .)
Dynamic volume expansion (DVE) is a modification operation that increases the capacity
Of standard or snapshot repository volumes. The increase in capacity can be achieved
Using any free capacity available on the volume group of the standard or snapshot
Repository volume. Data is accessible on volume groups, volumes, and disk drives
Throughout the entire modification operation.
If you receive a warning that the snapshot repository volume is in danger of becoming full,
You can use the DVE modification operation to increase the capacity of the snapshot
Repository volume.
Increasing the capacity of a snapshot repository volume does not increase the capacity
The associated snapshot volume. The capacity of the snapshot volume is always based on
The capacity of the base volume at the time that the snapshot volume is created.

3. remote disk array Mirroring

Remote Volume indexing ing
The Remote Volume processing ing feature is used for online, real-time replication of data
Between storage arrays over a remote distance. This is a premium feature of the storage
Management Software and must be enabled either by you or your storage vendor.

You must enable and activate the Remote Volume indexing ing premium feature on both
Primary and secondary storage arrays to create a mirror relationship.
(The Remote Volume image function is used for online and real-time volume replication between distant disk arrays. This function is required.
Additional charges, and you must purchase this feature on both the primary and secondary disk arrays for Remote Volume images .)

Primary and secondary volumes
When you create a Remote Volume mirror, a mirrored-volume pair is set up and consists
A primary volume at a primary storage array and a secondary volume at a secondary
Storage array. A standard volume may only be supported ded in One mirrored-volume pair.
There can be up to 32 defined mirrors on an e2600 array module and up to 64 defined
Mirrors on an e4600 or e5600 command module.
The primary volume is the volume that accepts I/O activity from the host and stores
Application Data. The secondary volume maintains a mirror (or copy) of the data from its
Associated primary volume. The controller owner of the secondary volume specified es
Remote writes from the owner of the primary volume controller but does not accept host
Write requests. hosts are able to read from the secondary volume, which appears
Read-only.
(The primary array volume is an I/O read/write volume that receives server and application data. Secondary array volumes are Storage
Volume of mirror data of the primary array volume) the controller of the secondary array volume only accepts write commands of the primary array controller,
Do not accept write commands from the server. The server can read information from the secondary array volume, but only read-only.