www.aiscl.co.uk

Apparently running Manage Backup/Validate (Test) Backup fixed the problem. It found some orphaned files and saved them. The backup ran last night--but aborted when it ran out of room on the destination. That apparently happened because there were several incomplete backups made without purging. Hope...

I told it to go ahead and finish pruning, but it still did not back up last night. Again I find the same message box about finishing pruning. I told it to go ahead. That was several hours ago. I have an icon on the lower right of my screen indicating AIS is pruning. It seems unlikely it could take t...

AISBackup runs on a Terminal Services login that I leave logged in for that and some other background processes. I needed to shut it down tonight, and on closing the other windows found an AISBackup windown saying some unidentified files were found, did I want to continue with pruning? Maybe now it ...

I'm using AISBackup v2.4.0.303 on my server (W2K3 Server) with scheduled backup jobs every weeknight called Full C and Full D. It is set to get backup contents from the destination drive, and I rotate out USB hard drives for the destination. (Backup to External Drive: [drive name] [drive2] etc, Back...

I always had at least one of the listed drives connected.

I have rolled back to version 2.4 and it is working fine now. Apparently "open backup contents from drives" is not working in 2.5 for multiple drive either. But with 2.4 it seems to be working great.

Thanks

I followed the tutorial, but this still is not working--keep getting message that it can't find the backup.

Maybe I missed the point--even though I followed the tutorial, was I supposed to go back to version x.4 also?

Andy

Okay! Looked at the tutorial, looks good.

I was planning to use 4, but 3 is likely enough. As I read it this will still make a backup on any day with any of the three drives. I just need to name them different and register each one.

I thought the job was supposed to look at the backup file before each time it runs, and decide what needed to be added based on what it saw. Thus each drive would end up having a backup that was complete as of the last time that drive was used. And it would still work even if you used the wrong driv...

To add some additional info: I am on my second time through, and getting the same message--so my backups aren't running overnight.

I have 4 identical USB hard drives to use for backups. In another thread I read that if you are using identical drives with the same drive letter, it is not necessary to list each one as a destination drive. I used autorunning to schedule a full backup each night. The second night I swapped a USB dr...

Well, I guess I found my answer in the thread "Batch Backup". (Honest, I did look through the forum before I posted--I just didn't realize that thread would have my answer, until I read the posts...) But that raises another question: I already scheduled each of the backup jobs individually...

I wanted to schedule a full backup of my server (C: and D: drives), but the software suggested dividing large jobs into parts. So I created a job for C: drive and one for D: drive. I scheduled them around the same time, thinking they would either multithread, or one would wait for the other. Instead...