[gpfsug-discuss] Spectrum Scale mirrored filesets across sites.

Andi Nør Christiansen arc at b4restore.com
Wed Dec 18 12:33:31 GMT 2019


Hi Jack,

Thanks, but we are not looking to implement other products with spectrum scale. We are only searching for a solution to get Spectrum Scale to do the replication for us automatically. 😊


Best Regards

Andi Nør Christiansen
B4Restore A/S

Phone       +45 87 81 37 39
Mobile      +45 23 89 59 75

Fra: gpfsug-discuss-bounces at spectrumscale.org <gpfsug-discuss-bounces at spectrumscale.org> På vegne af Jack Horrocks
Sendt: 18. december 2019 11:10
Til: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Emne: Re: [gpfsug-discuss] Spectrum Scale mirrored filesets across sites.

Hey Andi

I'd be talking to the pixstor boys.

Ngenea will do it for you without having to mess about too much.

https://ww.pixitmedia.com

They are down to earth and won't sell you stuff that doesn't work.

Thanks Jack.

On Wed, 18 Dec 2019 at 21:00, Andi Nør Christiansen <arc at b4restore.com<mailto:arc at b4restore.com>> wrote:
Hi,

We are currently building a 3 site spectrum scale solution where data is going to be generated at two different sites (Site A and Site B, Site C is for archiving/backup) and then archived on site three.
I have however not worked with AFM much so I was wondering if there is someone who knows how to configure AFM to have all data generated in a file-set automatically being copied to an offsite.
GPFS AFM is not an option because of latency between sites so NFS AFM is going to be tunneled between the site via WAN.

As of now we have tried to set up AFM but it only transfers data from home to cache when a prefetch is manually started or a file is being opened, we need all files from home to go to cache as soon as it is generated or at least after a little while.
It does not need to be synchronous it just need to be automatic.

I’m not sure if attachments will be available in this thread but I have attached the concept of our design.

Basically the setup is :

Site A:
Owns “fileset A1” which needs to be replicated to Site B “fileset A2” the from Site B to Site C “fileset A3”.

Site B:
Owns “fileset B1” which needs to be replicated to Site C “fileset B2”.

Site C:
Holds all data from Site A and B “fileset A3 & B2”.

We do not need any sites to have failover functionality only a copy of the data from the two first sites.

If anyone knows how to accomplish this I would be glad to know how!

We have been looking into switching the home and cache site so that data is generated at the cache sites which will trigger GPFS to transfer the files to home as soon as possible but as I have little to no experience with AFM I don’t know what happens to the cache site over time, does the cache site empty itself after a while or does data stay there until manually deleted?

Thanks in advance!

Best Regards<https://www.linkedin.com/company/b4restore-a-s/>

[cid:image001.jpg at 01D5B5A7.BC39FB20]

Andi Nør Christiansen
IT Solution Specialist

Phone       +45 87 81 37 39
Mobile      +45 23 89 59 75
E-mail       arc at b4restore.com<mailto:arc at b4restore.com>
Web          www.b4restore.com<http://www.b4restore.com>
 [B4Restore on LinkedIn] <https://www.linkedin.com/company/b4restore-a-s/>  [B4Restore on Facebook] <https://twitter.com/b4restore>  [B4Restore on Facebook] <https://www.facebook.com/B4Restore>  [Sign up for our newsletter] <https://www.b4restore.com/en/about-us/newsletter>
[Download Report]<https://www.b4restore.com/report>

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org<http://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/20191218/067b09f8/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2875 bytes
Desc: image001.jpg
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191218/067b09f8/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 2102 bytes
Desc: image002.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191218/067b09f8/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 2263 bytes
Desc: image003.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191218/067b09f8/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 2036 bytes
Desc: image004.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191218/067b09f8/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 2198 bytes
Desc: image005.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191218/067b09f8/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 58433 bytes
Desc: image006.png
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191218/067b09f8/attachment-0014.png>


More information about the gpfsug-discuss mailing list