<Original posting below> Hi all, and thanks to Darren Dunham and John Riddoch for their responses. Finally, I got a call from SUN, and they explained it. It's really as I supposed, although the Config-Location requires only 5.5 MB Diskspace (You're right, Darren, that's just a small slice), the entire disk cannot be part of a diskgroup. That makes it impossible to use the disk for storing other data in a cluster environment, since every metaset had to be part of diskset. It's even worse, 'cause you even can't use Software-RAID (like SDS or Veritas) to mirror the disk holding the config-location - to do this, it would be necessary that the config-slice is part of a metaset, so, the disk has to be part of a diskset... This makes the config-location a classical single point of failure, and - in my opinion - is not really useful in a HA-environment. SUN suggests using A3310 Storages or similiar, 'cause these have HW-RAID-Controllers. With this, it is possible to configure a small LUN of abt. 10 MB, putting this in a mirrored state with the HW-RAID-Controller, and use it as a config-location. Hm, that's of course right, that's the best solution - but, we already bought the D1000s, so it's more for the future. Thanks to all, have a nice hackin', Harald ============================================ Harald Husemann Systems Engineer Teammanager Unix administration and Configuration Management Materna Gmbh - Vo_kuhle 37 - D-44141 Dortmund, Germany Phone: +49-231-5599-8684 Mobile: +49-179-2300651 -----Urspr|ngliche Nachricht----- Von: Husemann, Harald [mailto:harald.husemann@Materna.DE] Gesendet: Dienstag, 18. Mdrz 2003 11:37 An: Sunmanagers@Sunmanagers. Org Betreff: Question regarding SUN StorEdge Availability Suite Managers, at the moment, we're "playing around" with the SUN StorEdge Availability Suite in a SUN Cluster 3.0 Environment. I've read the documentation, and saw the following: "The configuration location needed for the Availability Suite must be under Device ID (DID) Control only, it cannot be under Volume-Manager control. I. e. it cannot be part of a diskset, and it cannot reside on the boot-device. Also, the disk must not be used as a quorum device." Hmmmm... As far as I understand, I have to configure a volume on a disk as configuration location, and this disk cannot be used to store any data anymore - wasting almost the whole diskspace, since I have to use a 18 GB-HDD, and the config location just needs 5,5 MB... Is this right?! I can't imagine, but it seems that's was the docu tells me. Anyone made experiences with this, and can tell me if I'm right? Thanks, and keep on hackin', Harald ============================================ Harald Husemann Systems Engineer Teammanager Unix administration and Configuration Management Materna Gmbh - Vo_kuhle 37 - D-44141 Dortmund, Germany Phone: +49-231-5599-8684 Mobile: +49-179-2300651 _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Tue Mar 18 11:47:22 2003
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:06 EST