Please add a feature, that (not neccessary normal repos) files can be backed up parallel to multiple servers/repos/storages.
the idea is, to quickly copy all data to multiple directions, so they can never be lost.
means normal job (e.g. hyper-v job) runs, and then all data is backed up to the desired destinations:
- normal repo
- additional repo
- somekind of storage S3/object/webdav/ftps/sftp/samba...
...
So the data is streamed/copied quickly to all destinations.
yes it would be possible to use some copy jobs for this..
but it would be more convienient to just check a box and then the data is stored in my private fort knox which could be write-only (no deletion).
-
- Expert
- Posts: 246
- Liked: 15 times
- Joined: Jul 25, 2018 4:12 pm
- Full Name: Poweruser
- Contact:
-
- Service Provider
- Posts: 250
- Liked: 45 times
- Joined: Jun 10, 2019 12:19 pm
- Full Name: Daniel Johansson
- Contact:
Re: Feature Request: Double Backup
+1 for this. Copy jobs have their use, but one problem with them is that they cannot be remapped to normal jobs. So when the disaster happens and the main backup is gone, the expectation is that the backup admin will run new full jobs and then continue on the backup copy from the new backups. This could easily mean a gap in the backups while new fulls are being created. I would much prefer to be able to simply remap the job to the copy and continue, and configure a new copy where the original backup was. Of course, it wouldn't be much use to start with copying an incremental, so in such cases the copy should start with the latest full and then build up to the latest copy. So we would benefit from either a "direct copy" like this suggestion, or to change the format of copy backups so they use the same format as normal jobs and can be mapped to either.
Who is online
Users browsing this forum: No registered users and 3 guests