#FREENAS USB BACKUP HOW TO#
#FREENAS USB BACKUP UPDATE#
#FREENAS USB BACKUP TRIAL#

I reported the success of this workaround back to the second-level escalation support last Friday – still haven’t heard anything back.

#FREENAS USB BACKUP UPDATE#

Most important to me was to get the backup done… I may try that when I next update the backup set, but having paid for a device I shouldn’t have to be doing beta testing on it. I did not try backgrounding this command-line command with a ‘&’. I also changed the ‘q’ in the options clump -rlptDHq to a ‘v’ so that I could see which file was being backed up, where the job failed (if it did, which it didn’t) and when the job finished.

#FREENAS USB BACKUP TRIAL#

Through trial and error I discovered that simply eliminating the -timeout=30 option allowed the backup to complete without problems on the same large dataset on which it had failed before. when executing from the GUI appeared on stdout, the SSH console. The same complaint about timeouts and broken pipes that appeared in /var/log/apache2/web_error.log. I found that executing this command as written above on the command-line also caused the backup to fail. You will have to replace BackupJob and myshare with the name of the backupjob you selected and the share you selected for backup. Rsync -timeout=30 -job-name=BackupJob!_usb -rlptDHq -delete /mnt/HD/HD_a2/myshare/ /mnt/USB/USB2_c1/BackupJob/myshere When one does a ‘Synchronize’ backup, the Linux command that gets executed on the NAS embedded Linux looks like the following: Once permitted, I was able to easily develop a workaround. He also gave me permission to execute commands via the command-line over the SSH interface without voiding the warranty.

I got escalated to another second-level named Michael, who told me that Level 3 (= the developers) are working on a fix. Well, as a result of my posting to this list, and the moderator excalating this to tech support, I have some progress and a workaround. I’ll post here when I get any news from WD. Now (as I am writing this) I am working on getting a windows-8 storage space configured with 10tb of disks to see if i can cut that down to only one trip across the network.Īnd with some luck WD will fix this and in the end the backup will all happen inside the WD EX2 and not generate any external network traffic at all. And I could not get it to automatically do a backup of the EX2 so I got a third party window machine doing the backup using robocopy meaning all data makes two trips across the network. Any other functionality must run as a pluging and be installed as a virtual machine (jail) and confirured and yada yada yada. I have a FREENAS box running and now have a second copy of everything but if is a pain to add any new features to it. So I continue to search for other solutions. My opinion aside… until they have this working dependably I need a safe place for my data and 1 WD-EX2 is a single point of failure. They threw too many features on the whiteboard and sent it to production before it was finished and thououghly tested. I still contend this was not a well thought out product. Said it would probably end up being a firmwar update some day. All that happened was dump the log and then it got sent “up” to engineering. I had an encounter with the second level support tech too. If such poorly thought-through features must be included, at least provide a way to turn them off. This makes it hard to access the dashboard from any but the most simple of corporate networks. What I find completely annoying is, someone went to the extra trouble to block access to the web interface from any subnet other than the one on which the NAS is attached. I haven’t yet tried to execute the same command using -v, to get more information, because I’m afraid that some fascist customer sujpport agent will coma along and declare my warranty void.īut there clearly are some very easy-to-fix, elementary programming errors in the Linux system underying the web interface. The rsync command is executed with -q (quiet), so any chance of seeing where what went wrong is nit. There are ‘broken pipe’ errors recorded in /var/log/apache2/web_error.log. It would seem that, for a synchronizing backup, there are two commands launched, an ‘rsync’ command to actually synchronize the files between source and destination, and a du -sb, to find out how much space the backup is to take.įor some appallingly silly reason, they are launched in parallel, and if the number of files to be backed up is large, the du command never completes. I did discover the SSH interface, so I was able to look at the processes running during the backup job.

#FREENAS USB BACKUP HOW TO#

I was told how to turn on extended logging via the Web interface, but for thie particular problem, extended logging didn’t add any value. So far, I’ve only talked to second-level people who don’t seem to know much.

I have had a support case open now on this issue for TWO WEEKS.

Freenas usb backup