VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Thanks Chris
Thanks all
yes, it was working on V12
We have discovered that combination backup tags seem to be an issue, because if we separate into individual backup tags. The backup is working.
Case #07083882 Cannot find Linux guest credentials.
This morning as I was checking our Veeam backup jobs on one of our B&R servers, a backup job had retried several times before it finally completed. As I scrolled through its history two of the servers were failing because the corresponding .vib file was locked by the associated backup copy job (configured as continuously). After several retries of the backup job, the backup of the servers did complete.
Veeam support has submitted my enhancement request;
To make that change to the backup copy jobs would be a challenge since we have so many. If Veeam offers the continuous feature, you would think the application would prevent it from executing until its associated backup job completed.
Veeam support responded last Friday with the following. It seems as though there was some kind of event that happened during the original synthetic full run which caused the problem which may have involved something environmental. The synthetic fulls have generally been successful previously.Because the trigger seemed to be some temporary condition, and because the firmware on the storage has now been updated to 4.3.6, I wouldn't expect to see reoccurrence even prior to getting the updated hotfix.The affected backup chains were still in a problem state in the database that is preventing the replication from succeeding, but only the target side catalyst is affected. Because of this, it would be possible to either create a new catalyst store or just select affected backups and "delete from disk" and allow a fresh replication of the files. This has worked as a temporary fix.Pete
Veeam support is working out a fix in R&D and testing, hopefully it will be released soon.
Sure will, our SQL is on its own server, and we utilize HPe StoreOnce for the repositories. We are still waiting for a support engineer to review and provide us with a fix. While we are in a wait state, our storage architect is upgrading the firmware of a StoreOnce pair.
Support has stated there is a known bug and will be working with us on a fix. However, it appears we need to make sure our StoreOnce firmware is at 4.3.6.Keep you in the know.
We are on Veeam version 12.0.01420 P20230718 The error is occurring with our backup copy jobs, which we utilize StoreOnce catalyst repositories.
Even though we are not currently utilizing Veeam backup for AWS, this video is a good introduction to the product.
This Veeam P2V process works great for a physical windows server, which we have already accomplished. We attempted the P2V process with a physical SQL cluster, but for some reason the cluster disks were not recognized during the Instant Recovery process.Thoughts?
would love to, but I will attending remotely. Have fun and hit them straight. 😀
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.
