Contact Us

Author name: Managecast Technologies

Office 365 Backup, Veeam

“Processed by Another Job” Warning in Veeam M365 Backups

/

The “Processed by Another Job” warning in Veeam M365 backups appears when multiple backup jobs attempt to back up the same Microsoft 365 object (such as mailboxes, SharePoint sites, or OneDrive accounts). When Veeam detects that an object is already being processed or backed up by another job, it flags this warning to avoid redundant operations and potential data consistency issues. This warning typically occurs due to overlapping backup job configurations. You may have multiple backup jobs configured to protect the same set of mailboxes, SharePoint sites, or OneDrive accounts. For example, if one job is set to back up all mailboxes in your organization and another job targets a specific department that includes those same mailboxes, a conflict arises. Best Practices to Address the Warning Review Your Backup Job Configurations Schedule Jobs to Avoid Overlap Fortunately, the “Processed by Another Job” warning does not typically indicate a critical issue. Veeam intelligently manages the backup process to ensure that each object is protected only once, even if it’s referenced in multiple jobs. This warning serves as an alert that your configuration may need to be optimized to avoid inefficiencies or unnecessary resource consumption. If you have any questions or need assistance with your Veeam M365 backups, feel free to reach out to us at support@managecast.com. We’re happy to assist with troubleshooting and resolving your issue.

Veeam

Veeam I/O filter for CDP fails to install on ESXi 6.x 

/

Introduction  When installing the Veeam Continuous Data Protection (CDP) I/O filter on an ESXi 6.x cluster, the installation may fail with a generic error message that the install failed.  The Issue  This can often be caused by a certificate signing issue with older versions of ESXi 6.x. Per VMware/Broadcom documentation: https://knowledge.broadcom.com/external/article?legacyId=76555 More details about this issue can sometimes be found in the I_O_filter_deployment.log:  Solutions  There are two solutions for this issue:  Solution 1: Upgrade ESXi Version (Recommended)  VMware recommends upgrading to a later release of ESXi.  Version 7 or 8 have been known to work without issues.  Solution 2: Manual VIB Installation on ESXi Hosts   The other solution is to manually install the VIB on the ESXi hosts via SSH and the command line.  It is important to note that the VIB must be installed on all ESXi hosts in each cluster that will be using CDP.  CDP is installed at the cluster level.  After installing the VIB manually, run the Veeam I/O filter install again; it should already see the I/O filter installed and up-to-date, and it will just run the install process again and it should succeed since the I/O filter is already properly installed.  To install the VIB manually on an ESXi host, follow these steps:  1. Locate the VIB files on the Veeam server:  On the Veeam backup server, in the following directory by default:  C:\Program Files\Veeam\Backup and Replication\Backup\Packages  There will be three files that all start with veecdp-offline-bundle:  2. Install the VIB via esxcli command line: SSH into each ESXi host in the cluster and install this VIB using the following command: The –no-sig-check tells ESXi to ignore the signature check, which is what is causing the issue with the install from Veeam 3. Rescan and Synchronize Storage Providers in vCenter: While not usually required, it is recommended to rescan and synchronize storage providers from vCenter. 4. Retry the I/O Filter Installation in Veeam: Return to Veeam and attempt the I/O filter install again.  During the install process, it should see the I/O filter already installed and up-to-date.  Continuing the installation wizard should allow the install process to successfully complete. Conclusion Issues with certificate compatibility can prevent the installation of the Veeam CDP I/O filter on older versions of ESXi 6.x.  VMware recommends to upgrade to version 7 or later to correct this; however, if upgrading isn’t possible, the manual VIB installation process should work, allowing the I/O filter to be successfully installed and function correctly.

Uncategorized

Veeam CDP jobs hang and no data transfers when using Cloud Connect and the default port on the service provider side is changed from 6180

/

Introduction When using Veeam to backup or replicate virtual machines over the internet to a service provider, most likely the service provider will be using Veeam Cloud Connect.  By default, Veeam Cloud Connect uses port 6180 to receive incoming traffic from tenant (customer) locations. If the service provider already has something listening on port 6180, they may want to try and use a different port other than 6180 for their Veeam Cloud Connect service.  This should work with most Veeam applications and services; however, this usually will not work with CDP. The Issue Through may tests and working with Veeam support, it has been determined that CDP must use 6180 when transferring data.  If port 6180 is changed on the service provider side for the Cloud Connect interface, CDP will make the connection from the tenant to the service provider and it will appear to be working; however, no data will ever transfer, it will just sit and appear to be stuck at the transfer data phase. Veeam support has not confirmed why this behavior exists, but they have concluded that some part of CDP uses port 6180 to transfer data and this cannot be changed. No Workaround or Solution Unfortunately, when testing possible workarounds or looking for solutions for this, nothing seemed to work. Attempts were made at the firewall to redirect the port using port translations.  Software tools were installed directly on the service provider and tenant host systems to do port redirection before it ever leaves the server, allowing Veeam to use port 6180 then changing the port on the host, then changing the port back on the receiving host, back to 6180, attempting to trick Veeam into believing it truly is using port 6180.  These failed as well. Conclusion Currently, Veeam is not aware of a fix or workaround at this time that will allow CDP to transfer data on a port other than 6180.  This may be addressed in a future build or release, but there is no mention of that at the time of this writing.

