I mean, it's formally in a whitepaper from 2018,
https://www.ibm.com/support/pages/repair-occupancy-repair-reporting-occupancy-storage-pool

and dsmserv was updated in 2021 to allow this to run on a container pool.
https://www.ibm.com/support/pages/apar/IT15373

It's not normal maintenance, but for a server that's been around a long
time, it should be fine to run it.
Just make sure you're not running expire, replicate, client backups, and
ideally not a DBB at the same time.

With friendly Regards,
Josh-Daniel S. Davis



On Tue, Mar 21, 2023 at 8:01 AM Zoltan Forray <zfor...@vcu.edu> wrote:

> Linux Server 8.1.14.200
>
> Looking for feedback on this "undocumented" (i.e. not in a book but readily
> available via Google search) command.
>
> We have been seeing lots of wacky occupancy numbers, issues with nodes
> reporting something in stgpools that are empty, etc.  I stumbled upon
> REPAIR OCCUPANCY and it has corrected a lot of occupancy reporting issues.
>
> So far running it against 3-nodes has reduced "reporting occupancy" by over
> 10TB.  This is disconcerting since we do billing via occupancy numbers and
> this will make all of the numbers questionable!
>
> My question is, how safe is this command?  Does anyone else run REPAIR
> OCCUPANCY and if so, how frequently?
>
> --
> *Zoltan Forray*
> Enterprise Data Protection Administrator
> VMware Systems Administrator
> Enterprise Compute & Storage Platforms Team
> VCU Infrastructure Services
> zfor...@vcu.edu - 804-828-4807
> <
> https://www.credly.com/badges/131d9645-79f0-49ec-9f29-41f15900dca7/public_url
> >
>

Reply via email to