Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: NAS->NAS backup 'Source path is invalid'
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-09-08
03:17 AM
2012-09-08
03:17 AM
NAS->NAS backup 'Source path is invalid'
In the past I have used the backup feature to move downloaded torrent files from the downloads folder to their relevant folder (takes a fraction of the time it would through a computer), however when I select the folder containing the downloaded files (Share: downloads, Path /BitTorrent/Folder) as the source in the 'add new backup job' tab I get the message:
'ReadyNAS backup source path is invalid. Please check the path and make any necessary corrections.'
What am I doing incorrectly?
I am using a ReadyNAS Duo v1 with RAIDiator 4.1.9 [1.00a043] with 2 drives in RAID level 0. The source and destination folder are on the same drive.
'ReadyNAS backup source path is invalid. Please check the path and make any necessary corrections.'
What am I doing incorrectly?
I am using a ReadyNAS Duo v1 with RAIDiator 4.1.9 [1.00a043] with 2 drives in RAID level 0. The source and destination folder are on the same drive.
Message 1 of 3
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-09-08
10:14 AM
2012-09-08
10:14 AM
Re: NAS->NAS backup 'Source path is invalid'
I believe this is a bug introduced in the new firmware. I currently setting up one for a friend who is using a ver1 model Duo with 4.1.7 firmware. I have been slow to update hers because I was using betas and updating and noticing bugs every now and then.
Anywho, I was just setting up some backups similar to mine over a VPN connection and noticed some differences in the way the backup creation was handled...
Case1 Observation
When you are selecting the path using the browse button on version 4.1.7, the returned value is: "FolderName/"
Case2 Observation
When you are selecting the path using the browse button on version 4.1.9, the returned value is: "/FolderName"
The honest truth is that in the past, my backups never had a "/" at the beginning or at the end of the file string path. Although, I do not think it hurts to have it at the end, I just never put it in. My backups never failed either...
Case1 Result
The result of case one would be "BackupSource/FolderName/" ... backed up to ... "BackupDestination/FolderName/".
Case2 Result
The result of case one would be "BackupSource//FolderName/" ... backed up to ... "BackupDestination//FolderName/".
Conclusion
Case1 would actually work and have not problems... Case2 would fail due to the "//". The nas is looking for a "blank-named" folder in-between the source and destination. I know this is the case with you because you said your (Share: downloads, Path /BitTorrent/Folder). The string that is created by your submition is: "[downloads]//BitTorrent/Folder". You can verify this by looking at the list of all of your created backups.
Solution
Edit the backup and remove the preceeding "/" and save it. as I said before, my jobs have worked fine without the use of a preceeding or ending "/".
Also... I assume we are similar situation when it comes to backing up the files from the. I actually use the Remote: Rsync Server as the backup destination. Host, ReadyNAS local IP address, Path: "ShareName/FolderName", and Login/Password for local Rsync services. This way, it would sync the files... Not just backup duplicate files and such. I later set another backup job to clean out the bit torrent destination folder whenever it got too full.
Anywho, I was just setting up some backups similar to mine over a VPN connection and noticed some differences in the way the backup creation was handled...
Case1 Observation
When you are selecting the path using the browse button on version 4.1.7, the returned value is: "FolderName/"
Case2 Observation
When you are selecting the path using the browse button on version 4.1.9, the returned value is: "/FolderName"
The honest truth is that in the past, my backups never had a "/" at the beginning or at the end of the file string path. Although, I do not think it hurts to have it at the end, I just never put it in. My backups never failed either...
Case1 Result
The result of case one would be "BackupSource/FolderName/" ... backed up to ... "BackupDestination/FolderName/".
Case2 Result
The result of case one would be "BackupSource//FolderName/" ... backed up to ... "BackupDestination//FolderName/".
Conclusion
Case1 would actually work and have not problems... Case2 would fail due to the "//". The nas is looking for a "blank-named" folder in-between the source and destination. I know this is the case with you because you said your (Share: downloads, Path /BitTorrent/Folder). The string that is created by your submition is: "[downloads]//BitTorrent/Folder". You can verify this by looking at the list of all of your created backups.
Solution
Edit the backup and remove the preceeding "/" and save it. as I said before, my jobs have worked fine without the use of a preceeding or ending "/".
Also... I assume we are similar situation when it comes to backing up the files from the. I actually use the Remote: Rsync Server as the backup destination. Host, ReadyNAS local IP address, Path: "ShareName/FolderName", and Login/Password for local Rsync services. This way, it would sync the files... Not just backup duplicate files and such. I later set another backup job to clean out the bit torrent destination folder whenever it got too full.
Message 2 of 3
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2012-09-09
01:53 PM
2012-09-09
01:53 PM
Re: NAS->NAS backup 'Source path is invalid'
Thanks for your help, good to know it's not just me. I'll have a look at frontview tomorrow and let you know if it worked .. and hope that enough people raise it to merit an update.
Message 3 of 3