NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Backup fails after upgrade to 6.6.1
Hi,
I have been running a 2 disk 2TB mirror in xraid readynas with full backup to external hdd once a week without any issues.
I have about 228GB of data and 30GB of snapshot. not a lot.
After upgrading to version 6.1.1 the backup terminates with a disk full error. Its a 2TB external HDD connected to the nas via the front usb.
The disk was in ntfs and i have tried reformating in NTFS, FAT, ext3 and ext4 but still no sucess the backups fails with a disk full error message. i tried formating the external hdd on a PC with a 4k allocation unit size in FAT but the NAS does not recognise the disk.
I also recreated the backup function (with the option delete all files on the disk) no sucess.
any idea.
regards,
Frederic
- The point is not "how many snapshots" but "is it transferring snapshots". Did you try StephenB suggestions?
Snapshots are at block level, understand that they contain only the blocks that are different from a reference, which makes them very efficient is used space.
Traditional backups, such as what you're using, occurs at file level. It doesn't have a clue that it's a snapshot, it only considers the files it sees - the full files - the files reconstructed with the blocks in the snapshot merged with the reference(s) - the files like you would see if you were to browse the share.
If the backup tries to transfer a single snapshot, it would require the whole file size, two snapshots, twice. If you have a share with two empty snapshots and transfer the data and the snapshots, it requires THREE times the space.
In FAT, there are other limitations, like the maximum size of a file, which is much lower than the maximum file size on BTRFS. If you were to try transfer a file too big for FAT, it would fail.
12 Replies
Replies have been turned off for this discussion
already disable
Did you try turning off "snapshot access" on all the shares? This won't delete the snapshots, but it should ensure that you aren't backing them up.
Note that the 30 GB used for snapshots is the incremental space needed to store the snapshot. When you back up a snapshot to an external drive, it will take about the same amount of space as the original share. This adds up quickly.
- The point is not "how many snapshots" but "is it transferring snapshots". Did you try StephenB suggestions?
Snapshots are at block level, understand that they contain only the blocks that are different from a reference, which makes them very efficient is used space.
Traditional backups, such as what you're using, occurs at file level. It doesn't have a clue that it's a snapshot, it only considers the files it sees - the full files - the files reconstructed with the blocks in the snapshot merged with the reference(s) - the files like you would see if you were to browse the share.
If the backup tries to transfer a single snapshot, it would require the whole file size, two snapshots, twice. If you have a share with two empty snapshots and transfer the data and the snapshots, it requires THREE times the space.
In FAT, there are other limitations, like the maximum size of a file, which is much lower than the maximum file size on BTRFS. If you were to try transfer a file too big for FAT, it would fail.
jak0lantash wrote:
The point is not "how many snapshots" but "is it transferring snapshots". Did you try StephenB suggestions?
Snapshots are at block level, understand that they contain only the blocks that are different from a reference, which makes them very efficient is used space.
Traditional backups, such as what you're using, occurs at file level. It doesn't have a clue that it's a snapshot, it only considers the files it sees - the full files - the files reconstructed with the blocks in the snapshot merged with the reference(s) - the files like you would see if you were to browse the share.
If the backup tries to transfer a single snapshot, it would require the whole file size, two snapshots, twice. If you have a share with two empty snapshots and transfer the data and the snapshots, it requires THREE times the space.
In FAT, there are other limitations, like the maximum size of a file, which is much lower than the maximum file size on BTRFS. If you were to try transfer a file too big for FAT, it would fail.it was indeed the snapshot ot a home user folder that was the culprit.
thanks for the help.
regards,
Frederic
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
