VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
We relocated one of our VMs to another backup job and noticed that the job completion status information for the VM is “Resetting CBT per job settings for active fulls”. Our backup jobs are configured with incremental backups and one synthetic full backup per week. I am curious if we move one of the VMs to another backup job, does Veeam automatically perform an active full on it? Thanks Pete
Does Veeam plan to provide an install platform for Linux-based OS, referring to the installation of the Veeam Backup and Replication Application?
Has anyone experienced this issue after performing the Veeam v12.1 upgrade? Unable to connect to guest OS for guest processing. Cannot find Linux guest credentials. Our Veeam environment is configured to utilize vSphere backup tags (which includes both Windows and Linux VMs).After the upgrade to v12.1 our backup jobs that included Linux VMs didn’t backup.We have opened up a support call, and in the meantime have a work around. If we would specify each Linux VM along with the backup tags within the backup job, the Linux VM does backup.
We have configured our backup copy jobs to execute in a continuous mode and hadn’t any issues until the other day. Ten (out of 100) of our backup copy jobs failed, with the error of “Unable to copy the backup: some backup files are located on an unavailable scale-out repository extent”. Checking the restore points on the source and target repositories, we noticed the restore points (for the most recent backup) for the target repositories were in an incomplete state. We performed the following manual steps to resolve; Disable backup copy job After reviewing the target repository from the backup copy job, the identified servers with the error, have the most recent restore point showing incomplete. Rescan the target repository Then process the incomplete restore points by selecting forget Rescan the target repository Enable backup copy job and executeWe did open a support case and the engineer discovered the issue we experienced stemmed from the backup copy job interfering with the bac
We have six backup copy jobs that are failing with the following error;Error: Violation of PRIMARY KEY constraint 'PK_Storages'. Cannot insert duplicate key in object 'dbo.Backup.Model.Storages'. We have rescanned the repositories and reran the backup copy jobs, but still experiencing this error.A case has been opened with Veeam support and we are anxiously awaiting their response.Thanks
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.