[gpfsug-discuss] Pool migration and replicate
Marc A Kaplan
makaplan at us.ibm.com
Thu Apr 26 21:30:14 BST 2018
No need to specify REPLICATE(1), but no harm either.
No need to specify a FROM POOL, unless you want to restrict the set of
files considered. (consider a system with more than two pools...)
If a file is already in the target (TO) POOL, then no harm, we just skip
over that file.
From: "Simon Thompson (IT Research Support)" <S.J.Thompson at bham.ac.uk>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 04/26/2018 02:09 PM
Subject: [gpfsug-discuss] Pool migration and replicate
Sent by: gpfsug-discuss-bounces at spectrumscale.org
Hi all,
We'd like to move some data from a non replicated pool to another pool,
but keep replication at 1 (the fs default is 2).
When using an ILM policy, is the default to keep the current replication
or use the fs default?
I.e.just wondering if I need to include a "REPLICATE(1)" clause.
Also if the data is already migrated to the pool, is it still considered
by the policy engine, or should I include FROM POOL...?
I.e. just wondering what is the most efficient way to target the files.
Thanks
Simon
_______________________________________________
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=cvpnBBH0j41aQy0RPiG2xRL_M8mTc1izuQD3_PmtjZ8&m=9Ko588DKk_71GheOwRqmDO1vVI24OTUvUBdYv8YHIbU&s=04zxf_-EsPu_LN--gsPx7GEPRsqUW7jIZ1Biov8R3mY&e=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180426/40851292/attachment-0002.htm>
More information about the gpfsug-discuss
mailing list