Re: BRMS damaged object

[Steve McKay <samckay1@xxxxxxxxx>]

If you're using Flash Copy and seeing a damaged object reported within
BRMS, it may be that the object is damaged on the Flash Copy target system,
not the production system.  Flash Copy transfers the BRMS log and tape
information back to the source system so you can access it as if the backup
ran on the source.

Thanks,

Steve McKay
(205) 585-8424
samckay1@xxxxxxxxx



On Fri, May 21, 2021 at 9:38 AM Steve Pavlichek <spavlichek@xxxxxxxxxxx>
wrote:

> I ran the DSPOBJD before and after the save. BRMS still thinks the file is
> damaged but I can not find any way to verify that.
>
> Herman, VIOS is 2.2.5 and this is a new issue with this file.
> Yes, that VIOS is old but we are migrating the customer to a new POWER9 so
> no need to upgrade it.
>
> From: Rob Berendt<mailto:rob@xxxxxxxxx>
> Sent: Friday, May 21, 2021 8:44 AM
> To: Midrange Systems Technical Discussion<mailto:
> midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: RE: BRMS damaged object
>
> Are you doing the DSPOBJD before, or after, the save?
> Some years back we were having full system saves crash on certain
> Management Central objects.  They were frequently getting damaged.  We
> tried to check prior to the save by DSPOBJD, etc.  However that damaged
> flag is not set until the object is tried to be saved.  We got to the point
> of saving them to a save file prior to the full system save.  If they were
> damaged we would delete them.  Then we would proceed with the full system
> save.  We had to do this for years, through multiple OS upgrades.  IBM
> disavowed this was happening for a long time but they eventually got it
> fixed.
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dekko.com%2F&amp;data=04%7C01%7C%7Ca65b772453c744c989c708d91c5639d4%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637571978924486909%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=8yJFETq2Etu3hdL2W5PhyNckI4ZOzqLu7vXLujY39DI%3D&amp;reserved=0
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com