Veeam merging backup files stuck


  • Hyper-V VM Stuck In Backing Up… State
  • Veeam Backup Copy Job – Questions and Answers
  • Knowledge Base
  • Veeam Replication Job Stuck at 99%
  • Remove Lingering Backup Checkpoints from a Hyper-V Virtual Machine
  • Removing Backup Checkpoint in Hyper-V That Has No Delete Option
  • Hyper-V VM Stuck In Backing Up… State

    One day something went wrong with the server backup and I noticed a checkpoint that I did not create. It was created by a third-party application that I used to backup checkpoints. When I right-clicked the checkpoint to delete it, I noticed that the option Delete Checkpoint was not available.

    Notice that the options to Delete Checkpoint and Delete Checkpoint Subtree are missing in the above screenshot. If you run into this situation, first try the following techniques. Right-click the host server name in the Hyper-V Manager in the left-hand pane and select Refresh. Close and re-open the Hyper-V Manager. Highlight the checkpoint and use the Delete key on the keyboard. If none of these tips help, then use the PowerShell to get rid of unwanted checkpoint s.

    This applies to any checkpoint that you want to delete. The script should work on Hyper-V installed on any operating system, e. Start PowerShell on the computer where the virtual machine is located. Type the following command and press Enter.

    As I mentioned earlier, the checkpoint used to be called snapshot in Hyper-V before Microsoft changed its name. Make sure you use the name of the VM, not the name of the checkpoint. The following command will work if you have only one checkpoint that needs to be deleted. In other words, either one of the following commands should work. Depending on the size of the virtual hard disk, the merge process may take some time so be patient.

    If you need to export the virtual machine, you will be able to proceed once the merge is complete.

    Veeam Backup Copy Job – Questions and Answers

    Another huge factor, often overlooked, is the stripe size of the underlying storage. This is because they have to be a general purpose solution able to manage at the same time different workloads: datastore for VMware volumes, NFS or SMB shares, archive volumes. Since in many situations the different volumes are still carved out from the same RAID pool, this pool has a unique stripe size value. As you can read however in the aforementioned whitepaper, Veeam uses a different and specific block value.

    Again, as explained in the whitepaper, thanks to compression these values are reduced to half when the block lands into the repository. So, we can assume the default block size written in the repository is going to be KB. With this value in mind, we can do some simulations using an online calculator. Using the default 64KB, we get: Bandwidth is going to be Say you have to transform 1 TB of data, you need to move 2TB of blocks.

    At that speed, it will take 20,6 hours! If you change only the storage stripe size to for example KB, the new bandwidth will become 40,51, three times the previous one! This means the same backup job will last 6,86 hours. Compare it with the previous result of 20,6 hours, and you can immediately understand the importance of configuring the right stripe size on your Veeam repository. Also, the RAID level is important.

    You can see again in the tool the reason. But again, remember to carefully evaluate these configurations options when you design a new storage for Veeam backups. Share this:.

    Knowledge Base

    Right-click the host server name in the Hyper-V Manager in the left-hand pane and select Refresh. Close and re-open the Hyper-V Manager. Highlight the checkpoint and use the Delete key on the keyboard. If none of these tips help, then use the PowerShell to get rid of unwanted checkpoint s. This applies to any checkpoint that you want to delete.

    Veeam Replication Job Stuck at 99%

    The script should work on Hyper-V installed on any operating system, e. As you can read however in the aforementioned whitepaper, Veeam uses a different and specific block value.

    Again, as explained in the whitepaper, thanks to compression these values are reduced to half when the block lands into the repository. So, we can assume the default block size written in the repository is going to be KB.

    With this value in mind, we can do some simulations using an online calculator.

    Remove Lingering Backup Checkpoints from a Hyper-V Virtual Machine

    Using the default 64KB, we get: Bandwidth is going to be You can use encrypted VM backup files as a source for Backup copy jobs, if the backup copy job is the created on the same backup server as the primary backup job.

    You can choose to encrypt the backup copy files at rest in the remote repository, the source backups do not need to be encrypted. If there are concerns around air-gapping the data in the target repository, consider sending the data to a cloud connect service provider, as the cloud repository will not be visible at all from the tenant network. Cloud Connect for Enterprise can also be used, if there is desire to provide service provider side of cloud connect within an organization.

    How can I use the backup copy job to followwithout maintaining the target infrastructure?

    Removing Backup Checkpoint in Hyper-V That Has No Delete Option

    Contact a Veeam Cloud Connect service provider and allow them to provide the offsite location for you to use. We encourage the use of Backup Copy Jobs to Cloud repositories, as they decrease the impact on the production environment.

    You can choose to encrypt the data in the Cloud repository. From a Service provider point of view, it is a good idea to keep in mind that the tenants chose if they want to encrypt the data in the cloud repository, and deduplicating storage cannot will not provide much deduplication of encrypted data. Yes, note that all backup copy jobs are configured in the Veeam Backup server. The agent license needs to be installed in this backup server.

    Mapping or seeding is not currently available for agent backup copy jobs. Does the source backup job affect the backup copy job? Backup copy jobs can pull data from any VM backup, forward, reverse or forward forever backup files.

    In the target repository, there will either be forward forever or forward incremental chain.


    thoughts on “Veeam merging backup files stuck

    Leave a Reply

    Your email address will not be published. Required fields are marked *