AOMEI Cyber Backup
Fixed: FLR and Instant Recovery Fail with 24 TB Vbk
When the FLR and instant recovery failed with 24 TB Vbk, you may failed recovery operations and inability to store or process large backups, after you fix this problem the instant recovery progress will go smoothly.
By Amelia / Updated on December 3, 2024
FLR and Instant Recovery fail with 24 TB vbk
I hope I don’t spam this forum too much, but I don’t run out of problems with a very large VM (24 TB). Regarding Veeam 7, Patch 3, build 839. I managed to backup the VM after some trouble, but now I can’t get a FLR or Instant Recovery to work. The error I get is always: Poweron failed: the destination file system does not support large files. An Instant Recovery job starts up all-right, presents the VM correctly, but in vSphere (using latest 5.5 U1) I get the same error, as soon as I try to power on the VM. In the inventory the VM only uses the PowerNFS store. The underlying filesystem of the PowerNFS store is the same as that hosting the 24 TB vbk file. NFS cluster size: 32K, Windows 8.
- Question from Veeam R&D Forums
The FLR and Instant Recovery fail with 24 TB ABK issue in Veeam may cause Power on failed: the destination file system does not support large files. Such an error indicates that the file system on which the Instant Recovery or FLR mount point was created does not support files larger than 4GB or other size limitations specified by the target file system. This is a common problem when using file systems such as FAT32 or poorly configured NTFS/ReFS/XFS volumes. This next article will talk about what causes the error and the solution.
Solutions to FLR and Instant Recovery Fail with 24 TB Vbk
In this next section, you can learn the reason for the FLR and Instant Recovery fail with 24 TB vbk issue, while you follow the below steps to solve the problem which can help you to solve the issue successfully.
1. Identify the Destination File System
Confirm the file system of the destination drive, for example, where the VM disks or FLR temporary mount is being created.
▶On Windows: You can open a Command Prompt or PowerShell and run the following command, this will display the file system type.
▶On Linux you can use:
The following table lists common file system limitations to help you have a better understanding.
|
File System |
Max File Size |
|
FAT 32 |
4 GB |
|
NTFS |
~16 TB |
|
ReFS |
35 PB |
|
ext4 |
16 TB (with 64-bit enabled) |
|
XFS |
~8 EB |
2. Adjust the Destination for the Operation
Instant Recovery
◆Ensure the datastore or mount location supports large files:
- For VMware, ensure the ESXi datastore uses VMF5 or VMFS6 (not older VMFS versions).
- For Hyper-V, ensure the destination volume uses NTFS or ReFS.
◆Configure the Instant Recovery cache folder or temporary files to use a compatible file system: Go to Backup Infrastructure > Backup Repositories in the Veeam Console. Then edit the repository and set the correct Advanced Settings for storage.
File-Level Recovery (FLR)
✦Use a Destination Supporting Large Files: Re-direct the mounted recovery location to a volume formatted with NTFS, ReFS, ext4 (64-bit), or XFS.
✦Change FLR Temporary Folder
- Veeam uses a temporary folder for mounting the backup. Adjust this folder in the Veeam configuration to point to a drive with a compatible file system:
- Open the Veeam console and navigate to General Options > Advanced > FLR Helper Disk Mount Point. And set this to a volume with NTFS, ReFS, or a similar modern file system.
AOMEI Cyber Backup - The Efficient Instant Recovery Solution
AOMEI Cyber Backup provides you with an all-inclusive, simple, efficient, and free instant recovery solution that can help you recover your data in a short period and migrate it to production after instant recovery. It allows IT teams to quickly recover entire virtual machines, reduce Recovery Time Objectives (RTO), and maintain operational continuity.
👉Centralized Management: It can manage all your VMware virtual machines from a single intuitive dashboard.
👉Instant VM Recovery: You can quickly restore an entire virtual machine to a running state, reducing downtime and avoiding losses.
👉Automate Schedule Backups: You can set up VMware backup schedules to ensure VMs are protected without manual intervention.
👉Agentless Backup for VMs: It can create full, standalone image-level virtual machine backups of VMware ESXi virtual machines.
Step 1. Navigate to Task > Instant Recovery > + New Instant Recovery > Restore from task to configure the instant recovery.
Step 2. In the Source section, choose the virtual machine and backup version.
Step 3. In the Restore to section, choose the target device.
Step 4. Set the hardware settings for the new virtual machine, including CPU quantity, CPU Cores, and memory size.
Step 5. Click Start Restore to start the instant recovery.
Step 6. Click Start Migration to restore the virtual machine to the production environment after the production environment resumes normal.
Conclusion
The solution provided in this article can help you smoothly solve the FLR and Instant Recovery fail with 24 TB Vbk problem caused by the destination file system does not support large files, to ensure that timely recovery is carried out smoothly.
