Running out of space on a Veeam Hardened Repository (VHR)? There is a safe, controlled way to manually delete immutable backups using the VHR ISO in Live System mode. Check out our latest step-by-step guide.
If your Hardened Repository is getting out of space, you may need to quickly delete backups from the Veeam ISO Hardened Repository to avoid backup failures.
To perform backup deletion we must boot the server in Live System mode using the Veeam ISO file.
In the example below, the Veeam repository is almost full with only 33 GB of free space remaining and must be freed up to prevent backup job failures.

Boot the server in Live System mode
If the Veeam ISO Hardened Repository is configured according to best practices, you should enable iDRAC, iLO, or similar remote management to access the server console.
Download the Veeam ISO Hardened Repository from the Veeam website.

Ensure the downloaded .ISO file is accessible from the machine used to connect to the iDRAC/iLO of the Hardened Repository server.
Access the server console and map the downloaded .ISO file to the Virtual CD/DVD.

Configure the server to boot from the Virtual CD/DVD/ISO.

To ensure the server boots in Live System mode, the Veeam ISO Hardened Repository must be rebooted. Enter the credentials to login to the Hardened Repository console.

Select the Reboot option and press Enter.

Select Yes and press Enter. The server will reboot.

When the server boots from the mapped Veeam ISO, choose the Live System option.

Delete a backup from the Veeam ISO Hardened Repository
Login with the default credentials and change the password. The new password must comply with DISA STIG requirements. This password change only affects the Live System session and does not alter the production repository password.
default username: vhradmin
default password: vhradmin

Enter the following command to elevate privileges. Enter the password created earlier.
# sudo -i

Navigate to the vhradmin home directory and list available scripts.
# cd /home/vhradmin # ll

Mount the repository using the provided script.
# ./mount_datavol.sh

Go to the backups folder and list its contents.
# cd /mnt/veeam.repository01/backups/ # ll

Navigate to the specific backup folder and list its files.
# cd Backup\ SERVICE\ VMs/ # ll

Check if backup files are immutable. The i flag indicates immutability.
# lsattr

Remove the immutability attribute from the files you wish to delete. In this example, all files beginning with w22 will be processed.
# chattr -i w22*
![]()
Verify that the immutable attribute has been removed.
# lsattr

Delete the backup files and confirm removal. Be careful because this action permanently deletes backup files.
# rm -f w22* # ll

Reboot the repository to restore the original configuration.
# reboot
![]()
Update repository information in Veeam
To make Veeam Backup & Replication aware of the new space, in the Veeam console access the Backup Infrastructure area and select Repositories. Right click the processed repository and select Rescan to collect the changes.
To make Veeam Backup & Replication aware of the freed space, in the Veeam console go to Backup Infrastructure > Repositories. Right-click the processed repository and select Rescan.

Once the rescan completes, click Close to close the window.

After rescanning, the available free space should reflect the deletion. In the example, free space increased from 33 GB to 124 GB with a gain of 91 GB.

Remove missing restore points
After deleting backups from the repository, verify that the backup chain does not contain missing restore points.
From the Home area, go to Backups > Disk. Right click the just processed Backup Job and select Properties.

If the backup chain is intact and backups are recoverable, no further action is needed. If broken restore points are present, right-click the missing point and select option Forget > All unavailable backups.

By following this procedure, you free up space on the Veeam ISO Hardened Repository, avoiding backup failures due to insufficient storage.
from StarWind Blog https://ift.tt/uGEAyrR
via IFTTT
No comments:
Post a Comment