Points missing in Restore portal

[lmendel]

Hi,

Last year we migrated all M365 tenant data from local JET repos to Wasabi S3, all went pretty smoothly and all works mostly fine since. Unfortunately for some customers we are experiencing issue where all their restore points are accessible through GUI and API (confirmed by support twice) but Restore portal only shows restore points going back only few months, back to the point were JET repos were moved to S3. Issue was occurring on V7.1 and is still occurring on a new server on 8.1. We went through number of troubleshooting steps Veeam updates/repo re indexing's - no change.

Ticket has been opened with support since 07/10/2024 - case 07452390, but there has been no progress are lack of any useful support since December. I've escalated with our account manager twice since - nothing changed.

Can someone have a look please?

[Polina]

Hi Lukasz,

Support engineers will contact you soon, please continue working with them. If needed, your case will be escalated to RnD.

Thanks!

[DaStivi]

i just double checked in my environment and i've exact the same issue after moving Jet 2 S3 ... in restore Portal only the Restore Points after the move are displayed but not before...

[Polina]

Weird.

Stephan, please report this to our support team and share your case ID with me.

Thanks!

[MaartenA]

You probably created new jobs during the migration? If so, the older restore points are only visible at the organization level and not at the job level. If I'm correct, you can only see restore points at the job level via the restore portal and not on the organization level so the old ones are not visable.

[lmendel]

Of course new job was created, this is a required step when moving to object storage. I'm aware of point visibility at the job and org level - at org lever all points are available just fine in GUI and through API as I mentioned in 1st post. According to support, points available in Restore portal should be the same as available at org level in GUI. We have moved JET jobs/repos number of times in the past and never had the issue. If I recall correctly not all customers moved to S3 are affected.

[DaStivi]

NO, its not needed to create new jobs! in fact the PS1 Script thats available, disables the job, moves the data and then re-enables it. and it also runs a "fully sync" after migration of data! so its not needed to create a new job...
AND with the restore portal i don't choose on organization nor job level... via. the restore operators i've just set my admin can restore for the whole organziation!

[DaStivi]

i've double checked it now... and even i didn't have recreated the job (only changed the repo in the existing job) when using the explorers via the job, it doesn't display older restore points, as the restore portal, but gooing over the org-level the explorers does display the old restore points... so it doesn't matter if job has been recreated... but it looks like the restore portal "does not use" the org level to browse restore points, simply put...

[DaStivi]

Stephan, please report this to our support team and share your case ID with me.

Case #07633931

[lmendel]

Of course new job was created, this is a required step when moving to object storage. I'm aware of point visibility at the job and org level - at org lever all points are available just fine in GUI and through API as I mentioned in 1st post. According to support, points available in Restore portal should be the same as available at org level in GUI. We have moved JET jobs/repos number of times in the past and never had the issue. If I recall correctly not all customers moved to S3 are affected.

Apologies, the above is wrong. New job wasn't created, I was thinking about move between servers. However the issue still stands.