The error above shows up when trying to perform a failover in a Hyper-V environment. If you try to start the Network Extension Appliance manually you get the same error. icacls <Path of .vhd .avhd or .vfd file from step 1> /grant “NT VIRTUAL MACHINE\ <Virtual Machine ID from step 2> “:(F)
“Some Agents were not processed during the copy interval.” “Some VMs were not processed during the copy interval.” Errors similar to above can occur for periodic backup copy jobs created prior to VBR v12. This means that the job was actively transmitting data, or had not gotten a new version of the backup to copy when the copy interval expires. The resolution will differ depending on the cause. you may have an issue with the primary backup job used as the source that delayed its availability for the backup copy job to process. If this happens repeatedly, you can adjust the scheduling of the backup copy job. For example: if you want the backup copy job to run every 24 hours, make the copy interval start the same time as the local backup job it sources data from. This ensures the backup copy job processes the source items as they complete in the primary job. For more information on Backup copy jobs for VBR v11 please see the following link: https://helpcenter.veeam.com/archive/backup/110/vsphere/backup_copy_modes.html Note that in v12 the processing of periodic backup copy jobs were changed to allow more control over scheduling, so you are not likely to see this error in v12.
When a certificate change to the SMTP server that your Veeam agent uses to send out notifications occurs, the notifications may start failing to send. Your jobs will begin displaying the warning message, “Sending e-mail report Details: The remote certificate is invalid according to the validation procedure.” This can be easily resolved by running through the email notification settings and testing that it can connect. 2. In the Configure and test email notifications window, verify and test your SMTP email settings. Selecting Test Now will test the current settings. 3. If the Test Now fails, you may need to make a change to warrant Veeam to rescan the certificate. Veeam will only rescan the certificate if a change has been made here. Clicking the Mail server drop down, switch it to one of the other options, then switch back is a significant enough to warrant a rescan. Click Apply to initiate the rescan. 4. You should be met with an alert stating that the certificates are mismatched. Continue through the certificate window. Run the Test Now option to verify Veeam can now connect. There may be other reasons that could be interrupting the communication between your Veeam Backup Agent for Windows and the SMTP server. If you would like further assistance please contact Support@Managecast.com.
