The snapshot job is of type Rolling Snapshot:
- No advanced settings
- VMs to backup
- All statuses
- In our pool
- One tag selected
- 5 VMs total are governed by this job
- Schedule
0 4 * * *- 9 snapshots retention
- Enabled
The user existed well before we started doing scheduled snapshots. I just created a new user, made them a member of our problematic user group and am seeing the same behavior as with original group members: snapshots via schedule are not visible unless I change a user's role to admin.
Just to be on the absolute safe side though I did create a new backup schedule after creating my test user to check if order matters. Same result as before. Only difference in job config was that I chose a VM based on name instead of tag. Cron pattern was 27,28,29,30 18 * * * with 2 snapshots retention to get quick results. Snapshot were then visible for an admin but not for a user in the group that runs our resource pool.
What's also interesting is that the user sees a snapshot count on affected VMs' Snapshots tab, the count being absolutely correct with 9 scheduled snapshots and one manual:
I'm not quite sure where the 10th snapshot came from. It's only visible to admin users. I already verified at the beginning that resource pool users can create their own snapshots perfectly fine and interact with them after creation. Since the 10th snapshot here is not visible I'm guessing it was created by means other than the backup schedule or a user in the resource pool. I created yet another snapshot with my own admin account just now that confirmed the theory: to a resource pool user my admin-created snapshot was counted but not visible.
Just for fun I temporarily increased resource pool limits to see if those were affecting the situation. Looks like they weren't, behavior was unchanged.