Author name: Managecast Technologies

General Cloud Backup

Veeam Error:  Windows recovery image file not found

The “Windows recovery image file not found” error in Veeam Backup and Replication can occur if the Windows Recovery Environment is disabled or missing a necessary component.  This will cause the Veeam Recovery Media creation to fail.  First, check and make sure that the Windows Recovery Environment is enabled by opening an administrative command prompt on the machine that is causing the error, and run the command: If the Recovery Environment is disabled, you can reenable it by running the command: If the issue is occurring due to missing Windows Recovery Environment files, please refer to Veeam KB article kb2685 for additional information.  If the issue continues to persist after repairing the Windows Recovery Environment outlined in Veeam KB article kb2685, you can disable recovery environment collection during the job by adding a registry key. PLEASE NOTE: This should ONLY be done if the issue is isolated to a single Agent job.  In the event of a disaster recovery for a machine with this registry key added, you will need to use a recovery image from another Agent to boot the machine.  The registry key is below:  If you would like assistance, or have further questions regarding this issue, please email support@managecast.com.

Managecast News

Celebrating 25 Years of Managecast: A Legacy of Data Protection 

A Quarter-Century of Innovation & Trust  In 2025, Managecast marks 25 years of protecting businesses from data loss, downtime, and disaster. Over the years, we’ve evolved with technology, growing from tape-based backups to cutting-edge cloud and AI-driven security solutions—all while staying true to our mission: ensuring business resilience.  How Far We’ve Come  When Managecast started, backups were slow, storage was limited, and recovery was a challenge. Today, we provide seamless, secure, and efficient backup and disaster recovery solutions that help businesses stay ahead of cyber threats, compliance needs, and unexpected disruptions.  Key Milestones Along the Way  Through it all, we’ve remained a trusted partner, providing expert guidance and support to organizations that rely on us to safeguard their most valuable asset: their data.  The Next 25 Years: The Future of Backup & Disaster Recovery  While we celebrate how far we’ve come, we know that the future will bring even bigger challenges in cybersecurity, disaster preparedness, and data protection. Managecast is committed to staying ahead of the curve, focusing on:  Thank You for 25 Incredible Years!  This milestone wouldn’t be possible without our customers, partners, and team members. Your trust and collaboration have made our journey possible, and we’re excited for what the future holds.  “Our customers rely on us to protect their most valuable assets: their data. That responsibility drives us to continually innovate and improve. We look forward to the next 25 years of helping businesses stay resilient.” – Nathan Golden, Founder of Managecast.  Whether you’ve been with us since the beginning or just joined our community, we’re grateful for your support. Here’s to the next 25 years of innovation, security, and peace of mind! 

General Cloud Backup, Troubleshooting, Veeam

“Failed To Index Guest File System” Error in Veeam Backup and Replication 

When working with Veeam Backup & Replication, ensuring seamless backups is a critical part of IT infrastructure management. However, you might occasionally encounter errors that disrupt the process, such as:  Failed to index guest file system. Veeam Guest Agent is not started. Failed to prepare guest for hot backup. Details: Failed to connect to guest agent. Errors: ‘Cannot connect to the admin share. Host: [Target Machine]. Account: [Account Name]. Win32 error:The network path was not found. Code: 53  Or you may encounter errors such as:  Failed to inventory guest system: Veeam Guest Agent is not started. Failed to index guest file system. Failed to prepare guest for hot backup. Details: Failed to connect to guest agent. Errors: ‘Cannot connect to the admin share. Host: [Target Machine]. Account: [Account Name]. Win32 error:Access is denied. Code: 5  These errors can be daunting, especially if you’re unsure where to begin troubleshooting. It usually indicates issues related to network connectivity and/or permissions. By understanding the underlying causes and following structured troubleshooting steps, you can quickly identify and resolve the problem.  Error Codes Breakdown  Win32 Error Code 53: “The network path was not found.”  This error indicates that the Veeam server is unable to reach the specified host over the network. Common causes include:  Win32 Error Code 5: “Access is denied.”  This error occurs when the account used for authentication lacks the necessary permissions to access the admin share or perform guest processing tasks.  Troubleshooting Steps  1. Verify Network Connectivity Confirm that the host is reachable: 2. Verify Admin Share Accessibility Confirm that the admin share is enabled and accessible using Command Prompt: 3. Check Credentials and Permissions Verify that the account used for the job has the necessary permissions: 4. DNS and Hosts File Confirm that the Veeam server can resolve the hostname to the correct IP address: 5. Test Backup Job with Another Account If all else fails, test the backup job using a different account: By following these steps, you should be able to identify and resolve the “Failed to index guest file system” error. If you encounter persistent issues or need additional assistance, don’t hesitate to contact our support team at support@managecast.com. We are ready to help ensure your backup operations run smoothly and effectively!

