Slow when using asz
When I use an open partition for storing the image I can image my main drive twice as fast, but I want to use ASZ. I rely on the new image booting out the oldest image in the asz. This, of course, isn't necessary when I store the image in an open (plenty of space) partition. Is there anything I can do about this?
Does anyone at Acronis monitor this? I guess not. Its the 23rd and there have been 36 reads. Rather useless methinks.
I normally back up to a separate hard disk, but this evening I will create an ASZ and see how long it takes to back up to it compared to my normal backup procedure. I assume that when you say that its much faster when you back up to a separate partition, that the separate partition is on the same hard disk as your ASZ? If so, it occurs to me that the separate partition on your hard disk may be adjacent to your primary partition and that the ASZ partition is located further away from the primary partition on your hard disk. If that is the case, then a backup to the ASZ is going to be slower since the drive heads need to sweep across more of the disk platters when accessing the primary partition and the ASZ partition. One solution in this case would be to delete the extra partition and ASZ, recreate a new ASZ so that it is next to the primary partition, and then recreate another secondary partition. Another solution would be to install a second internal hard disk and create an ASZ on it for backup purposes.
Greetings from the gateway to the west. Thanks so much for replying. I was beginning to think there was no one out there. Well the ASZ is on the same disk but the additional time it takes isn't as finite as the movement of the drive heads...we are talking just about a half hour more than to just make an image on a regular partition. Since I wrote originally I have increased the size of the ASZ and deleted a few images from it and I believe the ASZ being full when I try to add to it is the real problem. I can make the image in much shorter time when it doesn't have to delete enough room to add the image to the ASZ. I don't know why this would amount to half an hour just to delete those images but that seems to be the case unless I have something set up wrong. It seems the mechanics of the procedure would be to estimate the size of the image to be created and then check to make sure the ASZ is open enough and if not delete whatever is oldest in the ASZ. Well again, thanks for responding. If you have any additional thoughts, please give me a shout.
Hi Charles,
It sounds like you have gotten to the root of the problem. Good job of increasing the ASZ size and deleting a few images before running another backup. I still think that I will test doing a backup to a newly created ASZ later this evening. :-)