nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Experiences with 8.1 running on 64-bit OS

InformationGatherer

I'm considering moving my ORION instance from a 32-bit and leveraging the 8.1 ability to run on 64-bit OS. Does anyone have any experience with this to date? I know its early in the release, but any feedback would be greatly appreciated.

Find more posts tagged with

64-bit

Accepted answers

All comments

vhcato

I'm curious about this as well.

vhcato

BUMP...

There seems to be a number of folks on the forum who are now running v8.1. Has anyone yet tried v8.1 with the 64-bit version of Win 2003? If so, would you please share your experiences?

Thanks.

rkawell

I installed 8.1 today on 2003 x64 dual core sun x4100. The install went pretty smooth, with the exception of the SQL. I needed to install the 64 bit application. I am currently monitoring 93 nodes and 849 interfaces. No issues at this point, and it seems to be running fast, at least faster than the old crappy dell server.

Also, I installed Cirrus and the engineers tool set with no issues so far too.

vhcato

I installed 8.1 today on 2003 x64 dual core sun x4100. The install went pretty smooth, with the exception of the SQL. I needed to install the 64 bit application. I am currently monitoring 93 nodes and 849 interfaces. No issues at this point, and it seems to be running fast, at least faster than the old crappy dell server.

Thanks for the feedback. With regard to your statement about SQL, I assume this is due to the fact that you are running your DB on the same server..? I imagine it wouldn't matter if your DB was housed on a different server..?

FormerMember

While we're discussing 64 bit- BUMP for any updates on the x64 bit version of the Orion Event Log forwarder..

FormerMember

It's something we're considering for the future, but it's not imminent.

a1ex

We've had Orion 8.1 running on x64 2003 for a few weeks without any major issues.

A couple of days ago the syslog service chewed through about 2GB of ram and really slowed the box down.

Process had to be killed rather than restarted but we've not seen any problems since.

We're using an external SQL server so it's just Orion on the box.

We have had problems running the toolset on the box though as the launcher just crashes on startup.

vhcato

We have had problems running the toolset on the box though as the launcher just crashes on startup.

Thanks for the feedback. Also, I don't believe the Toolset is yet supported on x64.

FormerMember

To bring this back-

We have a few servers in production running 2003 x64 Enterprise with SQL 2005 x64 Enterprise...one in particular is loaded with 16GB of RAM. Now, I don't know enough about memory allocation and SQL server etc as I would like but still, something doesn't seem right here.

We had a "process" that would lock users at the same time every day...upon doing some research, it was found to be caused by something with the x64. Once it was disabled, the users did not get locked up...BUT now the memory being reported by Orion is all weird. It is showing only 180MB of memory being used by SQL Server and only 400MB being in use total. Now I don't know enough about memory allocation and SQL Server etc- but still, as soon as we made the change, something went weird. It's almost like SQL is not reporting memory usage...

I don't remember exactly what the change was, but I will try to find it.

FormerMember

What we changed was to allow locked pages into memory- as seen here:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;918483

After doing so, the reported memory on this server changed dramatically. Just FYI-

vhcato

Thanks Jrutski. Are you looking at Windows Task Manager? I've seen issues in the past where Task Manager doesn't accurately represent memory usage for SQL instances, particularly if you have the instance configured to use more than 2GB of RAM.