Imaging prior to Service

[SilverLeaf]

No need to do the PE stuff; just install DriveImageXML like any other program, does a "hot/live" image just fine. Never had a bad one yet *knock on wood* but that's also why I manually verify each image on a separate machine - just open it up & make sure I can browse it.

I can also of course just pull the drive, plug it in via USB-SATA adapter & take the image that way. Had to do that recently when the image kept failing for some reason.

Yes, I generally do store the images on a NAS w/RAID.

After reading about 16k_zx81's experience with DriveImageXML in this thread: http://www.technibble.com/forums/showthread.php?t=41643&highlight=driveimagexml, I'd be hesitant to use it. Never used it myself, so I can't really offer any personal experience though.

 

[drjones]

After reading about 16k_zx81's experience with DriveImageXML in this thread: http://www.technibble.com/forums/showthread.php?t=41643&highlight=driveimagexml, I'd be hesitant to use it. Never used it myself, so I can't really offer any personal experience though.

Man, that really sucks and I will definitely be sure to take an even closer look at the images I take with DriveImageXML.

As I've said though here are the precautions I take when imaging a client drive:

- I use the exact same version of DriveImageXML. I keep a copy of the .exe on my network drive, USB drives, and have only ever used the exact same version.

- After each image, I manually verify it on a different PC than I used to take the image with.

- I manually backup all known valuable data to a separate directory; any obvious folders on the root of C:, any program data such as Quickbooks from the Public folders, user profile docs, desktop, favorites, Outlook data & settings, etc.

I do that because of how long it takes to extract data from the images, AND as an added redundancy.

After all those steps, I feel pretty confident that the clients data is safe.

Again, too bad the experience that tech had, but it seems to me he skipped the very important step of verifying the image.

ETA: Taking a closer look at that thread you linked to, looks like 16k really screwed up, frankly....he had no prior experience with the software and decided to test it on a clients machine/data....obviously a big, big mistake. Not to bash him in any way, but I think he's got nobody to blame but himself.

 

[drjones]

I prefer to image from a PE environment. Any of you guys do this? If so, what programs easily works that way?

Also, for those that promise to keep data for a specified period after the repair, are you on a RAID system or other type of redundant setup. This always worries me. I always take a lot of time explaining that I am not guaranteeing availability. The old lawyer in me I guess.

If you don't have any sort of a NAS or server for your office, you really should invest in one.

The data transfer speed & convenience of not fussing with USB drives to move data around alone is worth it.

 

[drjones]

Just curious as to what criteria everyone is using to determine when to image. Are you imaging every machine that comes through the door, whether it be for a virus removal, tune-up, etc..?

I'm generally a cautious tech, but I don't image as much as it seems some others do. Where do you draw the line?

I only ever image/backup a clients data when I'm going to reinstall the OS. Never any need to do it any other time, IMO.

 

[andcorptech]

Macrium Reflect also does this. You must view the image/files through the software itself, but seems to work well.

I use macrium all the time now. You technically dont view the image via their software, but you do mount each partition to a drive letter. From there is just a copy/paste for specific data. Alternativley you could image the whole thing back to a drive if required.

As for imaging prior to service, we do it when we suspect hdd fault, before we do a n&p and when we are uncertain what exactly is wrong as a precaution. We usually keep data for 60 days unless customer doesnt want us to.

On systems where free space permits i will copy the macrium image to a support folder to allow for easy retreival of anything we may have missed and tell the customer that they can delete it when they are comfortable they have all their data

 

[HFultzjr]

Just curious as to what criteria everyone is using to determine when to image. Are you imaging every machine that comes through the door, whether it be for a virus removal, tune-up, etc..?

I'm generally a cautious tech, but I don't image as much as it seems some others do. Where do you draw the line?

I do an image "almost all the time", except on site of course.

Unless it's something really simple and quick, I'll image.

It can be imaging as soon as I bring it into the shop, while I do the paper work, other things, etc. Or, even off hours (overnight) un-attended.

I just work it into my work flow as I have been burned in the past.

I also "try" and do an image when completed to keep as a "backup" for the customer, in case it comes back later with hardware failures. I usually keep them for a month or 2, rotating several 2TB drives. I've actually had occasion to use these images......such as the times hard drives fail for no apparent reason. You are the customer's HERO when they call you with bad news, and you say........I just may have an image from when I worked on your system last. Mostly depends on my workload and may not be feasible for those pumping out a lot of work. I'm just a 2 man show (my son and I), so there are times I'm not real busy. Plus this is something I can do to keep him occupied....LOL.

 

[SilverLeaf]

I'm not sure I'd want the responsibility or liability for the physical security of all that data in-house. Do you store it encrypted?

 

[HFultzjr]

I'm not sure I'd want the responsibility or liability for the physical security of all that data in-house. Do you store it encrypted?

Yeah,

That's always been a concern of mine also.

1st, I make no indications that I'm going to keep/store, etc. any of their information, as part of the work I'm performing. I do have in my work orders, that I may keep an temporary image of their data for up to 60 days at my discretion.

Right now, I'm storing them in a fire proof safe in my office.

If I do something other than residential, I'll usually store the image in a TrueCrypt container.

I generally don't keep them very long.....secure delete.... and then overwrite with a newer image.

If it's something "business" or really important, I usually try and talk the customer into saving it themselves on a portable hard drive and also set-them up with a backup program, or on-line backup.

It still amazes me how many people have NO backups at all.

Hope I'm doing it right!

 

[SAG]

I guess I'll throw it out there again. Disk2vhd. If the drive is ok, this is the way to go. It's free and painless. Mount the vhd in drive manager or just open it with 7-zip.

I use this tool extensively.
In fact, used it twice today.
Free, small, portable, and only 2 buttons to worry about.

 

[mikeroq]

I either use disk2vhd or I make a .wim image. Both can be mounted to view the files. If I go with vhd, I can use it in a virtual machine for testing repairs or to boot into it.

 

[Gary Rockliff]

I have always used Acronis.

Not only can I mount the image and copy files and folders but I never run into permission issues.

 

[16k_zx81]

I've long made it a habit to image clients drives, I've been using DriveImageXML and it works flawlessly.

That^, may not be such a good idea. A search of the forum for the product name will be informative as to why.

Dxml is *not* suitable for use to archive customer data, unless you really dislike your customers, that is.

(Edit) oh . someone beat me to it.

Yeah their software is iffy at best

These days I'm am using shadow protect.

 

[rsarceno]

I guess I'll throw it out there again. Disk2vhd. If the drive is ok, this is the way to go. It's free and painless. Mount the vhd in drive manager or just open it with 7-zip.

+1 Disk2vhd and Disk Management (Keep it simple and mount as read only)

I used a shared encrypted external USB drive connected to my server. I erased it as needed (average the data is keep for 1 - 2 weeks). If client drive is in poor condition, I save it as invoice#-poor.vhd This one I keep it a little big longer.