cbbackupmgr logs then ignores errors from the storage layer

During a backup when getting errors from the storage layer e.g. a failed write (caused by the mutation/deletion callback in dcp.go) they will be logged, however, we simply ignore them and continue trucking. This is the wrong behavior; we should at the very least evaluate the errors and exit if they are serious.