2D, I was going to skip over this but since there are post but a few days
old, here goes.
Disk imaging is a reasonbly simple method to get a base line of your system
which, if you are really paranoid; you should recreate on a schedule
(?Weekly, monthly, quarterly?). This will give you and in time methodology
for restoring your system to a date in time. Remember, if your system takes
a dump, you will lose whatever isn't on the last image.
For those since last imaging backups there are many options and you can make
a case for many avenues of approach.
My personal favorite uses TaskScheduler and batch files calling a free
utility availble in various places called robocopy (it's actually from
Microsoft utility). This tool is great for making duplicate copies of files
and disk structure and I think this is what it was designed to do.
The way I use this is to backup my data files on a nightly basis to a USB
drive of the same size (200GB) as the source drive. Now, you would think,
'Man, how long does that take?' Initially it took an hour and forty-five
minutes, nightly, it takes about ten. With proper command line structure,
you can set robocopy to only freshen and add new files or you can replace
everything. And several additional things in between but, we are here to
talk about backup.
You could get fancier by rotating your backup drive daily (been there) or
weekly (done that). It is really up to you.
Now, I recommend this for data files only, do your images for applications
and data, then use robocopy to restore any data files that you created since
the last imaging. Do not use this to backup sql databases, create disk dumps
and then back those ups. We had a client change to that when database
backups through BackupExec failed to restore properly. They create diskdumps
and then use robocopy and and executable to place them in an offline storage
folder which changes base on the day of the week.
Well, I've blithered enough. Good luck with what every you do!