ColDen
Senior Member
Yes.It also looks like the Synology DS220+ can handle both CIFS v2 and v3
Yes.It also looks like the Synology DS220+ can handle both CIFS v2 and v3
No, this was not done by BACKUPMON but by me (manually create the folders) while trying to previously troubleshoot this issue with the application but had forgot to delete them thereafter (now deleted).What share path are you using to see this? You shouldn't be able to see these other folders outside of the Backups folder if you were getting to it with a \\192.168.50.62\Backups share path.
I did not yet perform an actual backup but managed to successfully complete the test by reducing the "Backup Target Mount Point" length (why?????):No, this was not done by BACKUPMON but by me (manually create the folders) while trying to previously troubleshoot this issue with the application but had forgot to delete them thereafter (now deleted).
Still trying to figure out what might prevent the application to correctly access the directories and/or drives.
The \\192.168.50.62\Backups share path is not something that BACKUPMON creates... it's a share your NAS creates. I was simply asking if you could browse this share from a laptop? Because if so, you shouldn't be able to see anything else outside of the Backups folder, but only items under the Backups structure.No, this was not done by BACKUPMON but by me (manually create the folders) while trying to previously troubleshoot this issue with the application but had forgot to delete them thereafter (now deleted).
Still trying to figure out what might prevent the application to correctly access the directories and/or drives.
Well, it seems like your share path (\\192.168.50.62\Backups) is now working correctly, but I would highly recommend not tying it to your /tmp folder, as your router uses this to dump all kinds of temp files... and will all end up on your NAS. Didn't even think this was possible... Now that you know your share works, see if you can use the /tmp/mnt/primary (or some derivative) of this?I did not yet perform an actual backup but managed to successfully complete the test by reducing the "Backup Target Mount Point" length (why?????):
I am afraid that there is something more fundamentally wrong here...The \\192.168.50.62\Backups share path is not something that BACKUPMON creates... it's a share your NAS creates. I was simply asking if you could browse this share from a laptop? Because if so, you shouldn't be able to see anything else outside of the Backups folder, but only items under the Backups structure.
Well, it seems like your share path (\\192.168.50.62\Backups) is now working correctly, but I would highly recommend not tying it to your /tmp folder, as your router uses this to dump all kinds of temp files... and will all end up on your NAS. Didn't even think this was possible... Now that you know your share works, see if you can use the /tmp/mnt/primary (or some derivative) of this?
No, I'm pretty sure that /tmp is using the routers internal RAM. There's probably smarter people around here that could provide more depth to this.I am afraid that there is something more fundamentally wrong here...
Can you confirm that the /tmp folder is generated to a drive attached to the router's USB port?
That was the reply I was afraid off as I started noticing weird behaviors from my router (no longer working correctly on some displayed pages) after having also performing this test:No, I'm pretty sure that /tmp is using the routers internal RAM. There's probably smarter people around here that could provide more depth to this.
Yuck. Looks messy. Luckily this is volatile memory, so a reboot should reset things for you under the /tmp folder... but I would be focusing on whether or not you can use a "/tmp/mnt/primary" as is traditionally expected for a network share mount point.That was the reply I was afraid off as I started noticing weird behaviors from my router after having also performing this test:
View attachment 67810
Curiosity killed the cat...
View attachment 67812
It is also my hope that a simple reboot will do the trick and my gut feeling about not to do right away a backup following my initial discovery was right on. Agree with you that I should use the recommended Backup Target Mount Point path (note that I did try it right, still unsuccessfully, before using the "/tmp" one) and therefore I will still have to figure what prevent me to use the recommended one.Yuck. Looks messy. Luckily this is volatile memory, so a reboot should reset things for you under the /tmp folder... but I would be focusing on whether or not you can use a "/tmp/mnt/primary" as is traditionally expected for a network share mount point.
And when you use just "/mnt", it actually maps to "/tmp/mnt", but again... not a folder you want to entirely tie to a network share.
I'm hoping everything will start behaving after a nice fresh reboot. Crossing my fingers for you!It is also my hope that a simple reboot will do the trick and my gut feeling about not to do right away a backup following my initial discovery was right on. Agree with you that I should use the recommended Backup Target Mount Point path (note that I did try it right, still unsuccessfully, before using the "/tmp" one) and therefore I will still have to figure what prevent me to use the recommended one.
You can always try to time a reboot between potty breaks! LOL My family has gotten used to the fact that everything will just stop working every so often, and just get a bunch of angry looks. Ha!Now the hardest part, tell the boss (my wife) that I need to reboot now (as she is currently watching her favorite network show) ...
Done... This ASUS router (GT-AX6000) is the most robust of all the previously purchased ASUS routers (for me at less) and only had to reboot it when was required (either update or my own decision).I'm hoping everything will start behaving after a nice fresh reboot. Crossing my fingers for you!
You can always try to time a reboot between potty breaks! LOL My family has gotten used to the fact that everything will just stop working every so often, and just get a bunch of angry looks. Ha!
This very reason, is why I have her DVR her Telenovela's and stream the rest of her shows.I'm hoping everything will start behaving after a nice fresh reboot. Crossing my fingers for you!
You can always try to time a reboot between potty breaks! LOL My family has gotten used to the fact that everything will just stop working every so often, and just get a bunch of angry looks. Ha!
This very reason, is why I have her DVR her Telenovela's and stream the rest of her shows.
Provides for a fantastic Change Control buffer to minimize the angry looks from the occasional disruption.
Fortunately my Counter Strike addicted eldest son, moved out a while ago, which affords me a greater/flexible reboot window without impacting his stats.![]()
Still no luck and now wonder if this might be a full path length limitation problem since I was able to create/write with a very shorter one (/tmp and /tmp/mnt) and my NAS full path length or name (DS220_Plus_NAS)?Done... This ASUS router (GT-AX6000) is the most robust of all the previously purchased ASUS routers (for me at less) and only had to reboot it when was required (either update or my own decision).
Now I still have to figure out why still I cannot pass the BACKUPMON test with the recommended Backup Target Mount Point path but that will have now to wait for tomorrow.
Thanks, Viktor, for your assistance today.
Works like a charm for me. I useStill no luck and now wonder if this might be a full path length limitation problem since I was able to create/write with a very shorter one (/tmp and /tmp/mnt) and my NAS full path length or name (DS220_Plus_NAS)?
View attachment 67843
/tmp/mnt/NetBackup
(or the like) on DS718+, DS918+, and DS923+. Backup CIFS/SMB Version is 3.02. DSM version on all NASs is 7.2.2-72806 Update 4.I can give you the manual command so we can see what things look like after running these. It just can't be the /tmp/mnt path because that's just a function on the router. There's got to be another reason.Still no luck and now wonder if this might be a full path length limitation problem since I was able to create/write with a very shorter one (/tmp and /tmp/mnt) and my NAS full path length or name (DS220_Plus_NAS)?
View attachment 67843
I can give you the manual command so we can see what things look like after running these. It just can't be the /tmp/mnt path because that's just a function on the router. There's got to be another reason.Still no luck and now wonder if this might be a full path length limitation problem since I was able to create/write with a very shorter one (/tmp and /tmp/mnt) and my NAS full path length or name (DS220_Plus_NAS)?
View attachment 67843
Thanks for your reply visortwg,Works like a charm for me. I use/tmp/mnt/NetBackup
(or the like) on DS718+, DS918+, and DS923+. Backup CIFS/SMB Version is 3.02. DSM version on all NASs is 7.2.2-72806 Update 4.
Rights, no issues from various other PCs or devices.I can give you the manual command so we can see what things look like after running these. It just can't be the /tmp/mnt path because that's just a function on the router. There's got to be another reason.
Assuming you have no problem connecting to your \\192.168.50.62\Backups share from another computer right?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!