GFI Mailarchiver Upgrade (Full Version)

All Forums >> [Archiving & Fax] >> GFI MailArchiver



Message

jonathanhaun -> GFI Mailarchiver Upgrade (3.Nov.2005 4:31:00 PM)

Is there a way to force the upgrade utility to process more emails per second. I am upgrading a 11 GB Database and it has only proccessed 85000 of 490000 emails in the past 8 hours. Please help.



jonathanhaun -> RE: GFI Mailarchiver Upgrade (4.Nov.2005 3:57:00 PM)

We are going on days 3 of the upgrade. Is this a joke?



ConSolIT -> RE: GFI Mailarchiver Upgrade (4.Nov.2005 5:00:00 PM)

[Mad] I'm on day 4 and the damn utility has locked up 5 times!
Support won't even reply back to my requests.

I threw 4 processors in realtime processing at the update utility process and the damn updater never went any faster!

We're at over 20gigs in the 5 months of running this software and 2 gigs waiting to be dumped into the new database.

GFI WTF???? Through us a bone of info on what your doing to help us!
I want my support!
[Confused]
Gfi you should have given us a choise of an offline version of the updater so we could have kept 2.0 running while the update ran on another system.



muellert -> RE: GFI Mailarchiver Upgrade (5.Nov.2005 5:28:00 AM)

I agres.. mine has been running now for 20 hours and only 40% done. I am running a dual Xeon 3.0Ghz cpu with 5Gb's Ram (Windows 2003)...



angusm -> RE: GFI Mailarchiver Upgrade (6.Nov.2005 11:31:00 AM)

My db upgrade has been running for >27 hours and is still going. For the last three hours the counts have not changed (300132 of 300173 written). Although MArcUpgrade.exe nolonger seems to be doing much, sqlservr.exe is still busy, so I am hoping that the upgrade process is just waiting for SQL Server to catch up before finishing.



angusm -> RE: GFI Mailarchiver Upgrade (6.Nov.2005 1:27:00 PM)

My db upgrade, now in its 29th hour seems to be looping.

The old db is 35GB, and the new one is 15GB.

There are 300173 emails, and the progress counts stopped at 300134 read and 300132 written several hours ago. The CompletedIndexList table has 300173 rows, and the SQLProfiler tool shows shows a repeating sequence of

select top 50 [id] from arc where [id] not in (select [id] from CompletedIndexList) order by [id]
exec sp_reset_connection

Any suggestions as to how to make the upgrade finish?

Thanks,

Angus.



angusm -> RE: GFI Mailarchiver Upgrade (6.Nov.2005 1:36:00 PM)

Oh, and the MArcUpgrade.log shows a line like this

2005-11-06,19:44:30,065,1,"#000014D8","#000000C0","info ","MArcUpgrade","Download::AvailableSpace(): [209715200, -9457244]"

added every 2 seconds.



Rodion -> RE: GFI Mailarchiver Upgrade (6.Nov.2005 8:54:00 PM)

Hi All

We need to research each issue you experienced with upgrade tool. We encourage you to help us and submit compressed MArcUpgrade\DebugLogs folder with detailed issue description directly to josephde@gfi.com.

Also note that you can install MailArchiver3 on a separate machine and run Upgrade tool without configuring MailArchiver. Like this you can achieve "offline" functionality. The tool does not require licensing and will work with evaluation key



muellert -> RE: GFI Mailarchiver Upgrade (7.Nov.2005 4:24:00 AM)

My Mailarchiver Upgrade has been running from Friday afternoon to now (3 days) and its stuck at 426800 emails read out of 428725 (has been like this since yesterday).

So now what do I do? I can't leave this upgrade tool just sitting there doing nothing.



jonathanhaun -> RE: GFI Mailarchiver Upgrade (7.Nov.2005 4:37:00 AM)

It finally completed after 5 days and 10 restarts of the upgrade utility. This is the worst upgrade process I have ever experienced. An SQL DTS package would have been an great alternative to the MARC3 Upgrade utility..



muellert -> RE: GFI Mailarchiver Upgrade (7.Nov.2005 12:17:00 PM)

Had to restart it 4 times today.

This converter software is a very very slow. I sent in a email to tech support this morning with all my log files and no answer back.

Nothing like beta testing a release.. [Roll Eyes]



jfolsom -> RE: GFI Mailarchiver Upgrade (9.Nov.2005 6:08:00 PM)

We were having similar upgrade issues on a relatively small archive database (250K records) - the problem seems to be related to SQL's auto-sizing routine. Setting the new archive database size prior to performing the upgrade seemed to do the trick...I hastily read the MailArchiver upgrade documentation and missed the part where it is written to check the existing size of the old archive database and set the new database size accordingly. We run the archive database on a make-shift PC (Dell OptiPlex GX280, 1.8GHz P4) and, so far (knock on wood), it is averaging about 1,500 messages/min.

The initial setup routine is documented at the following link:

http://kbase.gfi.com/showarticle.asp?id=KBID002467

Don't know if this will help with the problem you're running into or not!



jfolsom -> RE: GFI Mailarchiver Upgrade (9.Nov.2005 6:26:00 PM)

Forgot to mention in my previous post - in our case, even before properly sizing the new database, the upgrade fiiinnnaaallly completed (started on Thurs 11/3, ended Thurs 11/10) after failing about a gazillion times. Unfortunately, the message count on the new db differed from the old db by a couple of hundred messages, so we decided to ditch the new database and re-try the upgrade process from scratch following the instructions that I posted in my previous post.

Don't know if this has been covered in another thread or not, but the upgrade utility creates a table in the old database called "CompletedIndexList" that logs which messages have been copied to the new database - this table had to be cleared so that our old messages were recognized as "transferrable" (since the process had already completed once, all messages were marked as having been archived and, consequently, the utility was not allowing us to re-run the upgrade process).

[ November 10, 2005, 12:31 AM: Message edited by: jfolsom ]



Kadee -> RE: GFI Mailarchiver Upgrade (9.Nov.2005 10:23:00 PM)

jfolsom,

Did the complete conversion run at the speed of 1500 or was the performance dropping again ?

All,

Was the speed problem solved for everyone by setting the database size ?

KD



jfolsom -> RE: GFI Mailarchiver Upgrade (10.Nov.2005 5:19:00 AM)

The process slowed to about 500 messages/min about an hour into the upgrade. This certainly is not "fast" by any stretch of the imagination, but since we're running the db on a relatively low-powered desktop machine, it's acceptable. It may be worth noting that we did not have to restart the upgrade process due to it getting "hung-up" (on our first pass, we were restarting every few hours).

Josh

[ November 10, 2005, 11:24 AM: Message edited by: jfolsom ]



Page: [1] 2   next >   >>