Veeam

Storage policy does not show up for Veeam CDP policy when using vCloud Director

/

Introduction When setting up a Veeam CDP policy and also using vCloud Director, the tenant account may not be able to choose the correct storage policy to assign to the CDP policy.  When going through the CDP policy wizard, some or all of the storage policies may be missing as options to select for destination storage. The Issue When using vCloud Director for tenant accounts, the tenant’s VDC is assigned storage based on storage policies.  When the Veeam CDP I/O filter is installed, Veeam automatically creates its own storage policy in VMware called Veeam CDP Replication.  This policy uses host-based rules for replication and chooses veecdp as its provider. While storage policies will often be used to select the storage itself based on something like tags, in this case Veeam is leveraging the VMware I/O filters of the host itself and matching the policy based on which host or hosts have valid I/O filters, then any storage connected to that host is allowed.  It is recommended to create your own custom storage policy, choosing the same host-based replication rule veecdp, the same as Veeam creates automatically, but in your own custom policy also select storage tagging to select which storage you want a specific tenant to use.  You can use host-based rules and storage tagging together. Veeam installs and communicates the I/O filter through vCenter to know which hosts it can use.  Sometimes, if an ESXi host has had its storage provider certificate updated recently, vCenter may not have automatically synchronized the changes, and furthermore, vCenter may have the old certificate data stuck in its database.  This needs to be cleaned up and synchronized. You can check vCenter’s status of the ESXi host’s I/O filter certificates here.  If your state is inactive or shows the certificates expired, this may be your problem: You can check the certificate installed on the ESXi host by using the URL provided by vCenter: When going to the URL provided, you should be able to check your certificate to verify one is installed that is usable and not expired.  Your browser may not trust this certificate, but this is used between vCenter and ESXi, so it’s only important that vCenter trusts it. If your ESXi certificate has expired, then it needs to be renewed.  If your ESXi certificate is valid, but it shows as invalid in vCenter, then vCenter needs to manually be updated.  This document from Broadcom/VMware shows how to do this: https://knowledge.broadcom.com/external/article/318887/certain-iofilter-providers-are-showing-a.html Conclusion Sometimes when the ESXi host’s certificates are updated, vCenter doesn’t always update its own internal database with this information correctly.  If this happens, vCenter may not recognize the ESXi hosts as having valid certificates for the I/O storage policies, which Veeam uses for CDP.  This in-turn causes vCloud Director to not be able to use storage policies that rely on host-based I/O filters, so those policies will not show up for a vCloud Director tenant when creating a new Veeam CDP policy.

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.

Uncategorized

Resolving Veeam Backup Errors for Domain Controllers with SentinelOne

/

Introduction If you’re using Veeam to back up domain controllers and have recently installed or upgraded to SentinelOne Agent version 23.2.3.358, you might encounter backup failures. This post will guide you through understanding the issue and provide a workaround to resolve it. The Issue After installing or upgrading to SentinelOne Agent 23.2.3.358 on a domain controller, Veeam backups may fail with the following error: Processing SERVER Error: VSSControl: -805306334 Backup job failed. Cannot create a shadow copy of the volumes containing writer’s data. Cannot prepare the [NTDS] data for a subsequent restore operation. Cannot process NTDS data. Updating BCD failed. Cannot execute [SetIntegerElement] method of [\SERVER\root\wmi:BcdObject.Id=” {56a36c07-368c-11eb-bd3b-edf2c267e255}”,StoreFilePath=””]. COM error: Code: 0xd0000022 This error is triggered by the boot protection feature of SentinelOne, which interferes with the VSS (Volume Shadow Copy Service) process used by Veeam for backups. Workaround Solution Until a fix is provided by either Veeam or SentinelOne, you can use the following workaround to disable the boot protection feature in SentinelOne. Retrieve the Passphrase In the SentinelOne console, look up the passphrase for the affected machine. You’ll need this passphrase to make local changes on the machine. Disable Safe Boot Protection Log on to the machine with administrative privileges. Open an elevated Command Prompt or PowerShell and run the following commands:     cd “C:\Program Files\SentinelOne\Sentinel Agent 23.2.3.358”    .\SentinelCtl.exe config safeBootProtection false -k “PASSPHRASE”    Replace “PASSPHRASE” with the actual passphrase you retrieved from the SentinelOne console. Restart the Machine (Optional) While it’s not confirmed if a reboot is necessary, performing a restart of the machine immediately after making the change is recommended to ensure the new settings take effect. Conclusion By following these steps, you can temporarily resolve the backup errors caused by the SentinelOne Agent. Keep an eye out for updates from Veeam or SentinelOne that address this issue permanently. In the meantime, disabling the boot protection feature should allow your backups to proceed without errors. For more technical tips and troubleshooting guides, stay tuned to our blog! Feel free to reach out if you have any questions or need further assistance. Happy troubleshooting!

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.

