[gpfsug-discuss] AFM cache re-link

[Venkateswara R Puvvada]

What is the fileset mode ? AFM won't attempt to copy the data back to home 
if file data already exists (checks if file size, mtime with nano seconds 
granularity  and number of data blocks allocated are same). For example 
rsync version >= 3.1.0 keeps file mtime in sync with nano seconds 
granularity. Copy the data  from old home to new home and run failover 
command  from cache to avoid resynching the entire data.

~Venkat (vpuvvada at in.ibm.com)



From:   Nick Savva <nick.savva at adventone.com>
To:     "'gpfsug-discuss at spectrumscale.org'" 
<gpfsug-discuss at spectrumscale.org>
Date:   04/22/2018 05:48 PM
Subject:        [gpfsug-discuss] AFM cache re-link
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



Hi all,
 
I was always preface my questions with an apology first up if this has 
been covered before.
 
I am curious if anyone has tested relinking an AFM cache to a new home 
where the new home, old home and cache have the exact same data. What is 
the behaviour? 
 
The infocenter and documentation say the cache expects home to be empty. I 
did a small test and it seems to work but it may have happened too fast 
for me to notice any data movement. 
 
If anyone is interested in the use case, I am attempting to avoid pulling 
data from production over the link. The idea is to sync the data locally 
in DR to the cache, and then relink the cache to production. Where prod/dr 
are gpfs filesystems with a replica set of data. Again its to avoid moving 
TB’s across the link that are already there.
 
 
Appreciate the help in advance,
 
Nick
 
 
 
 
 
 _______________________________________________
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=92LOlNh2yLzrrGTDA7HnfF8LFr55zGxghLZtvZcZD7A&m=nXbwwQdO-Ul1CumnSmAKP5UCePJCaBVsley8z-eLJgw&s=Rho3eJsFXeOseZuGqDzP33yLYKUUpyIA1DUGGtmx_LU&e=





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180423/fd3d494f/attachment-0002.htm>