Veeam

Veeam

Veeam CDP Errors: Failed to create long-term restore point – VM configuration for the initial sync completed with errors

Introduction If you are setting up Veeam CDP from scratch and are attempting to use seeding (seed copy) in order to speed up the process of getting the replication started, you may encounter the following errors: CDP seeding is when the backup files or replica of a VM is copied to a destination, and from there a CDP policy is created to replicate the VM from the original source to the destination and CDP will attempt to use the files that have already been copied to the destination to start the CD replication process rather than having to copy the entire virtual machine over the internet or LAN (depending on where you have CDP running).  Seeding is typically used for transfers over lower bandwidth connections, such as the internet. The Issue Veeam support believes this issue may be caused by the UUID of the VMDK (virtual disk) from the seed and the original source being the same.  When Veeam attempts to create the CDP replica checkpoint, a disk with the same UUID is already present and causes it to fail. Possible Workaround This issue has been seen with multiple builds of version 12.  Veeam support has acknowledged this as a bug and has said they plan to have a fix for it in a future release, but have no indication of when or what release that may be. Veeam suggested a possible workaround may be to change the UUID of the VMDK at the destination, however, in our own internal testing this did not work. Retrieve the UUID The UUID of the VMDK can be checked by using SSH to log into the ESXi host and typing the following command, where datastore, VM folder, and VM name are correct for your environment: vmkfstools -J getuuid /vmfs/volumes/<datastore name>\<VM folder>\<VM name>.vmdk UUID is 60 00 C2 9a 39 ef 7d 37-7c d6 b0 51 41 b8 b1 27 When running this on the original source VMDK and the destination VMDK, both UUID should be the same. Change the UUID To change the UUID, simply run the following command: UUID is 60 00 C2 96 99 01 13 61-76 3f 1c 9e 29 d3 e1 65 Conclusion Veeam has acknowledged that this is a bug with CDP and seeding.  While Veeam does plan to have a fix for this, the fix is planned for a future release, with no current indication of when or what release version that may be. The UUID change may work for some cases, however, in our own internal testing it did not fix the issue. CDP can still be setup by creating a new policy and allowing it to copy the data over the internet to setup its replica copy, and we have not seen any issues with this working.

Office 365 Backup, Veeam

Managing What You Backup Through the Portal with Veeam Backup for Microsoft 365

Most of the time, a full organization backup fits the needs of most users. However, there are times when you need to select specific mailboxes and groups to back up. Through the backup portal, selecting exactly what you need is made easy. First, it may help to check what you are currently backing up. If you are setting up a job for the first time, you can skip this step. You can find this information under the Reports section by selecting Licensed Users: Once you’ve identified the critical accounts that must be backed up, you can edit your job. In the portal, navigate to the Jobs tab. Ensure your company is selected in the drop-down menu (or if managing multiple tenants, select the company you wish to edit) and select the job you want to edit. To enable the ability to select specific objects, select the Backup the following objects option when editing the job. Note: These steps can be done when setting up your initial backup job as well. Once selected, there are two ways to add these users: Option 1: Per Group. This is the easiest way of managing what is backed up. Clicking the Add button and selecting Groups will bring up a full list of Groups in your environment. Creating a group specifically for backups is a simple way of ensuring the users that need to be backed up are backed up. Existing groups can be added, but we recommend managing a single group instead of multiple. Option 2: Per User. If you have a need to select specific users, perhaps to ensure you are not over X number of licenses, then this may be your best option. Clicking the Add button and selecting Users will bring up a full list of users in your environment. Here, you can select exactly which users you would like to backup.  Additionally, you can select specific Sites and Teams to backup. If you ever need to exclude a user, or a user object (OneDrive, Site, Teams), from a backup, this can be done on the very next screen. The most common reason to exclude a user is if a user in a selected group does not need to be backed up. Identical to adding a user, excluding a user, or any other object is done by selecting the Add button, choosing the type of object you want to exclude, and selecting it from the list. On special occasions, only a single user, group, site, or Teams needs to be excluded. For example, a user may need their mail backed up, but not their OneDrive. In this situation, just like above, you would select the user that needs to be excluded. Once selected, click on the users and press the Edit button. Here, you can select what objects you would like to exclude: Once all the changes have been made, finish the wizard and Save the job settings. That’s all there is to it! As always, if you ever need assistance, we are here to help answer any questions or assist with your backups. Please reach out to Support@Managecast.com for more information, questions, or assistance.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Backing Up Public Mailboxes Limitations and Settings

