Hallo Simon
replication attributes of a file won't be changed just by the fact , that the pool attribute is changed..
or in other words .. if a file gets migrated from POOLA to POOLB, does not change the replication automatically... even if the pool consists of NSDs with multiple fg
so depending on what you want to achieve.. you need to additionally specify REPLICATE clause or not..
if you want to keep your replication attribute.. it should work without specifying REPLICATE ...
as you said.. this statement is true for "move"...
a initial placement of a file would still follow the default of the fs
cheers
From: "Simon Thompson (IT Research Support)" <[email protected]>
To: gpfsug main discussion list <[email protected]>
Date: 04/26/2018 11:09 AM
Subject: [gpfsug-discuss] Pool migration and replicate
Sent by: [email protected]
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
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
replication attributes of a file won't be changed just by the fact , that the pool attribute is changed..
or in other words .. if a file gets migrated from POOLA to POOLB, does not change the replication automatically... even if the pool consists of NSDs with multiple fg
so depending on what you want to achieve.. you need to additionally specify REPLICATE clause or not..
if you want to keep your replication attribute.. it should work without specifying REPLICATE ...
as you said.. this statement is true for "move"...
a initial placement of a file would still follow the default of the fs
cheers
From: "Simon Thompson (IT Research Support)" <[email protected]>
To: gpfsug main discussion list <[email protected]>
Date: 04/26/2018 11:09 AM
Subject: [gpfsug-discuss] Pool migration and replicate
Sent by: [email protected]
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
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
