firstname.lastname@example.orgMy question to Kaseya (still unanswered satisfactorily) is 'what do I need to do to know that my backups are good?' If they can't provide an answer to this question, then they ought to be looking for a better backup vendor to use.
thirteentwentyjust my opinion, others have been successful with doing it, but I only run BU-DR via Kaseya on workstations.
--- what do you do for servers?
--- what does that do to your cost structure?
Edit: Also worth noting, we've used several different backup solutions, none of which are fool proof and work all the time.
--- been doing this since 1981 and thats why I lik using 2 or 3 different kinds of backup eg. ntbackup + budr/besr/whatever + mozypro/whatever. but as we rollout more clients mgmt becomes the issue.
Anyways I hope that my "style" of things answers your question...
In short, I don't believe it unless I or someone within spitting distance can do it... It's not an anti-BU-DR thing its just the way I am.
Edit: If you would/could share your BU-DR basic configuration, and points of failure... maybe others with more success can help.
My biggest pain was space for images, now I have a simple formula, total drive space to be backed up (this includes free space) x 5 is the minimum required for us to do any type of onsite backup. And even this is going to become an issue as more and more TB workstations show up... but until then, this part of the forumla works...
JMFI'll add my verify mystery to the pot:
We were supplying WD Passport Essentials to our laptop clients for backup and kept getting verify failures. If we backed up to a NAS drive or other external drive (including a WD Elements, which we supply now), no problems.
If we copied a backup that passed verification from a drive to the WD Passport Essentials, it would fail a verify.
Poking around on some Acronis forums, it appears that some USB drive chipsets (we tried an ACOMDATA enclosure and had the same problem) miscalculate/mangle the checksum, causing the verify to fail.
Only Acronis seemed to have a problem with these drives. Spinrite and Windows could read/write data without problems...
We rarely get a verify failure now, and if we do its usually caused by a machine rebooting in the middle of it or some other hadware issue.