Problem with FTP
First some rambling background information:
I have been successfully using and ATI FTP backup of some files and folders for several months but a week ago it started hanging up. And while the backup was hung up other network connections to/from my PC would hang up or terminate. The only evidence I had that ATI was the culprit was the couple times I manually started the backup and would immediately have the network problems. After fight this for two days I did a full restore of my C: drive back to before the problem started. That fixed the problem but also removed the ATI logs documenting the problem. :-(
I deleted the FTP backup task and replaced it with a more standard SMB backup ... hoping that the AAP ransomware protection is robust enough to protect the NAS-resident backups.
Now for the current problem:
I want to try to recreate the FTP error but cannot recreate the FTP task. From an old backup of Acronis ProgData if found "ftp://ds218_1:21/Backups/Puget-116877/@task@.tib" in the old backup script, but I cannot now get ATI to go below "ftp://ds218_1:21/Backups". When creating a new task ATI will not expand the "Backups" directory. it will also not let me create a new folder there. (It give the option but nothing happens when I click on it.)
I've tried specifying the uri "ftp://ds218_1:21/Backups/Puget-116877/" and ATI accepts it but creates the backups in the "Backups" directory rather than the "Backups/Puget-116877" directory. I have no trouble reaching the lower level directories with other FTP clients.
Update:
The FTP server above is on a Synology DS218 NAS. I just tried the FTP backup to a Western Digital MyBookLive and ATI has no trouble at all (except the the MBL is much slower than the DS218). I'm more puzzled than ever now because this does not seem to be an ATI problem but more of an ATI/Synology problem.
Steve, that's what I do, too (except I use a DNS name rather than IP address), but in my case I need to drill down one more level. My equivalent of your "Acronis" directory has multiple sub-directories. On my Synology NAS, ATI will not drill down to those lower level directories; it will not find existing directories or create a new directory. And if I try add an existing backup, ATI will not look below that top level directory. It obviously used to be able to do that since I had a backup working until last week. And I was up to b21_s3 for full + 5 incr taken daily so this had been working for some time.
Since I don't have the same problem with a WD NAS, I wonder if some recent Synology maintenance changed something. I'll dig around some more.
Patrick, seems strange that you cannot navigate to the sub-folders or create new ones. Just tested this again and had no problems with my Synology NAS and FTP doing both.
I was able to use both methods of connecting (IP address and IP Name) where the only thing that threw me for a moment was when ATI asked for credentials for the new IP Name FTP connection and failed until I just used the IP Name on its own, without any folder qualification!
The fact that this backup had been running with no problem and that ATI has no problem with my other FTP servers makes me think something has happened to my Synology NAS - a new permissions problem, perhaps. But I have no trouble with permissions when using a different FTP client - WinSCP.
The problems with backups to the Synology FTP server started after I restored by PC using a week old backup. A few backups on the NAS were no longer in the ATI database. I deleted that backup task. After that I was not able to access the sub-directories on the Synology FTP server. I suspect I have some corrupted data somewhere that is confusing ATI but this seems like a peculiar symptom to have.
Update:
Just for grins I deleted the Acronis Connection registry records for this NAS and tried "Add existing backups". ATI still had the NAS in "My FTP connections" (which I did not expect) but no longer had the credentials (which I did expect). And I still could not drill down beyond the top directory. ATI obviously has information about this NAS somewhere other than in the registry - in its database, I assume. I guess I could do a clean reinstall of ATI but I hate going that route.
Update #2:
This is almost certainly a problem on my Synology DS218. ATI on two PCs are acting the same and there has been no problem - restores, etc.) on the 2nd PC.
Update #3:
Once again, WireShark proves it's worth. ATI dutifully tries to list all the directories in my Backups directory but comes across one it can't list:
Request: MLST /Backups/#recycle
Response: 550 /Backups/#recycle can't be listed
At that point it gives up. (WinSCP can't list it either, but I had not tried with WinSCP). I don't know why #recycle is suddenly giving me trouble but I don't particularly want or need recycle support on this NAS. Maybe I'd better finally figure out how to get rid of it.
Patrick,
Thanks for the detailed followups on the TI/Synology FTP issues. I've been beating my head against it for three days. I could list the sub-folders under the <home> folder for the login account but not the sub-folders in the main shared folder, even though all permissions, etc looked right. Using an administrator account to login let the shared folder work properly. This is with TI 2017 and TI 2019.
I found that the #recycle folder in my shared folder had permissions for only the administrator group after I read your wireshark findings. Changing the permissions of the #recycle folder to <everybody> made the main shared folder list it's sub-folders like it should. Apparently when TI hits a denial it just rolls over and quits....
Thanks again for the followups. Hopefully Google will find this so others don't have to waste the time.