Managecast News

Managecast Achieves Platinum Veeam Cloud & Service Provider Status

/

Managecast is excited to announce that it has achieved Platinum status in the Veeam® Cloud & Service Provider (VCSP) program. Veeam Software is the #1 leader by market share in Data Protection and Ransomware Recovery. This prestigious designation highlights Managecast’s extensive experience and expertise in delivering Veeam-powered solutions, specifically tailored to build reliable, enterprise-grade Backup as a Service (BaaS) and Disaster Recovery as a Service (DRaaS) offerings. Managecast is excited to announce that it has achieved Platinum status in the Veeam® Cloud & Service Provider (VCSP) program. Veeam Software is the #1 leader by market share in Data Protection and Ransomware Recovery. This prestigious designation highlights Managecast’s extensive experience and expertise in delivering Veeam-powered solutions, specifically tailored to build reliable, enterprise-grade Backup as a Service (BaaS) and Disaster Recovery as a Service (DRaaS) offerings. Nathan Golden, Founder of Managecast, expressed his enthusiasm about the achievement, stating, “Achieving Platinum status within the Veeam Cloud & Service Provider (VCSP) program is a testament to our team’s hard work and deep expertise in Veeam solutions. This recognition empowers us to further enhance our service delivery, ensuring our clients receive the most advanced and reliable data protection and ransomware recovery services available today.” Veeam supports Managecast in this elevated status. “We are thrilled to acknowledge Managecast’s achievement of Platinum status in the Veeam Cloud & Service Provider program. Veeam’s #1 data backup and ransomware recovery solutions combined with Managecast’s exceptional service delivery and expertise in Veeam technologies ensures optimal success and enables cyber resiliency for our joint customers,” says Matt Kalmenson, vice president of Veeam Cloud & Service Providers, Americas at Veeam. Managecast has been providing robust disaster recovery and cloud backup solutions for over 20 years. With this new status, Managecast will continue to leverage the latest Veeam technologies, including the Veeam Data Platform to enhance its offerings, ensuring clients’ critical data is secure and recoverable in the event of any disaster. This elevated status allows Managecast to offer more competitive pricing, enhanced support, and access to the latest Veeam products and features. “We are excited to bring these additional benefits to our clients, helping them to not only protect but also manage their data more efficiently in an ever-evolving digital landscape,” added Golden. For more information about Managecast and its services as a Platinum VCSP, please visit www.managecast.com or contact Nathan Golden at ngolden@managecast.com. About Managecast Technologies, Inc. Managecast Technologies, Inc. specializes in providing complete cloud backup and disaster recovery solutions, fully managed and monitored. With over 20 years of experience, Managecast has been committed to helping businesses protect their data and ensure business continuity, catering to clients across the globe.

DRaaS, General Cloud Backup

Mid-Year Backup Health Review: Tips and Best Practices

/

As we approach the middle of the year, it’s a crucial time for businesses to review their backup and DR plans. This mid-year checkup ensures your systems are up to date, your data is secure, and your recovery strategies are effective. Let’s dive into why a mid-year backup health review is essential and some tips on conducting one effectively. Why Conduct a Mid-Year Backup Health Review? A mid-year review helps you address potential vulnerabilities, update your strategies to cover new data types or technologies, and reaffirm that your data recovery plans align with current business objectives. It also provides a great opportunity to test your systems in a controlled environment, ensuring they function as expected in an actual emergency. Key Components of a Backup Health Review Best Practices for a Successful Backup Health Review A mid-year backup health review is not just a routine checkup; it’s an essential part of a proactive data protection strategy. By regularly assessing and updating your backup procedures, you ensure that your business can withstand and quickly recover from data-related incidents. Take this opportunity to tighten your defenses and keep your data safe and recoverable, no matter what lies ahead.

  • (513) 735 - 6868
  • sales@managecast.com
  • 8354 Princeton Glendale Rd #108
    West Chester, OH 45069
Facebook X-twitter Youtube Linkedin

Powered by Veeam

Veeam Solutions

DRaaS

Resellers & Partners

Support

Blog

About

Scroll to Top