Back up to network drive does not work
I have an error that I cannot resolve that deals with a remote back up.
I have my server set to perform an FTP back up to my system here on site (at my home office). The FTP server that I am using is firezilla. When I set the user in firezilla to us a hard drive in my man computer as the home directory with full rights, the back up goes flawlessly. However I do not want that to be the permanent location of my back ups. I want to use a NAS attached to the network. When I change the users home directory to the mapped network drive, it fails. When I run the validation in WHM this is the error that I get. Note teh 550 error at the nest to the last line.
Is there a way I can set things up so that the back up will perform correctly to the mapped network drive?
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> Connected, sending welcome message...
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> 220-********************************************
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> 220-***
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> 220-*** Hello Neo, I've Been Waiting For You
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> 220-***
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> 220 ********************************************
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> USER Back Up Users Name
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> 331 Password required for Back Up Users Name
(000003)7/30/2016 2:10:00 AM - (not logged in) (xxx.xxx.xxx.xxx)> PASS Back Up Users PW
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 230 Logged on
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> TYPE I
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 200 Type set to I
(000002)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> disconnected.
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> PORT zzz,zzz,zzz,zzz,151,193
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 200 Port command successful
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> FEAT
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 211-Features:
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> MDTM
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> REST STREAM
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> SIZE
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> MLST type*;size*;modify*;
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> MLSD
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> UTF8
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> CLNT
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> MFMT
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 211 End
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> HELP ALLO
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 214 Command ALLO is supported by FileZilla Server
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> ALLO 84
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 202 No storage allocation neccessary.
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> STOR /validate.tmp-15823-1469859000.txt
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 150 Opening data channel for file upload to server of "/validate.tmp-15823-1469859000.txt"
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> 550 can't access file.
(000003)7/30/2016 2:10:00 AM - Back Up Users Name (xxx.xxx.xxx.xxx)> disconnected.
-
Of course not 10 minutes after I posted I figured out what the stupid thing is that I am doing. Instead of setting the FTP users home directory to the full network path I was using the mapped network drive on my PC. As soon as I rectified that SNAFU everythign started running 100% correctly. Thanks for tolerating my stupidity! Problem solved. :) 0 -
Hello, I'm happy to see you were able to address the issue. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
2 comments