chris.smouse replied on Wed, Sep 30 2009 4:31 PM

rated by 0 users

Hi wwiley -

Just to verify - are you upgrading from a previous VoIP install (what version?) or are you a new IP SLA Manager customer?

We are aware that upgrading to 3.0 can take a long time when upgrading a large VoIP database.  But, it is expected that the progress bar does not move during the upgrade itself, while it is doing VoIP database migration.

One more question - assuming you're an existing customer, have you been monitoring a lot of Cisco Call Managers (CCM)?  If so, we added a couple of indexes for CCM data to improve performance in 3.0.  This has the unfortunate side effect of extending the upgrade time while the indexes are added.

Hope this helps!

Chris

wwiley replied on Wed, Sep 30 2009 10:11 PM

rated by 0 users

Chris,

Thanks for your reply.  Yes I am upgrading from a previous VoIP install.  We were monitoring 3 CCM servers and approximately 25-30 VoIP nodes.  I left the upgrade to run overnight and just checked on it.  6 hours and it is still running...

wwiley replied on Thu, Oct 1 2009 7:17 AM

rated by 0 users

15 hours now and no further progress...

chris.smouse replied on Thu, Oct 1 2009 9:26 AM

rated by 0 users

wwiley -

Sorry to hear about this.  Are there other processes running against your VoIP database that might be competing with the database migration step of the config wizard?  Examples include: an additional installation of VoIP, SolarWinds services or other external process that might be reading/writing from the database?

If not, please submit a support ticket for this issue and reference this thwack thread.

Thanks.

wwiley replied on Thu, Oct 1 2009 10:21 AM

rated by 0 users

I already had a case open from yesterday.  I called Support this morning and while talking to the gentleman I made an astonishing discovery.  My database which was running 69GB with a 4GB log file had EXPLODED to 165GB with a 95GB log file after installing IPSLA.  Long story short, I made the decision to cut and run.  My NPM environment had been down for over 20 hours and created a serious disk space issue on my production SQL environment not to mention the lapse in monitoring.  I provided a diag file to Support this morning and then restored my database to a point prior to the IPSLA installation, uninstalled IPSLA and I am back in business.  The database is back to 69GB with a 4GB log file.

I have had issues with my NPM database growing exponentially over the past few months, but Support determined it was related to NetFlow.  Since I have disabled NetFlow and am awaiting a fix from Support / Development.  It would seem to me that there is an issue with SQL.  We run many other applications with a SQL backend and have never seen a DB grow 100GB in less than 24 hours.

At this point I do not intend to reinstall IPSLA until Support comes back with an explanation of what has occurred and what the resolution is and can assure me it will not crater my SQL server.  I am more than happy to provide a backup of my NetPerfMon DB to Support or Dev for testing if needed.

chris.smouse replied on Thu, Oct 1 2009 10:46 AM

rated by 0 users

wwiley -

It would be fantastic if you can provide a backup of your NetPerfMon DB.  Please submit this through the support ticket you already have open.

Thanks.

macnugetz replied on Thu, Oct 1 2009 10:49 AM

rated by 0 users

Thanks for the additional information.  Support and Development are actively investigating this issue.  We will keep you posted.

wwiley replied on Thu, Oct 1 2009 12:31 PM

rated by 0 users

What is the file size limitation for LeapFile?

Jason Ferree replied on Thu, Oct 1 2009 12:51 PM

rated by 0 users

2 gig

wwiley replied on Thu, Oct 1 2009 12:54 PM

rated by 0 users

I would like to get you guys a backup of my NetPerfMon database which averages 16-17GB per backup.  What are my options?

derhally replied on Thu, Oct 1 2009 3:37 PM

rated by 0 users

You have a couple of options.  You can export all tables prefixed with Voip to a temporary database and send the backup, or you can use the bcp utility as such

bcp <dbName>.[dbo].[VoipLinks] out VoipLinks.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipLinkTestResults] out VoipLinkTestResults.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipSimulationNodes] out VoipSimulationNodes.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipSites] out VoipSites.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipTest] out VoipTest.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipTestInstance] out VoipTestInstance.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipTestType] out VoipTestType.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipUdpJitterResultDetails_Daily] out VoipUdpJitterResultDetails_Daily.out -S<server> -T -c -U<username> -P<password>

bcp <dbName>.[dbo].[VoipUdpJitterResultDetails_Detail] out VoipUdpJitterResultDetails_Detail.out -S<server> -T -c -U<username> -P<password>

You will need replace <dbName> with your databasename, <server> with your Sql server address, and username and password for <username> and <password>

You can do this all in a temporary folder and then zip it up.  Should compress pretty nicely.

MarieB replied on Mon, Oct 5 2009 9:52 AM

rated by 0 users

WWiley--

Did you get this installed/working? Hope so.

Thanks,

M

wwiley replied on Mon, Oct 5 2009 1:37 PM

rated by 0 users

Not yet... have a Support case open.

Ovad replied on Wed, Nov 4 2009 9:17 AM

rated by 0 users

I have same issue, since I could not get down time I created a copy of the server and installed v3 there the configuration wizard completed after 6 hours without errors but I can't get any views from the voip modules its reporting an error The "VoIP Sites Overview " resource threw an exception..
Specified cast is not valid.

I was lucky not doing it on the production server or I would lose all data and voip monitoring capabilities.

btw - if you want to go back to v2.1 you must delete teh nodeID column from teh VoipSites table as it being added by v.3 but not required by 2.1