Stimmen - 0, Durchschnittliche Bewertung: 0
(
)
)
|
Anleitung Zusammenfassung
Secure Path version
VCS 3.110 requires the latest version of Secure Path for your operating system. The current version of
Secure Path for your operating system can be found at the following website:
ht p://h18006.www1.hp.com/products/sanworks/secure-path/index.html
Codeload usage
When a maximally configured system is running at maximum load, Secure Path timing constraints make
codeload functionality ineffective. The system may time-out before codeload is complete. Therefore, you
should perform VCS upgrades at an off-peak time.
SSSU
Changing comments on a disk enclosure
Use Command View EVA to change comments on a disk enclosure. If you try to change a disk enclosure
comment using SSSU, the following error message appears:
Error:
Invalid Operation
Changing the name of a disk enclosure
Changing the name of a disk enclosure is not supported with SSSU or with Command View EVA. If you
try to change a disk enclosure name using SSSU, the following error message appears:
Error:
Invalid Operation
Logical Volume Manager
When creating snapshots or clones of a device that is managed by Logical Volume Manager (LVM),
take care to properly configure LVM. After creating a snapshot or clone of a physical volume, always
run vgchgid(1M) to break the association between the volume group and the snapshot or clone.
Otherwise, snapshots or clones appear to LVM as an alternate path to the original physical volume.
This could lead to data corruption if the snapshot or clone is later added to the volume group using
vgextent(1M), vgimport(1M), or vgscan(1M).
When a path to a device managed by LVM becomes unavailable because of a controller, path link,
switch, or HBA failure, I/O requests can be delayed for up to one minute after the failure. As a result,
the responsiveness of mirrored logical volumes may be affected briefly. When a physical volume
becomes unavailable, applications may experience a delay while an I/O request to that physical volume
times out. By default, this delay takes 30 seconds, but you can change the time-out value using the
pvchange(1M) command.
For a read, LVM selects another mirror and requests I/O again. For a write, LVM records the error, and
continues if the data has been written to at least one mirror. In either case, with Secure Path installed, this
initial time-out may take up to one minute longer. After initial time-out, LVM stores the physical volume
status as unavailable, and henceforth, I/O requests do not suffer this delay.
Overloaded EVA configurations
Under conditions where multiple servers are overloading an EVA, the boot or reboot of one of the servers
may time-out. If the combined delayed access to EVA LUNs takes more than 10 minutes, the boot does
not complete. To avoid this situation, restart the boot process and reduce the load to the EVA.
8
...Dieses Handbuch ist für folgende Modelle:
Media Storage - HP StorageWorks EVA3000 EMEA Bundles (133.65 kb)