Corruption of backed up files > 4gb


Author
Message
dcb
dcb
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 5
Hi, it appears that when mounting a macrium reflect V6.1.1225 (Home 64bit) File & Folder Backup (backed up from and saved to an NTFS filesystem) that files larger than 4gb are split into smaller files (suffixed by ~001,~002 etc).  This is clearly a result of the FAT32 maximum 4gb file size constraint.  However, as I discovered to my dismay this appears to corrupt .zip files that have been backed up in this manner.

This cripples macrium reflect for my use as I have a great many files > 4gb and individually splitting them before archiving is not practical.  I have searched and found no adequate response from macrium to this problem.

I would expect at least one of the following solutions allowing support for large files to be available:
1 - The backup to automatically adopt the native filesystem as the backup filesystem (in my case NTFS).
2- The ability to specify NTFS as the filesystem when either creating the backup or mounting the backup.
3 - A tool provided by macrium to re-merge files split in this way.

Are any of these solutions available? I am amazed to see very few other inquiries into this bug/lack of utility as I assume it would also be a major issue for others, although I only noticed the issue by accident when looking to restore a large file.

I find reflect to be an excellent product otherwise and would be disappointed to have to abandon it. Please could you let me know a course of action. Thanks.



Richard V.
Richard V.
Most Valuable Professional
Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)Most Valuable Professional (4.1K reputation)
Group: Forum Members
Posts: 2K, Visits: 8.1K
There was some discussion previously, but not a lot.  See this thread in the old Reflect v5 forum.  If I understand Nick's replies there correctly, the large file split can occur with any file over 4 GB (not just ZIP files) but it only affects Reflect's mounting and browsing of the backup and should not prevent proper recovery of the file using Reflect's restore functionality.  Apparently it's due to the fact that File and Folder backup archives are virtual FAT32 containers.  If you're unable to recover the file intact, that certainly would be a serious issue.

Regards, Richard V. ("Arvy")
https://forum.macrium.com/uploads/images/afc5d4fe-5d25-4e25-be94-185e.png

Edited 14 April 2016 4:20 AM by Arvy
dcb
dcb
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 5
Hi Arvy, thanks for your rapid and informative reply.  As always happens, after I had posted the original comment, I did more testing and found that functionality.

I can confirm that using the Restore Backup option within Reflect restores my ZIP files without corruption.  I had previously relied so heavily on the excellent and easy "mount backup" functionality that I had never needed to use the Restore Backup function within the Reflect main application.

So, that is the "corruption" issue resolved, however the Restore Backup process is the exact opposite of the Mount Backup process when it comes to ease of use, requiring quite a number of not particularly obvious steps to get a file restored.  Additionally, when restoring a file to a "New Location" it appears that the backed up folder structure is always restored with the selected file, rather than just the file, which is inconvenient too.

So whilst my original panic attack is over and my faith in the product restored, I would still like macrium reflect to consider implementing solutions 1 or 2 above.  I'm sure this is easier said than done, but being able to mount a backup as NTFS would resolve the large files issue and keep the restore process quick and simple.

Thanks for your help. Cheers

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search