Author name: Managecast Technologies

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 SharePoint “The remote server returned an error: (429)”

The nuisance error, “The remote server returned an error: (429)” in Veeam Backup for Microsoft 365 indicates that you have exceeded the request rate limit imposed by Microsoft. This occurs when too many requests are made to Microsoft within a specific time frame. We commonly see this during the initial Veeam for M365 backup and the error resolves itself during the automatic retry, which is enabled by default. If you would like to make changes on the backend in Microsoft, such as editing Retry-After headers or decorating traffic, you may refer to this Microsoft Article on how to avoid getting throttled in SharePoint. If the (429) error persist, please reach out to us at Support@Managecast.com. We’re happy to assist in troubleshooting and resolving your issue.

Veeam

Are you using Veeam to its fullest potential?

In today’s digital age, data is the lifeblood of businesses. Protecting and ensuring the availability of this data is crucial for the success and continuity of any organization. Many organizations like yours are already utilizing Veeam, but are you using it to its fullest potential?  Step One: Are you utilizing the features already built into the software you own?  Network Extension Appliance (NEA)  The Veeam Network Extension Appliance, a part of your Veeam license, facilitates effortless access to your disaster recovery (DR) location. This appliance cleverly makes DR servers appear as though they are on the production network. It is easy to configure, deploy, and use, allowing you to set it up and then rest easy, knowing your DR strategy is sound.   See more about the NEA here: https://helpcenter.veeam.com/docs/backup/cloud/cloud_network_extension_appliance.html?ver=120       SureBackup  SureBackup is a service from Veeam that creates isolated virtual environments where backup or replicated VMs can be started and tested without affecting the production environment.  SureBackup streamlines the testing process, allowing your team to quickly and easily assess the recoverability of VMs and applications without the complexity of setting up separate testing environments.   Learn more about SureBackup here: https://bp.veeam.com/vbr/2_Design_Structures/D_Veeam_Components/D_SureBackup/SureBackup.html Linux Hardened Repositories  A Linux Hardened Repository is purpose-built to provide businesses with a secure and trusted immutable backup solution for their backup data, ensuring that their data is safe and reliably recoverable when disaster strikes.  This solution is built with hardened security and compliance in mind, guaranteeing the immutability of all your data and safeguarding it from any unauthorized changes or removal. This is especially significant for organizations handling sensitive information such as financial records and personally identifiable data.  Learn how to set up your Linux Hardened Repositories here: Step 2: Are you doing Disaster Recovery? Veeam Disaster Recovery as a Service with Cloud Connect Veeam Cloud Connect seamlessly enables customers to easily leverage disaster recovery as a service. This approach empowers IT departments to capitalize on the benefits of a multi-cloud architecture while retaining direct communication and a close working relationship with the DRaaS provider.  By shifting the responsibility of disaster recovery to a trusted service provider like Managecast, businesses can focus on core operations while ensuring the safety of their data. This flexibility allows IT departments to configure and consume the service to suit their unique needs.  Resource: https://www.managecast.com/veeam/ Your secondary Data Center shouldn’t contain secondary equipment!  Most backup Data Centers (DCs) are comprised of hand-me-down older equipment that is close to, or out of warranty when the primary DC is refreshed. On the surface, this approach is inexpensive, until warranty, software licensing, cooling, electrical, and human capital costs are calculated.   And when this equipment is needed, will the performance be enough? Think about three years ago and the changes that have happened since… The average age of DC servers/storage is at least 6+ years!   Run Books – Do you have one? If so, how up-to-date is it?  A Run Book is a document that outlines the steps involved in recovering from a disaster. It is a critical part of any DR plan, as it provides clear instructions for IT staff on how to restore systems and data in the event of an outage. Ensuring you have a current Run Book is vital for an effective DR plan. An up-to-date Run Book is essential for several reasons: Have you ever experienced (DR) Test Anxiety?  Sure, you studied and re-reviewed the course material, but you’re just not confident with the test you’re about to take. We’ve all been there, and let’s face it, sometimes we choke. Whether we overthink things, are ill-prepared, or the test is harder than we anticipated – we sometimes don’t do well.   The time for test anxiety need not be present during a DR event. Too many people are depending on you and your team to enable them to do their jobs.   Managecast helps you test with confidence, not anxiety. When you subscribe to our Disaster Recovery as a Service (DRaaS), the environment is available to you 7x24x365 to test your DR readiness. And when you know that it works as advertised you and your team will have the confidence to use it should the need present itself.   Step Three: Review other products in your stack that may need protection  Microsoft 365 Backup  Microsoft provides a wide array of powerful services within Microsoft 365, but a comprehensive backup of your Microsoft 365 data is not one of them. Remember, it’s your data – you control it – and it is your responsibility to protect it.  Veeam Backup for Microsoft 365 ensures the comprehensive protection of your Microsoft 365 data, including emails, files, calendars, contacts, tasks, SharePoint sites, and OneDrive files. This all-inclusive coverage guarantees that no critical data is left vulnerable to loss, accidental deletion, or security breaches.  AWS Backup  Amazon Web Services (AWS) provides a robust cloud platform for you to create and deploy apps without the burden of maintaining your own infrastructure. However, as referenced by the AWS Shared Responsibility Model, your apps and data remain your responsibility to secure and protect.  Veeam delivers native, fully automated AWS backup and disaster recovery to effortlessly protect and manage Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Relational Database Services (Amazon RDS) data.     Azure Backup  Microsoft Azure provides a reliable cloud computing platform for you to build, test, and deploy applications without the financial burdens and time commitments of maintaining your own infrastructure. However, as referenced by the Microsoft Shared Responsibility model, it’s still your data and it’s still your responsibility to protect it.  Veeam Backup for Microsoft Azure delivers enterprise‑ready Azure backup and recovery to cost‑effectively and securely protect your cloud data and easily overcome ANY data loss in minutes! With turnkey deployment directly through the Azure Marketplace and a simple, wizard‑driven UI, you can start protecting your applications and data with a comprehensive Azure backup solution.  Salesforce Backup   Salesforce is one of the most utilized CRMs (Customer Relationship Management) in the world because of its advanced account and contact

