Author name: Managecast Technologies

Veeam

One or more bad blocks were detected and skipped

Veeam agent backups check if bad blocks are listed in the $BadClus metadata file on the NTFS file system. The One or more bad blocks were detected and skipped and skipped in the source disk error message means that there were bad blocks found. You can try to scan for and fix these bad blocks by running the following command. Replace C: with the affected drive letter. If during the above command you see errors about open files, you can run the following command. Keep in mind that this may disconnect any drives in use so ensure that there are no active tasks using the drives before running. If you continue to see these issues it may be time to replace your drives. You may want to backup and restore the drives to new disks. In that scenario, the $BadClus metadata may also be restored which can cause these error messages to continue, even though the drives have been replaced. You may need to run chkdsk again using the /B flag for all of the partitions. That will clear the $BadClus file and rescan all of the clusters. Example: Then also to run it on the recovery partition:

Veeam

Veeam Replication: Restore Point is Corrupted

The restore point is corrupted error can be caused if the replication is set to use a backup as it’s source. If the source backup is running it marks the backup files as incomplete which can cause the replication job to see the files as corrupted. Once the job is completed the restore point is changed to a “valid” state. There are typically a few different ways to fix these errors: *In both of these scenarios it may also be beneficial to set the backups window of the source backup job to disable it from running during the time the replication job is scheduled.

Office 365 Backup, Veeam

(401) Unauthorized – Veeam Backup for Microsoft 365 Errors

Veeam Backup for Microsoft 365 provides support for backing up SharePoint Online sites, but currently does not support Microsoft Loop SharePoint sites. If you are attempting to backup a Microsoft Loop SharePoint site, you may receive the “(401) Unauthorized” error. In this case, your best course of action is to exclude the Microsoft Loop site from your backup job. You can do this by modifying your backup job settings and excluding the site in question. Veeam has provided a knowledge base article with more information on this issue, which you can find at https://www.veeam.com/kb4440. In that KB article you will also find a hotfix available for Veeam Backup for Microsoft 365 v7 that will silently ignore and exclude these sites. Veeam is planning to add support for these Microsoft Loop SharePoint sites once the product becomes generally available.

Office 365 Backup, Veeam

Cannot change WebPart ExportMode to ‘All’. WebPart will be skipped

The error message “Cannot change WebPart ExportMode to ‘All’. WebPart will be skipped” indicates that a WebPart cannot be backed up due to an issue with custom scripting when using Veeam backup for Microsoft 365. To resolve this issue, you must enable the “Allow custom script” option in SharePoint, as detailed in KB article from Veeam: https://www.veeam.com/kb4091. Once enabled, you should be able to successfully back up the affected SharePoint sites. Alternatively, if you do not need to backup custom Web Parts content, edit the Organization and uncheck the option for Allow this application to enable export mode for SharePoint Web Parts.

Office 365 Backup, Veeam

Veeam for Microsoft 365: The specified Azure AD application is missing required delegated permissions

You may run into the following error when trying to perform restores from Veeam for Microsoft 365: The specified Azure AD application is missing required delegated permissions (Microsoft API: Microsoft Graph, permissions: Sites.Read.All) This issue seems to be caused by upgrading from previous versions of Veeam for Microsoft 365, specifically version 5 to version 6. The quick fix for this is simply to edit the organization in the Veeam for Microsoft 365 console, and run through the steps to Automatically register a new Azure AD application.

Veeam

Veeam Partial-site Failovers Failing During Second VM boot

