meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 7 months |
| seen | May 14 at 18:21 | |
| stats | profile views | 186 |
UNIX noob, enterprise storage expert
|
May 7 |
awarded | san |
|
May 7 |
awarded | Popular Question |
|
May 4 |
comment |
High speed storage drive (over 8 GByte/s) Can we assume that the bandwidth between the storage server and the workstations/renderfarm isn't going to be your bottleneck? |
|
May 4 |
comment |
High speed storage drive (over 8 GByte/s) You make it sound like it's trivially easy, but you clearly haven't done it. |
|
May 4 |
comment |
Solaris not seeing FC volume I'm a little unclear about the architecture- what type of controller is it? Local raid card in the server, or standalone shared storage? |
|
May 2 |
awarded | Notable Question |
|
Apr 16 |
comment |
Server 2012: how to plan for storage failover? Synchronous replication costs an arm and a leg on the storage- especially since this will be for one type of server only (Hyper-V), it makes sense to use the hypervisor to provide failover and clustering. |
|
Apr 3 |
awarded | Popular Question |
|
Apr 1 |
comment |
What are the tradeoffs between using hypervisor- vs. storage-array-based snapshots as backup sources? The full copy wouldn't be, but the snapshot integration would allow a VM snapshot to be created using storage snap technology, which is typically a lot more advanced and efficient. |
|
Apr 1 |
comment |
HP P4000 / Lefthand : how to do a manual failover I'd characterize that as "well written firmware". And mirrored cache prevents data corruption upon the failure of one controller, but if you're being picky about terminology, that isn't strictly a quorum issue. |
|
Apr 1 |
answered | What are the tradeoffs between using hypervisor- vs. storage-array-based snapshots as backup sources? |
|
Mar 28 |
comment |
HP P4000 / Lefthand : how to do a manual failover A simple two-head SAN controller doesn't use a quorum disk, it uses well written firmware and cache mirroring to ensure write consistence. When they go offsite, they have to use replication rather than failover, but the P4000 should be able to handle a basic one-site storage environment without all the extra hassle of FOM. |
|
Mar 27 |
comment |
HP P4000 / Lefthand : how to do a manual failover I meant in the sense of not baking "lack of data corruption, no matter what" into the storage. Uncoordinated writes to the same disks is a problem that every other storage controller on the market has solved without requiring the use of software running on a server somewhere. |
|
Mar 27 |
comment |
HP P4000 / Lefthand : how to do a manual failover Haha, a "feature". That's cute. |
|
Mar 27 |
revised |
HP P4000 / Lefthand : how to do a manual failover edited tags |
|
Mar 27 |
answered | HP P4000 / Lefthand : how to do a manual failover |
|
Mar 11 |
revised |
How to Shrink a Volume on Equallogic SAN edited tags |
|
Mar 5 |
revised |
Troubleshooting MySQL Performance Issues clarification |
|
Mar 5 |
answered | Troubleshooting MySQL Performance Issues |
|
Mar 5 |
answered | How to share Fibre Channel between servers on Windows 2012 STD |
