If your restore software uses the gpfs_fputattrs() or
gpfs_fputattrswithpathname methods, notice there are some options to
control the pool.
AND there is also the possibility of using the little known "RESTORE"
policy rule to algorithmically control the pool selection by different
criteria
Hi Uwe,
Thanks for your response.
So our restore software lays down the metadata first, then the data. While it
has no specific knowledge of the extended attributes, it does back them up and
restore them. So the only explanation that makes sense to me is that since the
inode for the file
> However, I took a look in one of the restore directories under
> /gpfs23/ RESTORE using mmlsattr and I see files in all 3 pools!
> So ? I don?t think GPFS is doing this but the next thing I am
> going to do is follow up with our tape software vendor ? I bet
> they preserve the pool
Hi again all,
I received a direct response and am not sure whether that means the sender did
not want to be identified, but they asked good questions that I wanted to
answer on list…
No, we do not use snapshots on this filesystem.
No, we’re not using HSM … our tape backup system is a
I think the restore is is bringing back a lot of material with atime >
90, so it is passing-trough gpfs23data and going directly to
gpfs23capacity.
I also think you may not have stopped the crontab script as you
believe you did.
Jaime
Quoting "Buterbaugh, Kevin L" :
Hi All,
First
Hi All,
So in trying to prove Jaime wrong I proved him half right … the cron job is
stopped:
#13 22 * * 5 /root/bin/gpfs_migration.sh
However, I took a look in one of the restore directories under /gpfs23/ RESTORE
using mmlsattr and I see files in all 3 pools! So that explains why the
> On Jun 7, 2018, at 10:16 AM, Buterbaugh, Kevin L
> wrote:
>
> Hi All,
>
> First off, I’m on day 8 of dealing with two different mini-catastrophes at
> work and am therefore very sleep deprived and possibly missing something
> obvious … with that disclaimer out of the way…
>
> We have a
Hi All,
First off, I’m on day 8 of dealing with two different mini-catastrophes at work
and am therefore very sleep deprived and possibly missing something obvious …
with that disclaimer out of the way…
We have a filesystem with 3 pools: 1) system (metadata only), 2) gpfs23data
(the default