Page 1 of 1

ftp backup location

Posted: 24 Nov 2016, 06:25
by PB4FUN
Would be great if I could have the possibility to backup to an external location (e.g. my personal space on some webserver).
In case of total destruction things like fire, flooding or damaging of local storage devices by lightning my log will still survive.

Re: ftp backup location

Posted: 24 Nov 2016, 08:07
by G4POP
Many of us use cloud storage, like Dropbox or Google Drive, for just that reason

Re: ftp backup location

Posted: 25 Nov 2016, 17:50
by PB4FUN
But without ftp options in backup location some cloud spaces cannot be reached directly from within the program.

Re: ftp backup location

Posted: 20 Dec 2016, 21:40
by NN7D
Check out page 159 of the Log4OM User Guide for information to using one of the cloud storage facilities for storing an automatic backup copy of your Log4OM log. It describes using Dropbox, however my personal favorite is Google Drive. Microsoft also has their own version. When set up, your log is still on your computer, but whenever a change is made to your log, it is automatically updated in the cloud storage. The bonus is that you can then access your log from another computer if need be. And if the inevitable strikes, and your hard drive goes kaput, you have a complete and current backup available. Good stuff.

You will need to install either one of the services apps on your computer - Dropbox, Google Drive or Microsofts ever changing name app. I install Google Drive app on my computer. Then you will need to change your log file location to the Google Drive folder. Once that is done and the Google Drive app is running (auto start), any change to your log will be synced with the cloud storage.

Doug - W7DRM

Re: ftp backup location

Posted: 24 Dec 2016, 20:26
by PB4FUN
dropbox != ftp;

Re: ftp backup location

Posted: 28 Dec 2016, 17:44
by IW3HMH
FTP may be an option in the future.
The problem is FTP, SFTP, FTPS, Anonymous, registered, ........

There are a couple of different ways a FTP can work. Choosing a way will make someone happy, some one else unhappy...
I personally have a .cmd script set on Log4OM startup that retrieve the .ADI file and make an FTP.
Yes, it's on "next start", but it's another backup (i already have Google drive, local backup when closing...)

If Google drive fails, local disk fail i have an FTP version updated to the latest-1 usage of Log4OM.

Considering i have realtime upload to QRZ, HAMQTH, CLUBLOG, HRDLOG.NET it's a pretty acceptable solution...