www.aiscl.co.uk

I am trying to restore some files from by backup onto my main disk- but am having problems.

The obvious way I thought to do it was to do the following:

launch AISBackup
Select the correct Job (in this case I only have 1 job defined so it always pre-loads it)
Press the "restore from backup" button

I do this- but nothing happens. Clicking the button has no effect.

Am I doing anything wrong, or is something broken?

Good thing I discovered this while mucking around not trying to bring back an entirely dead system!

Ruahrc

Are you using version 2.2 of AISBackup? Very old versions of AISBackup also required a 'Load Script' before 'Restore From Backup' was enabled.

What you are doing is correct. Is the sessions tab enabled and after selecting sessions tab are there one or more backup sessions?

On the 'Job' tab is there a last backup date?

If you would like us to give a more informed answer, please send us the job files via the Help / Bug Report / Attach Check boxes option. Again, if you have a very old copy of AISBackup we require the <jobname>.bdb, <jobname>.buz and all the other <jobname> files from the AISBackup database folder, which by default is:

C:\Program Files\Aquarius IS Consultancy\AISBackup\Database

Before that I just thought of one more thing!!

The disk to disk copy style of backup does not have a restore option as this is a 'clone' operation, to 'Restore' select the destination as the source of the backup and copy to the original source of the backup, example:

The backup was from C: to D:

to restore copy from D: to C:

Barry

Barry,

You're right that makes sense. What I did then was I created a new job and called it "Restore". I made it identical to my "Backup" job except I switched the positions of destination and source. Then I ran it and it seemed to detect the altered portions and restore them according to my backup.

I did run into one snag, however. It seems like after I ran this "restore" job, I saw a folder in my C: drive I had not seen before. It was called AISRSTR. In it were some files, namely one exe called AISBRSTR.exe. I (foolishly) ran this exe and it said I had to reboot my computer to finalize the restore process. Okay- reboot. Then it booted, and ran this AISBRSTR.exe automatically upon loading the desktop and asked me to reboot.... you can see where this goes- an endless cycle of reboots.

I was able to break the cycle by booting into safe mode. From there I erased the AISRSTR folder and booted normally. The first time around it gave me an error saying it could not find C:\AISRSTR\AISBRSTR.exe. Of course not I removed it to get out of that circular cycle Anyways I rebooted one final time and things seem normal now.

Can you please explain to me what this folder/file is? It obviously is related to AISBackup but I have not ever seen it on my disk before. It is not on my backup volume either.

Ruahrc

C:\AISRSTR\AISBRSTR.exe is used to complete backups which require a re-boot, and checks the integrity of the restore and may do some post restore tidying up, e.g. remove temporary files used during the backup.

The fact yours looped is a bug, so I will try and re-create what you did here and provide a fix. What you did to fix the problem was correct - a hammer may of worked too

C:\AISRSTR may be on the PC and may be empty, and indeed the folder may be on more than one drive - it usually contains temporary restored files (those which cannot be replaced until a re-boot) and various control files.

Perhaps it is about time we looked at removing the folder when it is no longer required, however, it usually does no harm - well, until today

Barry

Hello Barry-

Wondering if you had any more info regarding this? I haven't tried to do any more restores yet so unknown if this was a one-hit wonder or not.

Ruahrc

The update to remove the redundant AISRSTR folders is in the 'next' version of AISBackup, this is not on general release but you are welcome try it:

http://www.www.aiscl.co.uk/build274/aisbi274.exe

Your report was the first to report things going wrong with AISBRSTR, and I think the problem may have happened because you manually ran AISBRSTR rather than a restore running it. However, when I ran AISBRSTR it terminated quietly , which is what was supposed to happen.

Barry