Is using 'mirror' for offsite backup's safe
At the moment I am doing a bunch of incremental backups to a local drive and then running a mirror job to copy all the backup data to an FTP location, this seems to make sense, but suppose some sort of hdd issue / virus / stupid user cause one of the local backup files to be updated with an incorrect file - this would then be mirrored to the ftp and it's gone forever.
Would it be a good idea to have a copy new files but don't update modified files? - I know this is pretty much another incremental backup, but the issue with just creating another incremental backup for the offsite process is that it means putting all your existing zips in another set of zips - which seems unnecessary?!
Any thoughts?
Would it be a good idea to have a copy new files but don't update modified files? - I know this is pretty much another incremental backup, but the issue with just creating another incremental backup for the offsite process is that it means putting all your existing zips in another set of zips - which seems unnecessary?!
Any thoughts?
-
- Posts: 1948
- Joined: Wed Dec 16, 2009 12:46 pm
Re: Is using 'mirror' for offsite backup's safe
Hi,
The application was designed to back up both new and existing files that were modified.
With all these, you can set up a scenario as you need if you run the mirror backup daily and use an exclude filter for all files having the creation date older than "yesterday".
The application was designed to back up both new and existing files that were modified.
With all these, you can set up a scenario as you need if you run the mirror backup daily and use an exclude filter for all files having the creation date older than "yesterday".
Do you know you can monitor your backups remotely with Backup4all Monitor? You can read more here: https://www.backup4all.com/backup4all-monitor.html