Veeam

Veeam Management Agent Not Reporting Veeam Backup Services

We have had several reports recently of Backup Servers failing to deploy the Veeam service provider management agent through the console. Even after the management agent had been installed manually, the server would show up under the discovered computers in the Veeam Service Provider Console (VSPC) but would not detect that Veeam Backup and Replication was running. If you run into a similar issue these steps may resolve the problem. Check that the Veeam Management Agent logs (C:\ProgramData\Veeam\Veeam Availability Console\Log) have error messages similar to the following: BackupServerDiscovery: System.Management.ManagementException: Access deniedBackupServerDiscovery: Backup Service (VeeamBackupSvc) is running, but select query from WMI returned NULL First, try reinstalling WMI on the backup server by running command prompt as Administrator and running the following command followed by rebooting the system: “C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.WmiServer.exe” /install The next step is to make a note of the accounts used by the Veeam Management Agent and Veeam Backup Services. Next, open the Veeam Backup and Replication console and go to the Users and Roles menu. If the Veeam Management Agent Service is running using the Local System account, verify that account still has access. The ‘BUILTIN\Administrators’ group should give that account permission by default. However, if these roles have been modified, or if MFA has been enabled, an exception will need to be made for the ‘NT AUTHORITY\SYSTEM’ service account (or other account used by the Veeam Management Agent service). Click add and add the user as well as check the box for “This is a service account (disables multi-factor authentication).” After making this change the Veeam Management Agent should now be able to report Veeam Backup and Replication details to the VSPC successfully.

Veeam

Veeam Backup “given key was not present in the dictionary” error

We have run into an issue when a job starts reporting the “The given key was not present in the dictionary” error. This seems to occur when a backup is interrupted multiple times. When this isn’t caused by the metadata being corrupted, we’ve been able to be resolve the error by removing the chain, re-importing, and re-mapping the job: 1. Connect to the tenant Veeam backup console.2. Open Home – > Backup Copy Jobs.3. Find your cloud job that processes the backup you want to modify, right-click the job and select Disable. The option can be greyed-out if the job is not scheduled to run at some particular time.4. Open the Home –> Backups –> Cloud view.5. Press and hold the [CTRL] key (please do not release it) and right-click the backup you want to modify.6. Select the Remove from configuration option.7. Open the Backup Infrastructure -> Backup Repositories view.8. In the inventory pane, find the cloud repository where the affected backup is stored, right-click it and select Rescan.During the rescan operation, in the statistics window, you will see that the backup was imported.The modified backup should appear in the Home –> Backups –> Cloud node in the tenant Veeam backup console.9. Open Home –> Backup Copy and find the cloud job associated with this backup.10. Right-click the job, select Edit, proceed to the Storage step of the wizard and select Map backup.11. Select the cloud backup from the cloud repository. Then, click OK to finish mapping.12. Save the settings and enable the job. Then run it or wait for the job to run upon schedule. If this does not resolve the issue, it may point to metadata corruption as the culprit. For further troubleshooting, please reach out to Support@Managecast.com to help get your backups running again.

Office 365 Backup, Veeam

Veeam for Microsoft 365 “Item may have a virus reported by the virus scanner plug-in” warning

