Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[anotheruser]

Hi,

Am currently having a DNS323 with 2 x 500 GB WD Green Drives (Mirror mode).

I have setup a couple of different shares for use in the network. Both share1 and share2 are accessible thru the LAN.

share1 is not password protected, share2 is password protected.

Share1 has about 2-3GB of data (about 3000 files), share2 has about 20 MB of data (about 20 files).

I have backups scheduled as follows :

\\nas\Volume_1\Share2    Volume_1/Backup/   (Daily)     1 PM
\\nas\Volume_1\Share1    Volume_1/Backup/   (Daily)     2 PM

I also have weekly backups running in the evenings as such :

\\nas\Volume_1\Share2     Volume_1/Backup/Friday/   (Weekly) 7PM
\\nas\Volume_1\Share1     Volume_1/Backup/Friday/   (Weekly) 8PM

The days change to accomadate the actual day the backup is done.
There are a total of 2 daily and 12 weekly (Monday to Saturday) backups set in the interface.

Account settings are given, and tested to make sure they work (using the test button).
There is time given in between both backups so that the smaller backup (just 20 MB) has ample time to complete before the larger backup takes place.

I have noticed many times that backups seem to work sporadically, and once one fails, that backup seems to fail forever until I come back and set it up again in the interface. I have also noticed that backups seems to take hours (even for the 20MB share).

Sometimes I do a forced backup, and after waiting for a day or longer, I kill it, as it does not seem to finish at all (the icon in the schedule list shows it still running).

This is used in a small office environment with about 5 users.

What can I do to make it work?

This is running the 1.07 firmware.

Thanks.

[gunrunnerjohn]

I pretty much gave up on the NAS backup scheduler and I use a PC program for any backup operations.

[JavaLawyer]

I am currently using multiple scheduled incremental backups on the DNS-343 (I'm assuming here that the 323 and 343 are based on the same code).  From what I've experienced and have read on these forums, the backup software has trouble handling file and folder names with special characters and that these can cause backups to fail.  After renaming all rogue file names on my DNS, the scheduled backups started working without a problem. 

There are other issues as well, but this was one of my major sticking points.

[anotheruser]

After spending a few hours and doing some research, I finally installed the telnet funplug and found that a bunch of files were owned by account "nobody" and the other accounts were not given access at all.

I had to do a chmod 777 on everything to get back full access.

I hope this will fix the problem of the multi-hour "hanged backups".

I only wish there was a way to secure the root account during telnet access, as passwd does not seem to create / ask for credentials when doing a telnet login.

[gunrunnerjohn]

I think the ticket here is to install a different telnet client that has password control.  I agree, being able to simply telnet directly into the box with no password is a bit on the dangerous side.

[anotheruser]

After not checking since the last post here, today I find that my schedule list is wiped clean.



Back to setting up everything again.