BUMP!!!
More and more clients are asking for CBU to be updated to cover 2010 and 2013.
Cheers,
Ewen
BUMP!!!
More and more clients are asking for CBU to be updated to cover 2010 and 2013.
Cheers,
Ewen
I would like to see:
better logging support (preferably in Applications and Services Logs. When running as a service there is no log that I can find (this is windows 2008, which is buggy).
Also friendlier or more verbose logs. For example, say âNetwork SMB credentials failedâ, rather than saying âError writing in backup file.â
higher priority: be able to backup the complete disk(s) that are on different physical disks. Currently I have to schedule two jobs to do this.
Thatâs a great idea. +1
I would prefer to have it this way: One click button to create a recovery bootable USB drive that allow to connect to whatever backup store over iSCSI, NAS share, FTP, Rsync, DFS-R, Cloud, USB, eSATA, VHD, VHDX, etc. and proceed to a bare metal recovery to the same or dissimilar hardware.
With that feature, I would recommend CBU without restriction.
Backup verification is good but restore simulationâs better. A backup is only helpful if you can rely on it and make sure you can recover from it
One of the greatest thing that should be implemented is a bandwidth friendly protocol like Rsync or DFS-R.
Rsync client and server should be implemented so two CBU installations could be used to achieve remote sync or incremental backups.
DFS-R is even a better solution as it doesnât bother with filenameâs changes or files that have been moved to some other folder in the structure. Itâs working at the block level so it can sync a 200 GB working set in a matter of minutes over a slow link WAN like Internet.
Of course, encrypted channel option like SSH or SSL or VPN (like Comodo Unity) would be a must too.
For many similar backup files, integration with Windows Server 2012 deduplication feature would be a reasonable choice.