HP P4000 9.0 HP StorageWorks P4000 Windows Solution Pack User Manual - Page 42

HP StorageWorks P4000 Windows Solution Pack

Page 42 highlights

In particular, if a reconfiguration was done by accident, you don't have to wait until it finishes to change back to the original configuration. See "Stripe". resync When a storage system goes down, and writes continue to a second storage system, and the original store comes back up, the original storage system needs to recoup the exact data captured by the second storage system. rolling back Replaces the original volume with a read/write copy of a selected snapshot. Starting with release 8.0, he new volume retains the same name. SAN/iQ interface When you initially set up a storage system using the Configuration Interface, the first interface that you configure becomes the interface used for the SAN/iQ software communication. secondary site A site that is less important than the primary site. In this setup a minority of managers runs in the secondary site. In a two-site setup, this allows the secondary site to go offline if the network link between the Primary and secondary sites fails. Typically, the secondary site has a minority, or none, of the application servers. If the primary site fails, customers can manually recover quorum in the secondary site. server An application server that you set up in a management group and then assign volumes to it to provide access to those volumes. shared snapshot Shared snapshots occur when a clone point is created from a newer snapshot that has older snapshots below it in the tree. All the volumes created from the clone point will display these older snapshots that they share, as well as the clone point. site A user-designated location in which storage systems are installed. Multi-Site SAN configurations have multiple sites with storage systems in each site, and each site has its own subnet. A site can be a logical configuration, such as a subnet within the same data center, department, or application. SmartClone volume SmartClone volumes are space-efficient copies of existing volumes or snapshots. They appear as multiple volumes that share a common snapshot, called a clone point. They share this snapshot data on the SAN. snapshot A fixed version of a volume for use with backup and other applications. snapshot set Application-managed snapshots created for a volume set. SNMP traps Use traps to have an SNMP tool send alerts when a monitoring threshold is reached. solution pack HP StorageWorks P4000 Windows Solution Pack split mirror A split mirror is a remote snapshot whose relationship to the primary volume has been severed. Split mirrors are usually created for one-time use and then discarded. standard cluster Also known as a "cluster." A standard cluster is one that does not use any of the Multi-Site features within the SAN/iQ software. Standard clusters: • Cannot contain storage systems that are designated to reside in a site. • Cannot contain storage systems that span subnets. • Can only have a single VIP. 42 Glossary

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48

In particular, if a reconfiguration was done by accident, you don't have to wait
until it finishes to change back to the original configuration. See
Stripe
.
resync
When a storage system goes down, and writes continue to a second storage
system, and the original store comes back up, the original storage system needs
to recoup the exact data captured by the second storage system.
rolling back
Replaces the original volume with a read/write copy of a selected snapshot.
Starting with release 8.0, he new volume retains the same name.
SAN/iQ interface
When you initially set up a storage system using the Configuration Interface, the
first interface that you configure becomes the interface used for the SAN/iQ
software communication.
secondary site
A site that is less important than the primary site. In this setup a minority of
managers runs in the secondary site. In a two-site setup, this allows the secondary
site to go offline if the network link between the Primary and secondary sites
fails. Typically, the secondary site has a minority, or none, of the application
servers. If the primary site fails, customers can manually recover quorum in the
secondary site.
server
An application server that you set up in a management group and then assign
volumes to it to provide access to those volumes.
shared snapshot
Shared snapshots occur when a clone point is created from a newer snapshot
that has older snapshots below it in the tree. All the volumes created from the
clone point will display these older snapshots that they share, as well as the clone
point.
site
A user-designated location in which storage systems are installed. Multi-Site SAN
configurations have multiple sites with storage systems in each site, and each
site has its own subnet. A site can be a logical configuration, such as a subnet
within the same data center, department, or application.
SmartClone
volume
SmartClone volumes are space-efficient copies of existing volumes or snapshots.
They appear as multiple volumes that share a common snapshot, called a clone
point. They share this snapshot data on the SAN.
snapshot
A fixed version of a volume for use with backup and other applications.
snapshot set
Application-managed snapshots created for a volume set.
SNMP traps
Use traps to have an SNMP tool send alerts when a monitoring threshold is
reached.
solution pack
HP StorageWorks P4000 Windows Solution Pack
split mirror
A split mirror is a remote snapshot whose relationship to the primary volume has
been severed. Split mirrors are usually created for one-time use and then
discarded.
standard cluster
Also known as a
cluster.
A standard cluster is one that does not use any of the
Multi-Site features within the SAN/iQ software. Standard clusters:
Cannot contain storage systems that are designated to reside in a site.
Cannot contain storage systems that span subnets.
Can only have a single VIP.
Glossary
42