VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Locally, the snaps are removed off the storage on the node Nutanix created. The issue lies with synchronous replication and the fact that these snaps are being replicated to a second node. Nutanix creates the snap, replication copies the snap to the second node. Nutanix deletes the snap off the first but not the second and there’s no expiration date so they have to be removed manually. With hundreds of servers bouncing due to replication, its too much to keep on top of it.Possible options - If possible, move the snaps to someplace that isn’t replicated (per Nutanix, impossible to more the default location). Have the replicated snaps set with a expiration data - again Nutanix said can’t be done.I’m scratching my head that we can’t be the only ones running in such a setup. We’ve found that Hycu does the same thing in testing. jd
During the Proxy upgrade, part of the procedure is to set the permissions that are to be used. The correct ones are selected, the installer can actually make connection and pull up the list of datastores so comm is good with those creds. It’s when the procedure is actually trying to update the Proxy is where it fails, Invalid Credentials. Checking the proxy server itself, the logs show invalid login with the ID of ROOT being used.
If you have a Enterprise licensed product, you can contact your person at Veeam and they should be able to get a local tech in your part of the world to go over things with you.
Like Amore514 said, check out Wasabi for immutable storage.. or just replace the older synology with a DS220+
I’m running v12 and I didn’t have to reboot any servers. VBR does shut down and restart but the hosting server doesn’t have to.
I ran into the same issue.. had the same result. The chain gets corrupted and causes that error. If you haven’t done so, in the job / storage / advanced settings, make sure to enable Storage-level corruption guard. It will scan the storage and fix minor things that could turn into major things. It won’t fix one that’s already gone bad though.
Just to clarify (and I can leave the immutability out of the question), when a system stored on the performance tier applies retention, merges the oldest incremental into a full, Veeam will push out the old data from the capacity tier and add just the changed blobs which will represent the oldest restore point when the metadata is stitched together when requested for restoration?Thanks for all your help
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