General Cloud Backup, Office 365 Backup, Troubleshooting, Veeam

Veeam for Microsoft 365 v8 “Missing Permissions” Warning 

Updated 3/10/2025 Permissions are the backbone of successful backups in Veeam for Microsoft 365. Without the right access levels, Veeam cannot read, write, or manage the data required for seamless backup and restore operations. With the recent update to version 8, Veeam for Microsoft 365 requires the following permissions to be granted to the backup Application Registration: Assigning the Global Reader Role to the Application Registration To assign the Global Reader role, follow these steps: 1. Sign in to the Microsoft Entra admin center and on the left side panel, navigate to Identity and click on Show More 2. Next, navigate to Roles & admins > Roles & admins. 3. In the Administrative roles list, find the Global Reader role and click on it. 4. In the Global Reader window, click Add assignments. The Add assignments wizard will open. *If you don’t have any members assigned to the role, click on Select members link at the bottom. *The role needs to be assigned to the App Registration, not the service account.  5. In the Add Assignments window, search for the App Registration used for M365 backup jobs. (If you are unsure which application is used for backups, please contact our support team.)  6.Check the box next to the App Registration and click Add.  The Global Reader role is now assigned to the App Registration.  Assigning API Permissions to the Application Registration To assign missing permissions or verify existing ones, follow these steps: 1. Navigate to Applications > App Registrations, click on All Registrations and click on the App Registration used for the backup jobs. (If you are unsure which application is used for backups, please contact our support team.)  2. Once the App Registration is opened, under Manage, click on API Permissions Here, you can review the list to see what permissions have already been granted. 3. Click Add a permission to add new permissions. For ChannelMember.Read.All, after clicking on Add a permission button, navigate to Microsoft Graph > Application Permissions and search for ChannelMember. Expand ChannelMember line, check ChannelMember.Read.All and click Add Permissions.  For Exchange.ManageAsApp, after clicking on Add a permission button, navigate to APIs my organization uses and search for Office 365 Exchange Online and click on Office 365 Exchange Online > Application Permissions. Search for Exchange, expand the Exchange line, check Exchange.ManageAsApp and click Add Permissions.  4. After adding new permissions, click on Grant admin consent for [your organization] to activate them. Without admin consent, the newly added permissions will remain inactive.  Conclusion Ensuring the proper permissions are assigned in Microsoft Entra is critical for the smooth operation of Veeam for Microsoft 365. Following the steps outlined above will help you resolve the “Missing Permissions” warning and ensure your backup jobs run successfully. If you encounter any issues during this process, please reach out to our support team at support@managecast.com for assistance. We will be happy to help!

General Cloud Backup

Start Strong in 2025 with These Backup Resolutions

As we step into 2025, it’s an ideal time to evaluate and enhance your IT strategies, particularly your data backup and disaster recovery plans. A robust backup plan is essential for safeguarding your business against data loss and ensuring continuity. Here are three key resolutions to strengthen your backup strategy this year: 1. Assess Your Current Backup Plan Regularly reviewing your backup plan is crucial to ensure it aligns with your business needs and adapts to evolving threats. Consider the following: 2. Implement Immutable Backups With the increasing prevalence of ransomware and accidental deletions, incorporating immutable backups into your strategy is vital. Immutable backups ensure that once data is written, it cannot be altered or deleted, providing a reliable safeguard against data tampering. Key benefits include: 3. Regularly Test Your Recovery Process The effectiveness of your backup plan is ultimately determined by your ability to restore data when needed. Regular testing of your recovery process ensures that backups are functional and that your team is prepared to execute recovery procedures efficiently. Steps to consider: Conclusion Prioritizing these backup resolutions will enhance your data protection strategy and contribute to your business’s resilience in 2025. At Managecast, we specialize in tailored backup and disaster recovery solutions to meet your unique needs. Contact us today and take the first step toward a more secure future.

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.

Scroll to Top