Salta al contenuto principale

Can I Automatically Backup to my Hosted server Instead of Local Disk?

Thread needs solution

Can True Image automatically backup my PC to a directory on my hosted server? I don't want to create the backup on a local drive then use FTP to upload it. I'd like to point the backup process to store its file on a directory of my hosted server.

0 Users found this helpful

Kenneth, welcome to these User Forums.

You can use FTP direct from the ATI application to your hosted server directory but if doing so then you should use the Password encryption feature of the application, as ATI does not support using Secure FTP.

 

Thanks, Steve. That will work for us. The office currently uses ATI 2018 and I am remote so I cannot see it. Does ATI 2018 also have this feature?

Kenneth, yes, the same FTP option has been present in all of the recent versions of ATI going back quite a few years.  For ATI 2018 see here.

Kenneth, the FTP client in ATI is not particularly well behaved.  It works well for backing up small files and folders but has some unfortunate behavior that causes problems with large backups such as complete PCs.  In particular, ATI FTP limits an individual backup file to 2GB so the backup of a PC with large amounts of data can create a backup containing hundreds of .tib files.  This is not a problem in itself, but during deletion of FTP backups the ATI FTP creats a separate FTP control connection for each file being deleted and keeps these connections open until the entire delete process is complete. 

This is very problematic behavior.  If your FTP server limits the number of open connection, and this limit is lower than the number of files being deleted, the delete process just hangs.  If your server (or remote host) does not limit the number of connections, you risk exceeding the number of connections allowed by your remote host or hanging up the Windows TCP/IP stack.  (I've run into both problem before I had a NAS that restricted the number of FTP connection with a given client.)

This problematic behavior has been around since at least ATI 2017 and still exists in ATI 2019.  Acronis support is (in theory) aware of the problem.

A possible circumvention to this problem is to take ATI backups to a local drive and then FTP the backup outside of ATI.  An added advantage of that procedure is that you can use a client that supports a secure transfer such as SFTP or FTPS ... as long as your remote host supports them. 

I agree with Patrick here.  It is much better to "transfer" already created backup files via FTP using a third party client such as Filezilla for example.  Less problematic and more secure.  :)