Backups

XP Pro, SP3, current updates, Comodo firewall, A^2 AV, Lenovo T60p Dual CPU - 2.1 ghz, 15.6" screen, 3 Gb computer memory, 3 cent operator memory

A long time ago I made a bootable backup on an external drive identical to the one in my laptop (same brand/version, same size, etc.). Since then I've made updates to it with a program called "Allway Sync" and when System Fix blew my primary system I booted to it even though it was pretty old.

If anyone is familiar with Allway Sync I could use some help on using it. The last time I used it I ignored all the warnings saying I should stop and look at zillions of files. Now I'm not sure about repeating that, even though I don't really know what I'd be looking for and what to do about it.

Current issue: I fired it up yesterday and it showed warnings on ALL .log files. Why? If I'm trying to make a copy of my system, why would I want to leave stuff out? Allway Sync seemed to do a good job before, but it seems too convoluted to me to anything other than let it fly.

Not that I'm ready to duplicate the formerly crashed system on the computer's internal drive before I can find out what is still wrong with it.

 

Something is wrong here. Allway Sync is purely a DATA backup and synchronisation program. You cannot backup an entire system with it. For system backup you have to use an imaging program like Acronis or one of the free alternatives.

 

No, nothing is wrong here. I said, quote:

"A long time ago I made a bootable backup on an external drive identical to the one in my laptop (same brand/version, same size, etc.)."

Then I said, quote:

"SINCE THEN I've made updates to it with a program called "Allway Sync" "

I said nothing about making a system backup with Allway. If you find it necessary I can look it up and tell you what program I used to make a bootable, swappable full system backup on an external (It boots on an external drive or I can install it into the laptop), but that is beside the point. Now I want to keep up the backup drive as a copy of the internal system. My OP was clear.

I am not using the original backup program to update the backup drive, because it was hard coded to make updates many times a day without warning, which would copy bugs as well as good data.

Since you know Allway, you know that it CAN pull stuff off your backup onto the other drive. I do not want to do that. I want it all going TO the backup drive; that part is easy enough, but I still don't know why it halts on .log files (among many others).

 

OK, I misunderstood your OP, sorry 'bout that. So what you actually created was a clone, and as Allway is running in Windows seems to me it's inevitably going to have mega trouble trying to update the clone simply because there are so many files it won't be given access to, either because of permission issues or because they are in use.

I don't know of any way a clone can be updated, but if there is a way it would have to be done before Windows is loaded, with a boot disk of some sort. And of course a clone is a clone, it will never be a selective backup that excludes bugs or anything else.

I think you are going to have to re-create your clone at intervals, but will be intrigued if someone can actually point you to a way of doing what you want.

 

I came here asking about some fine points. Now you're telling me I couldn't even do what I've already done because it's a clone. I don't know what your definition of "clone" is nor why you would declare what the original program did, not even knowing what it is. What program do you know that makes a windows XP "clone" that boots from anywhere it pleases. Are you telling me I could put my internal drive on USB and boot it? Because it is the perfect clone of itself. Or are you telling me I haven't actually been booting the "clone" from a USB extension for a couple weeks?

 

You know, you're right. Even virus writers can't do things that aren't "in the book." They are always limited to whatever the pile of libraries upon libraries upon libraries upon libraries allow them to do!!!!! That's why nothing strange ever happens when a virus attacks.

 

It's an approach to backing up that I've never come across before. You seem to have originally created a clone - in your words "bootable ...same brand/version, same size, etc", and how that clone was actually created is not now important, a clone is a clone. By subsequently running Allway those files that Allway can access will have been updated but many others that have changed will not have been, so what was once a clone most certainly isn't now. Your backup is some sort of hybrid, and while it may still be bootable it can't really be considered a backup in the usual sense of the word.

I prefer to stick with the mainstream backup methods, by imaging the system at intervals and using a sync program like Allway to keep more frequent backups of selected data folders.

Sorry I can't help more, maybe others can.

 

Actually I'm not sure it can even be called a clone. I chose to put it on an identical laptop drive so I could swap it no sweat, but the program will make it a bootable USB system drive on just about anything (if it's big enough). Altho it takes THE DRIVE, whatever you're using. 500GB? It is now your extra system drive and nothing else, according to the author. Clone?