As a Disaster Recovery service provider Managecast uses Veeam to provide virtual machine failover into its VMware Cloud Director (VCD) DR environment. However, recently we’ve run into an issue during partial-site failovers using Veeam and the Network Extension Appliance (NEA). When you initiate a partial-site failover using Veeam will bring up the NEA and configure a VPN tunnel and ARP proxy so that it can forward traffic to and from the powered-on replica VM in the DR environment. This typically works well, even if you select multiple VMs and perform a failover now on all of them at the same time. However, an issue can occur when you select multiple VMs and initiate a planned failover or start a failover now of multiple VMs sequentially rather than all at once. This seems to be caused by the fact that VCD reconfigures all VMs in the vApp if one of the VMs is reconfigured. Veeam configures the NEA at the start of the failover and attaches vCenter networks that VCD is not aware of. When VCD reconfigures the NEA when the second failover VM is powered on it is not aware of the vCenter network and so disconnects that network from the NEA VM, causing the failover to fail due to loss of connectivity. Veeam support confirmed this behavior and luckily have identified the issue it has been resolved in VMware Cloud Director version 10.3.2. They have provided a hotfix for this version, but it will not work for earlier versions. If you are unable to upgrade to VCD version 10.3.2, there is also a workaround. When a NEA is deployed through Veeam it is placed into the default Cloud Connect vApp in VCD. The workaround is to move the NEA into a separate vApp that does not contain any of the DR replica VMs. This way, when subsequent replica failovers start, the NEA will not be reconfigured.

General Cloud Backup

VSS Troubleshooting Guide

A VSS (Volume Shadow Copy Service) is a Windows feature that enables users to create backup copies or snapshots of data, even while it’s in use. When VSS malfunctions, it can lead to data loss or corruption. Here’s a troubleshooting guide to help you fix common VSS issues: By following these steps, you should be able to troubleshoot most VSS issues. However, if the problem persists, Managecast may be able to help. Contact us today at sales@managecast.com or 513-735-6868.

Linux, Veeam

File level recovery of OES/NSS Volumes – Veeam Agent for Linux (VAL) 

It was observed that when attempting to use Veeam B&R to deploy and manage a Veeam Agent for Linux backup job, that Veeam does not display any data within those volumes when attempting to perform a file-level recovery of that backup data. Furthermore, Veeam does NOT back up any of the data on those volumes.   To effectively back up and restore the data on an OES/NSS volume, we have found the following process to be successful. While you will not be able to utilize the Veeam Explorer/File Level Recovery wizard to perform restorations of those files, the veeamconfig commands make it quick and easy to perform file-level recovery of data on OES/NSS volumes.   Build the Backup Job with the Veeam Backup & Replication console  Job Mode  Select Server type here, and agent managed.   It is critical that we build the job in Managed by agent mode; if we select the job to be managed by the backup server, we will be unable to mount the backup later in the restoration process due to file permission restrictions.  Name the job to your desire, and select the appropriate machines to be backed up. To better understand creating protection groups for your VAL servers, please refer to Veeam’s documentation here — Creating Protection Groups – Veeam Agent Management Guide. Backup Mode For backup mode, we will select file level backup with the option checked to backup directly from the live file system. Objects For objects, this is where you will select the NSS volumes in which you desire to be backed up. For this demonstration, we will specify two directories that we need to be protected. Target For the target location for the backup, we are using the Veeam Backup & Replication server in which we are using to build the job. This is to your desire, though for centralized backups, we recommend keeping all backups on your main backup repository. Guest Processing For guest processing, we want to enable Application Aware Image Processing. This will utilize the credentials configured in the protection group for the agent’s installation. After the backup has processed, we can proceed to the next section, where we will restore files from the CLI of the machine in which we are protecting. Restoring Files and Folders on Linux protected by the Veeam Agent for Linux (VAL) The following text was excerpted from the Veeam Agent for Linux 5.0 official documentation, which can be viewed here — Restoring Files and Folders with Command Line Interface – Veeam Agent for Linux User Guide If some files and folders on your computer get lost or corrupted, you can restore them from backups. For file-level restore, you can use backups of any type: When you perform file-level restore, Veeam Agent publishes the backup content directly into the computer file system. You can browse to files and folders in the backup, restore files and folders to their initial location, copy files and folders to a new location or simply target applications to restored files and work with them as usual. With the Veeam Agent command line interface, you can restore files and folders in a more flexible way than with the use of the File Level Restore wizard. In particular, you can specify a directory in which Veeam Agent should mount the backup file content for file-level restore. You can also mount several backups to different directories to work with files and folders restored from different backups simultaneously. Before You Begin Before you begin the file-level restore process, check the following prerequisites: Step 1. Locate Backup To view a list of backups created by Veeam Agent, use the following command: In the list of backups, Veeam Agent displays information about all Veeam Agent for Linux backups stored in all backup repositories. If Veeam Agent is connected to a Veeam backup server, all Veeam Agent for Linux backups that are kept on Veeam backup repositories managed by this server also appear in this list. The –all parameter is optional. If you do not use this option, Veeam Agent displays information about backups created by the current Veeam Agent computer only. For security reasons, if you work with Veeam Agent connected to a Veeam backup server as a member of a protection group for pre-installed Veeam Agents, the veeamconfig backup list –all command will display backups created only by the current Veeam Agent computer with the current connection settings. For each backup, Veeam Agent displays the following information: Parameter Description Job name Host name of the computer on which the backup job was configured and name of the job by which the backup was created. Backup ID ID of the backup. Repository Name of the backup repository in which the backup was created. Imported backups are marked as Imported in the Repository column. Created at Date and time of the backup creation. For example: Step 2. Explore Backup Content For file-level restore, you can use backups of any type: To view detailed information about specific backup, use the following command: where: <backup_id> — ID of the backup for which you want to view detailed information. For a volume-level backup, Veeam Agent for Linux displays the following information: Parameter Description Machine name Host name of the computer on which the backup job was configured and name of the job by which the backup was created. Name Name of the volume in the backup. Device Path to the block device that represents the volume FS UUID File system ID Offset Position of the volume on the computer disk Size Size of the volume in the backup For a file-level backup, Veeam Agent for Linux displays the following information: Parameter Description Machine name Host name of the machine on which the backup job is configured and the name of the job. Backed up Backup scope for the file-level backup job For example: Step 3: Mount Backup To mount a backup for file-level restore, use the following command: where: <backup_id> — ID of the backup that you want to

