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

[Venkateswara R Puvvada]

>Site A:
>Owns “fileset A1” which needs to be replicated to Site B “fileset A2” the 
from Site B to Site C “fileset A3”.
 
a. Is this required because A cannot directly talk to C ?
b. Is this network restriction ? 
c. Where is the data generated ? At filesetA1 or filesetA2 or filesetA3 or 
all the places ? 

>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”.
 
Same as above, where is the data generated ?

 
>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?
 
AFM single writer mode or independent-writer mode can be used to replicate 
the data from the cache to home automatically. 

a. Approximately how many files/data can each cache(filesetA1, filesetA2 
and fileesetB1) hold ?
b. After the archival at the site C, will the data get deleted from the 
filesets  at C?

~Venkat (vpuvvada at in.ibm.com)



From:   Lyle Gayne/Poughkeepsie/IBM
To:     gpfsug-discuss at spectrumscale.org, Venkateswara R 
Puvvada/India/IBM at IBMIN
Date:   12/18/2019 08:03 PM
Subject:        Re: [EXTERNAL] [gpfsug-discuss] Spectrum Scale mirrored 
filesets across sites.



Adding Venkat so he can chime in.
 
Lyle
 
----- Original message -----
From: "Andi Nør Christiansen" <arc at b4restore.com>
Sent by: gpfsug-discuss-bounces at spectrumscale.org
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Cc:
Subject: [EXTERNAL] [gpfsug-discuss] Spectrum Scale mirrored filesets 
across sites.
Date: Wed, Dec 18, 2019 5:24 AM
 
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



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
Web          www.b4restore.com
    

 
 
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=IbxtjdkPAM2Sbon4Lbbi4w&m=eqWwibkj7RzAd4hcjuMXLC8a3bAQwHQNAlIm-a5WEOo&s=dWoFLlPqh2RDoLkJVIY0tM-wTVCtrhCqT0oZL4UkmZ8&e= 

 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191219/2f3c2dc8/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2875 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191219/2f3c2dc8/attachment-0002.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2102 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191219/2f3c2dc8/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2263 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191219/2f3c2dc8/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2036 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191219/2f3c2dc8/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2198 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191219/2f3c2dc8/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 58433 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20191219/2f3c2dc8/attachment-0014.png>