When backing up on XFS repositories for example with Veeam Backup&Replication, XFS feature reflink can be used for Fast Cloning. I wrote already a post about checking Microsoft ReFS space savings. Now I want to show some basics to check XFS savings too.
In this post I share a small PowerShell/PowerCLI script to check if VMs get backed up by Veeam B&R. If you do not run VeeamONE, it can be challenging to check if every VM that should be backed up, is really backed up. For checking this, this script should be helpful.
These days I had to troubleshoot poor VMware vSphere SAN transport mode performance during backup with Veeam. Before SAN mode, NDB transport mode was used. NBD outperformed SAN mode totally!
This post shows three ways to analyse ReFS space savings with Block cloning. And because Veeam Backup&Replication uses this feature massively, I use this backup solution as an example here.
Recently I had to troubleshoot a Veeam Backup & Replication (B&R) problem. There the question popped up which are the running Veeam jobs at point or period of time. The GUI is not a big help to answer this question. Therefore I wrote a small script that show these jobs.
Recently I had a strange behavior when creating 3PAR snapshots in Veeam Backup&Replication after a site-failover (Peer-Persistence) occurred. Snapshot-jobs stop with error, backup-jobs using 3PAR integrated snapshots jobs are still running because they failed over to NBD. Snapshot-jobs were configured using secondary 3PAR for snapshots too – see more information here. Management console showed the following error for snapshot-jobs: VM VM name does not meet […]
An interesting question arose some time ago. A customer changed permissions of files on a Windows file-server VM. Changes were replicated using DFS. So far so good, but the amount of data that was processed at next incremental backup of target VM was even more than a full backup. Because incremental backup is based on VMware Changed Block Tracking (CBT) feature, it was suddenly interesting […]
In a 3PAR Peer Persistence configuration volumes are synchronously replicated between two 3PAR arrays. For each volume one array acts as primary or source array. This array exports the volume for read/write. The other array acts as secondary or target for replication. For performance reasons it could be an advantage when backup reads data from target array. This is easily possible with Veeam B&R 9.5.
Here is a small and simple PowerShell script to list VMs, their last successful backup and the days gone since then.