Print

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

[Jack Ryan]

Background:

I use some DNS-325s as file servers and others are used as backups for the file servers. The backups are programmed to perform an incremental backup of a particular server at a particular time. This has been operating fine for some years. As the devices are "on line", I don't update the firmware unless there is a need.

What I did:
The need finally arose to use the latest firmware so I chose one of the backup devices and upgraded it from 1.01 to 1.03. All looked good and IE10 still required compatibility mode as it did with the previous version.

The Problem:
This morning I find that the programmed backup failed. As usual, there is no message in the log giving further information. I attempted to manually start the backup - it failed again with the sum total of the diagnostics information as "failed".

I cannot see what the problem is. Both the source and destination directories are present and accessible. No other changes have occurred.

Any suggestions?
Thanks

[Jack Ryan]

I have some additional information:

The backup configuration is:
Category = Lan Backup
Login Method = Anonymous
Type = File

The problem appears to be in the specification of the source. I deleted the original configuration and entered it again. I have always entered the source in the form:

//Nas-Server/Volume_1/

However, with firmware version 1.03, I get the error message:

The URL format is not correct, the correct format is : Volume_1/Test or \\192.168.0.32\Volume_1\Test\test.txt . Please try again.

And the source is changed to:

Volume_1//Nas-Server/Volume_1/

Which is incorrect (and invalid). Has version 1.03 of the firmware forgotten how to perform a DNS lookup?

Does everyone else have this problem?

Jack

[Jack Ryan]

Firstly, used the wrong slashes in my last post but I have confirmed that:
\\Nas-Server\Volume_1\ fails and
\\192.168.1.205\Volume_1\ succeeds

So (local) DNS lookup seems to be broken. It worked fine in 1.01 and continues to work on the remaining devices on the network.

Jack

[HomeCloud]

I had what I would describe as a similar problem after upgrading from 1.01 to 1.03. My backup (from one NAS to another and from a PC to NAS) was working as anonymous. Then I upgraded to 1.03 and anonymous no longer 'succeeded'. So I went with the user/pw to the NAS and it was again successful.

The other thing I had to do was delete all the scheduled backups that had failed and reconfigure. Now it works.

Hope it helps

[Jack Ryan]

Hi, Thanks for the response.

I deleted the original configuration when I was trying to work out what would work. Neither "Account" nor "Anonymous" worked if I used a domain name that required DNS lookup. In other words a URL of:

\\Nas-server\Volume_1

always fails in 1.03. Only the IP form

\\192.168.1.205\Volume_1\

will work.

In version 1.01 of the firmware, both forms work and the remaining DNS-325 and DNS-320 devices on the same network all work using the domain name.

I believe this is a bug in version 1.03 of the firmware.

What do you have in the URL field?
What response do you get if you press the Test button?

Jack

[HomeCloud]

I've always used the ip address so my results were consistent with yours the the IP addressing is successful (though as mentioned anonymous no longer succeeded in 1.03). 

[Jack Ryan]

Thanks for that.

I am still using anonymous transfers and they work for me - it is the backup source URL that is the problem. It works if I use the IP address but I can no longer move the drives from one subnet to another without adjusting the IP address in the backup configuration. It is just another potential source of error.

A question for the moderator; do I need to post somewhere else to make sure the bug report is logged?

Jack