Archive maintenance report

markmorgan · Post by **markmorgan** » Fri Jul 21, 2006 11:11 am

I would like to see the start time on the Archive Maintenance Report alongside the end time as this time it took 2.5 hours to complete for 76 channels. :bigshock:

This was during an upgrade from 2.2.3 Alpha3 to 2.2.3 Beta. The last run would have been for 2.2.2 I think.

Mark.

Post by **support** » Fri Jul 21, 2006 11:21 am

markmorgan wrote:it took 2.5 hours to complete for 76 channels.

You must've had a lot of archived content. How big is your ARCHIVE.DB file?

markmorgan wrote:This was during an upgrade from 2.2.3 Alpha3 to 2.2.3 Beta.

There is no need to run ArchiveMaintenance if you are upgrading from a 2.2.3 alpha and actually, it won't even work :-)

markmorgan · Post by **markmorgan** » Fri Jul 21, 2006 2:16 pm

The archive.db file is 217,283KB.

Mark.

Post by **support** » Fri Jul 21, 2006 2:53 pm

markmorgan wrote:The archive.db file is 217,283KB.

That's chunky but it still shouldn't take hours.

It could possibly be explained by a slow and/or full disk. There might also be a problem with your database e.g. a key index has disappeared because of a previous partial upgrade. I'm curious as to why your upgrade didn't just fail. Upgrading from a 2.2.3 alpha to 2.2.3 should fail almost immediately.

markmorgan · Post by **markmorgan** » Fri Jul 21, 2006 4:25 pm

It did fail at first with a message saying that this was a fresh install not an upgrade until I noticed that the instructions said to remove the Awasu.upgrade file.

Mark.

Post by **support** » Fri Jul 21, 2006 4:41 pm

markmorgan wrote:It did fail at first with a message saying that this was a fresh install not an upgrade until I noticed that the instructions said to remove the Awasu.upgrade file.

OK, this explains why your upgrade was so slow: the first attempted upgrade deleted some indexes.

If you don't mind losing your archived content, it wouldn't be a bad idea to delete your ARCHIVE.DB file. Otherwise you'll find Awasu running slow because of the missing indexes.

markmorgan · Post by **markmorgan** » Fri Jul 21, 2006 4:51 pm

Can I not just run the rebuild indices option in archive maintenance?

Thanks,
Mark.

Post by **support** » Fri Jul 21, 2006 4:56 pm

markmorgan wrote:Can I not just run the rebuild indices option in archive maintenance?

Different index :-)

That's the search engine index, I was talking about the internal indexes in the SQL database.

What edition are you running? Do you save a backup before upgrading?

markmorgan · Post by **markmorgan** » Mon Jul 24, 2006 9:48 am

I'm running 2.2.3 Beta Personal Edition. Unfortunately I haven't backed up since 2.2.1 at the start of June. :cry:

Mark.

Post by **support** » Mon Jul 24, 2006 10:54 am

The easiest way to get back up and running would be to delete your ARCHIVE.DB file, although you lose your archived content.

It might be possible to recover your content, although it requires a bit of fiddling around in the command line and analyzing SQL tables/indexes. If you really want to keep your archived content and you can do this kind of thing, let us know and I'll tell you what needs to be done.

markmorgan · Post by **markmorgan** » Mon Jul 24, 2006 3:49 pm

I'll go with deleting the archive.db as it's easier. As a programmer myself I could do the other stuff but there is obviously a time issue and the content is not that valuable as it were.

Many thanks,
Mark.

Archive maintenance report

Re: Archive maintenance report