Veeam will report when an “Item may have a virus reported by the virus scanner plug-in.” This warning is caused when Veeam for M365 attempts to backup an item that the built-in Microsoft 365 virus protection has flagged as possibly being infected. If you were to attempt to download the file that is reporting the malware/virus you should be met with a “This file is compromised” message: It is recommended that you get your security team involved to investigate if the item has been compromised. Additionally, removing the infected item will clear up the warning in Veeam for M365. Additionally information on Microsoft built-in virus protection can be found HERE. If the item that is reporting as potentially having a virus is downloadable and found to be a healthy file, please reach out to Support@Managecast.com and we can assist in investigating the issue.

Office 365 Backup, Veeam

Veeam Backup for Microsoft 365 “Failed to find Team mailbox owner account”

The “Failed to find Team mailbox owner account” error can be caused by the owner of the mailbox being moved, or if the owner no longer has a licensed assigned. Resolving either of these will also resolve your M365 issues. Here are the steps to resolving the cause to either issue: If the owner was removed from the mailbox: Assigned owner does not have a license: As these are two of the most common causes of the “Failed to find Team mailbox owner account” error, there may be other issues causing the error. If your issues persist, please reach out to Support@Managecast.com for assistance. Additional Microsoft information on assigning a Team mailbox owner can be found HERE, and assigning a license can be found HERE.

Veeam

Veeam Backup & Replication Virtual Machine is unavailable and will be skipped from processing

A common Veeam Backup and Replication warning we see is when a virtual machine becomes unavailable. Veeam will report the “Virtual Machine VMNAME is unavailable and will be skipped from processing” error for a few reasons. Some common reasons for the error could be: Depending on the cause of the VM becoming unavailable will determine what actions you can take to get the VM backing up. These are just a few common reasons and solutions for VMs becoming unavailable. If you would like further assistance with your backups please feel free to reach out to Support@Managecast.com.

Veeam

Veeam “Unable to connect to SMTP server because of invalid credentials or connection settings”

From time to time, there are changes and updates to your SMTP server that may adversely affect you nightly reports. Your jobs will start throwing Sending e-mail report warnings that Veeam is “Unable to connect to SMTP server because of invalid credentials or connection settings” and/or “the remote certificate is invalid according to the validation procedure.” Resolving the SMTP warning is quick and easy as long as you know where to look. Here are the quick steps to checking and re-accepting the SMTP certificate: There may be other reasons that could be interrupting the communication between your Veeam backup server and the SMTP server. If you would like further assistance please contact Support@Managecast.com.

Veeam

Veeam Backup and replication error: Job has failed unexpectedly

This error occurs when the Veeam Backup Service on the VBR abruptly stops while a backup is running.  Most commonly it is because the server is shut down or rebooted.  It could also be due to the OS crashing, a power loss event, or the Veeam Backup service crashing.  Check the Windows application and system event logs for clues to the source of the issue. It is always best practice to make sure reboots due to Windows updates or maintenance windows do not interrupt running backups; be sure to schedule updates and maintenance outside of backup windows when possible, and to temporarily disable backup jobs when it is not possible.

DRaaS, Veeam

Veeam replication disks stuck on Linux proxies

We have recently encountered issues with Veeam replication jobs where they would fail with the following errors: Error: Failed to open VDDK disk [[DATASTORENAME_0] PATH_0] ( is read-only mode – [true] ) –tr:{ –tr:VDDK error: 1 (Unknown error). Value: 0x0000000000000001 –tr:Failed to open virtual disk [DATASTORENAME_0] PATH_0 (flags: 4) –tr:Failed to execute VDDK command ‘Open’ In this scenario, the replications were using Linux Veeam virtual hot-add appliance backup proxies. When we checked the Veeam backup proxies there were hot-add snapshot disks still attached from the replicas after the jobs had completed. This was locking those disks as read-only and preventing Veeam from being able to take additional snapshots and perform the replications. Here are two possible solutions: SSHD.conf file configurations These issues can be caused by timeouts and disconnects that can be resolved by tuning the SSH configuration on the proxy. To make these adjustments modify the /etc/ssh/sshd_config file and add the following lines: You may need to restart the sshd service or restart the machine for these changes to take effect. Disabling multipathing In the Session.log log file there may be errors similar to the following: Error Failed to get guest OS path for newly attached disk [Datastore] VM_replicaNew/VM_1-000003.vmdk: there are 2 new disks with uuid 00000000-0000-0000-0000-000000000000 (System.Exception) These point to issues that can happen on linux systems where multipath is enabled and hot-add is used. These commands will disable multipathing, they will also reboot the system so do not attempt this while jobs are running: Veeam has more information on this issue here: KB4460: Failed to get guest OS path for newly attached disk there are 2 new disks with uuid (veeam.com) In our case we made both changes and our issues so far have not returned.

Scroll to Top