General Cloud Backup

World Backup Day is March 31st

World Backup Day is coming up quickly this year. WBD 2023 takes place on March 31st, the day before April Fool’s Day, for a good reason: Don’t be a fool backup your data! What is World Backup Day? World Backup Day is the day to bring attention to whether your data, most likely your most critical and vital business asset, is well protected. World Backup Day originated in 2005 as World Backup month, but was changed to World Backup Day in 2011 on March 31st as a reference to April Fool’s Day. Why Should You Backup Your Data? If you had to choose between all of the money in the bank or all of the data that your organization has, what would you choose? In some cases, choosing all the money would make sense, but in most cases, data is what helps the company stay going and keep making money for years to come. Backing up your data is important for many reasons, including enabling your organization to go on as usual in the event of a disaster. Disasters can happen anywhere: from a critical server failing, to natural disasters like flooding and fires, to man-made disasters such as theft, sabotage, and chemical spills. Additionally, ransomware attacks are on the rise globally and are evolving to be more complex. Data backup is also important in an event like a pandemic, which we are currently experiencing. In this case, suffering an additional disaster such as fire, floods, tornadoes or ransomware could cripple an entire business. Supply chains are stressed, getting replacement equipment may be difficult and more problems would arise. Plus, many workers are going remote since the start of 2020, and you need to be sure their data is protected. Now more than ever, we have seen why a good disaster recovery and business continuity plan is imperative. What Can I Do to Protect My Data? We encourage you to think about all of the data you need to protect, and whether or not you are meeting best practices. Are you following the simple 3-2-1 rule of backup, which states you should have 3 copies of your data, on 2 different media with at least one offsite? In recognition of World Backup Day, please consider how protected your data really is. We are here to help improve your data protection methods.  Feel free to contact us here, send me an email at ngolden@managecast.com, or give me a call at 513-735-6868 Ext. 4002 to request more information. Join us in taking the pledge here: http://www.worldbackupday.com/en/

Scroll to Top