Monthy and Weekly markers not appearing on file names

[Brad.Morris]

I think since I have installed patch 2 version 10.0.0.2018 (as supplied by support to fix a issue), it seems that my vbk files from my copy jobs are not getting the suffix of _M or _W applied to the names. Is this by design?

I used to get names like
CPY_FIRE_PRD_FILE_002015-04-27T210000_M.vbk
Now I am getting:
CPY_FIRE_PRD_FILE_002015-05-04T210000.vbk
CPY_FIRE_PRD_FILE_002015-05-11T210000.vbk

Cheers,
Brad.

[foggy]

Brad, could you please check the build version - is it a private hotfix? Then what is the issue it is meant to fix (could you please provdie the case ID)?

[veremin]

As far as I know, the Update 2 has introduced some problems related to the naming of GFS restore points. Those should be fixed in the upcoming Update 2a; so, stay tuned. Thanks.

[Brad.Morris]

As far as I know, the Update 2 has introduced some problems related to the naming of GFS restore points. Those should be fixed in the upcoming Update 2a; so, stay tuned. Thanks.

Any idea when 2a will be released?

[Brad.Morris]

Brad, could you please check the build version - is it a private hotfix? Then what is the issue it is meant to fix (could you please provdie the case ID)?

I am now running the public build of 8.0.0.2021. Seems like there is a bug in this from the other post.

[Lewpy]

I can confirm that I have the same issue with Weekly/Monthly markers not appearing on GFS retention points with Update 2 Build 2018.
I've updated to Update 2a Build 2029 (from Support), so hopefully this will resolve going forward (it hasn't magically fixed the existing files with no markers).

[veremin]

Update 2a is now in limited availability stage and should be released to general public soon. Of course, it won't rename the existing GFS restore points, but will make sure that those appearing afterwards have proper names. Thanks.

[veremin]

The Update 2a is now generally available. Kindly, download it and see whether it solves the issue. Thanks.