NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Backup to USB drive fails with unknown error
My ReadyNAS is very full up, and I'm trying to copy stuff of it without any success. First, I was having trouble with those stupid DS_Store files, so I decided to compress the files in order to m...
Thanks Brian L.
The file system of the USB drive is FAT32. The ReadyNAS firmware is 5.3.8, and it's a 4-bay ReadyNAS nv+ v2. (Apparently I can update it to 5.3.11, but I don't know if that will make any difference to this issue?)
Sometimes, it just truncates a file that's bigger than 4.29GB (so this appears to be the limit for this USB drive), and carries on, but at other times, it stops. I haven't figured out what the difference is.
What I'd really like to be able to do, and I've no idea if this is possible, is to say to the backup: okay, backup everything you can, and give me a list of the things you couldn't (I imagine because of characters in filenames, or file size), and then I can do them manually later.
Also, I've got another USB drive, which I know for a fact has over 600GB spare on it, but when I connect it up to either of my ReadyNASes (I also have a v1, which I'm actually copying this data to, via the USB drive), they say it has no free space. It would be useful if I could use this drive as well in this process. According to Disk Utility, its file system is "Mac OS Extended (Journaled)".
But what would be really, really useful, is if the backup could actually tell me what the error is, rather than just "unknown", and the system log doesn't SEEM to have any more detail. It just says "Please see log."!!
Many thanks.
colmosiris wrote:
The file system of the USB drive is FAT32.
Sometimes, it just truncates a file that's bigger than 4.29GB (so this appears to be the limit for this USB drive),
That's not a problem with the USB drive - the problem is the FAT32 formatting. If you used NTFS, then you could write the larger files.
colmosiris wrote:
... and carries on, but at other times, it stops. I haven't figured out what the difference is.
Have you tested the USB drive? Possibly writes are actually failing.
Thanks Stephen. No, unfortunately I can't use NTFS, because I can't format those on my Mac. Anyway, I can't format this drive as anything other than what it is, as it has data on it.
There's nothing wrong with the USB drive, or at least Disk Utility says so, anyway. (It's the same drive I was copying stuff onto from the other NAS box last week.) Any thoughts on the other USB drive with 600+GB available on it?
My main question, apart from what use is an 'unknown error', is, is there a way I can make the backup process bypass the errors, and just make a note of them, rather than stopping? It's extremely time-consuming this way!
And also, is there a way of copying directly form NAS to NAS, without using an intermediary drive, and without using Rsync, which AFAICT, wants to incrementally backup the whole volume? (Unless that's not true, in which case, how do I do it, please?)
colmosiris wrote:
And also, is there a way of copying directly form NAS to NAS, without using an intermediary drive, and without using Rsync, which AFAICT, wants to incrementally backup the whole volume? (Unless that's not true, in which case, how do I do it, please?)
You can backup up NAS-to-NAS with NFS, CIFS, or rsync. And you can back up individual shares with any of these protocols. I use incremental rsync to back up each share of my pro-6 daily to various backup ReadyNAS.
If the protocols are enabled on the v2, you can configure the backup jobs to run on the v1 (or vice versa, but I am more familar with the v1). What is confusing you on the backup job configuration?
colmosiris wrote:
Thanks Stephen. No, unfortunately I can't use NTFS, because I can't format those on my Mac.
Well, the format is the issue with the file size. There are also character limits with FAT32 that might be getting in your way. There are inexpensive ways to format as NTFS on the mac (paragon being one). If you are willing to get paragon, you could also go with ext formatting, which has faster copying than NTFS (especially on the v1).
Or you can copy the data over the network to a USB drive connected to the mac. If you have wired ethernet, that is the fastest way to do it. And you can format the drive to anything the mac supports.
Thanks Stephen.
You can backup up NAS-to-NAS with NFS, CIFS, or rsync. And you can back up individual shares with any of these protocols. I use incremental rsync to back up each share of my pro-6 daily to various backup ReadyNAS.If the protocols are enabled on the v2, you can configure the backup jobs to run on the v1 (or vice versa, but I am more familar with the v1). What is confusing you on the backup job configuration?
I've set up Rsync on both boxes. I couldn't use CIFS, because it doesn't appear to be available on the v2.
I'm doing this on the v2, rather than the v1, because although I much prefer the v1's GUI, it doesn't allow me to select paths in the backup. If I click 'Browse', it gives me an empty window which I can't close without rebooting the browser. This means having to dump everything on the top level, which is very messy.
The two boxes are connected to, and by, a Netgear Portsafe 8 Port Gigabit Switch, model GS108. I could connect the two NAS boxes directly, if I need to.
When I set up the Backup Job, and tested the connection, I got the message 'Cannot connect to host.', with the code 7077010011. These are the settings I used:
BACKUP SOURCE [this is the v2, which is called Media2]
Type: share
Name: share: films
Host: [empty, and unclickable]
Path: FILMS/Other1
Log In:
Password:
BACKUP DESTINATION [this is the v1, which is called Media1]
Type: remote
Name: remote: Rsync Server
Host: Media1
Path: FILMSNEW/FINALBACKUPS [with greyed out Browse button, but at least I can type in the Path field, which I can't do on the v1]
Login: admin
Password: ********
This is what I get when I try the backup:
--------------------------------------------------------------------------------
FULL Backup started. Wed Mar 9 14:25:11 GMT 2016
Job: FINALBACKUP
Protocol: rsync
Source: [Films]/FILMS/Other1
Destination: Media1::FILMSNEW/FINALBACKUPS
rsync: getaddrinfo: Media1 873: Name or service not known
rsync error: error in socket IO (code 10) at clientserver.c(122) [sender=3.0.9]
Backup failed. Wed Mar 9 14:25:12 GMT 2016.
Reason for failure:
Error encountered copying data from source path /Films/FILMS/Other1 ==> Media1::FILMSNEW/FINALBACKUPS due to unknown reason. Please see log.Thanks for the info about FAT and NTFS etc.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