Veeam has added the ability to backup public folders again, but with a few setting changes and limitations that you may run into. Here are a list of some of these that you may run into or need to adjust: Additionally Veeam information on public folders can be found HERE. Microsoft is constantly pushing changes that may affect the backups. These are just some things to check when trying to backup a public folder. If you continue to run into issue, reach out to Support@Managecast.com for assistance.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Not allowed to access Non IPM folder Error

Microsoft constantly pushes out changes, and sometimes these changes break things for 3rd party vendors. After a recent change, we had started seeing the error message “Failed to get folder properties. Not allowed to access Non IPM folder” across several backups. The Microsoft change to the properties of the TeamsMessagesData folder caused Veeam to be unable to retrieve the data over the EWS APIs. Luckily, the fix for this a quick and easy! Note: This requires you to be on Veeam for Microsoft 365 6.1.0.1015 or Newer. Implementing the change on prior versions will NOT resolve the issue. We recommend upgrading to a supported version before applying the following fix. Recent Veeam for Microsoft 365 releases cover this issue. Please follow these steps: If you continue to experience issues or would like assistance with any other issues you may be experience, please reach out to Support@Managecast.com.

Linux, Veeam

Veeam Backup and Replication Linux VM “Failed to check fingerprint” Error

If you’ve recently upgraded to Veeam Backup & Replication 12.1 and have begun seeing your Linux jobs fail with the “Failed to check fingerprint” error, there is no need to worry! This issue is easily resolved with a few clicks. The cause of the error comes from the change to the format used by Veeam to store the Linux SSH fingerprints. If the config database is stored in an SQL 2019 or 2022 instance, the conversion process fails to process blank current_fingerprint values and sets them to NULL, causing the error in Veeam. To resolve the issue, you must manually validate each fingerprint for each machine: If these changes have not resolved the Failed to check fingerprint error, or have any other backup questions, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 Invalid Serialized Stream, Unknown Opcode Found:4 error

A recent Microsoft change to the Serialized Property of Exchanges items have caused “Invalid ‘serialized stream, unknown opcode found: 4’” errors across Veeam for Microsoft 365 users. This issue has been resolved with new hotfixes for users on versions 7.0.0.4551 and 7.1.0.1401. Below are the KB links to download the hotfix that pertains to your environment: Hotfix for 7.0.0.4551 P20231218 Hotfix for 7.1.0.1401 P20231218 To install the hotfix, follow these quick steps: If you continue to experience the error, would like assistance with the hotfix, or have any other backup replated questions, please reach out to Support@Managecast.com.

Veeam

Veeam How to Manually Updating Suspicious File List in Limited Network Environment

It isn’t uncommon to come across an environment that has limited to no access to the internet. This can be for many reasons such as security or regulations. In these instances, your Veeam console won’t have the ability to reach out to the Veeam database to update the SuspiciousFiles.xml, which logs known malware extensions. Here areas steps to download and update the xml file manually: Additional Veeam information can be found in KB4514. If you have any questions or would like any assistance, please reach out to Support@Managecast.com.

Office 365 Backup, Veeam

Veeam for Microsoft 365 What’s unsupported after the deprecation of basic authentication?

After Microsoft’s decision to deprecate basic authentication in favor of modern authentication, there are a few things that will change when switching from basic to modern. Below are items that are not supported through modern app-only authentication, and support that has been added in newer releases: Further information on what is/is not supported when switching to modern authentication can be found here KB3146. If you would like assistance, or have any further questions on what is supported, please email Support@Managecast.com.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “objects types are unsupported in the modern app-only authentication mode”

After Microsoft’s deprecation of basic authentication, item’s that were excluded that aren’t supported in modern app-only authentication mode will raise a warning. The warning will specify, “Found # excluded objects. Some of the objects specified for exclusion will be ignored during processing because such objects types are unsupported in the modern app-only authentication mode.” If you are unsure what is no logner supported, you can check HERE. To resolve this warning: If you continue to experience issues with your M365 job, or any Veeam issue, please reach out to Support@Managecast.com.

Scroll to Top