[gpfsug-discuss] NDS in Two Site scenario
Mark.Bush at siriuscom.com
Mark.Bush at siriuscom.com
Thu Jul 21 00:33:06 BST 2016
So in this scenario Ken, can server3 see any disks in site1?
From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Ken Hill <kenh at us.ibm.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Wednesday, July 20, 2016 at 4:15 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] NDS in Two Site scenario
Site1 Site2
Server1 (quorum 1) Server3 (quorum 2)
Server2 Server4
SiteX
Server5 (quorum 3)
You need to set up another site (or server) that is at least power isolated (if not completely infrastructure isolated) from Site1 or Site2. You would then set up a quorum node at that site | location. This insures you can still access your data even if one of your sites go down.
You can further isolate failure by increasing quorum (odd numbers).
The way quorum works is: The majority of the quorum nodes need to be up to survive an outage.
- With 3 quorum nodes you can have 1 quorum node failures and continue filesystem operations.
- With 5 quorum nodes you can have 2 quorum node failures and continue filesystem operations.
- With 7 quorum nodes you can have 3 quorum node failures and continue filesystem operations.
- etc
Please see http://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.0/ibmspectrumscale42_content.html?view=kcfor more information about quorum and tiebreaker disks.
Ken Hill
Technical Sales Specialist | Software Defined Solution Sales
IBM Systems
________________________________
Phone:1-540-207-7270
E-mail: kenh at us.ibm.com<mailto:kenh at us.ibm.com>
[cid:image001.png at 01D1E2B5.280C2EA0]<http://www.ibm.com/us-en/> [cid:image002.png at 01D1E2B5.280C2EA0] <http://www-03.ibm.com/systems/platformcomputing/products/lsf/> [cid:image003.png at 01D1E2B5.280C2EA0] <http://www-03.ibm.com/systems/platformcomputing/products/high-performance-services/index.html> [cid:image004.png at 01D1E2B5.280C2EA0] <http://www-03.ibm.com/systems/platformcomputing/products/symphony/index.html> [cid:image005.png at 01D1E2B5.280C2EA0] <http://www-03.ibm.com/systems/storage/spectrum/> [cid:image006.png at 01D1E2B5.280C2EA0] <http://www-01.ibm.com/software/tivoli/csi/cloud-storage/> [cid:image007.png at 01D1E2B5.280C2EA0] <http://www-01.ibm.com/software/tivoli/csi/backup-recovery/> [cid:image008.png at 01D1E2B5.280C2EA0] <http://www-03.ibm.com/systems/storage/tape/ltfs/index.html> [cid:image009.png at 01D1E2B5.280C2EA0] <http://www-03.ibm.com/systems/storage/spectrum/> [cid:image010.png at 01D1E2B5.280C2EA0] <http://www-03.ibm.com/systems/storage/spectrum/scale/> [cid:image011.png at 01D1E2B5.280C2EA0] <https://www.ibm.com/marketplace/cloud/object-storage/us/en-us>
2300 Dulles Station Blvd
Herndon, VA 20171-6133
United States
From: "Mark.Bush at siriuscom.com" <Mark.Bush at siriuscom.com>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 07/20/2016 04:47 PM
Subject: [gpfsug-discuss] NDS in Two Site scenario
Sent by: gpfsug-discuss-bounces at spectrumscale.org
________________________________
For some reason this concept is a round peg that doesn’t fit the square hole inside my brain. Can someone please explain the best practice to setting up two sites same cluster? I get that I would likely have two NDS nodes in site 1 and two NDS nodes in site two. What I don’t understand are the failure scenarios and what would happen if I lose one or worse a whole site goes down. Do I solve this by having scale replication set to 2 for all my files? I mean a single site I think I get it’s when there are two datacenters and I don’t want two clusters typically.
Mark R. Bush| Solutions Architect
Mobile: 210.237.8415 | mark.bush at siriuscom.com
Sirius Computer Solutions | www.siriuscom.com<http://www.siriuscom.com/>
10100 Reunion Place, Suite 500, San Antonio, TX 78216
This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. This message may be viewed by parties at Sirius Computer Solutions other than those named in the message header. This message does not contain an official representation of Sirius Computer Solutions. If you have received this communication in error, notify Sirius Computer Solutions immediately and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Sirius Computer Solutions<http://www.siriuscom.com/> _______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1621 bytes
Desc: image001.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1597 bytes
Desc: image002.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1072 bytes
Desc: image003.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 979 bytes
Desc: image004.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1564 bytes
Desc: image005.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1313 bytes
Desc: image006.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 1168 bytes
Desc: image007.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 1426 bytes
Desc: image008.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 1369 bytes
Desc: image009.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 1244 bytes
Desc: image010.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 4454 bytes
Desc: image011.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160720/70592878/attachment-0010.png>
More information about the gpfsug-discuss
mailing list