I'm designing a server for a small group of loan officers (3). So it is not going to be very intensive the traffic, but they do want it to be really reliable.
Any suggestions? Even general comments about srver's hardware are welcome.
![]()
Thanks
I'm designing a server for a small group of loan officers (3). So it is not going to be very intensive the traffic, but they do want it to be really reliable.
Any suggestions? Even general comments about srver's hardware are welcome.
![]()
Thanks
You would find this discussion interesting and helpful, too.Originally Posted by nsilva
HTH.
Regards,
Can I ask you, just what your role is, in regards to those 3 loan officers?
I'll kinda get to my ultimate point.
With HAVING a server also comes a fairly large responsibility AND expense for that matter.
That responsbility is the management, maintenance, and upkeep of the server.. In one word 'administration'.
Not only to have a 'reliable' server but adequate redundancy and archival of the servers data (I'm inferring very regular backups utilizing a revolving backup system) of which takes the manpower (money) of an EXPERIENCED and competant system administrator..
To be quite honest, IF all the LO's are going to do with such 'server' is use it for Sugar, I would personally say that the purchase of a server by them is a mistake, and would continue to be a constantly frustrating and costly mistake at that with the regular problems that arise and/or required administration and upkeep of the server.
Such types of users are MUCH better off utilizing some commercial web host.
On another topic though, and be forewarned, I'm more familiar with the lending industry that you might be able to imagine..
Their own server would be a valuable tool/assett if utilized to run Asterisk as well. Asterisk combined with Sugar and a toll-free DID make for a nice combination.
I only mention these details in order to try and help.. From the opposite perspective, if you're just the guy to sell them (the three LO's) some 'server' (computer) of which they try to use and implement SugarCRM on....well...they'll end up targeting all of their blame on you and/or the server with each and every future trouble(s) in which they experience..
And though such troubles are nothing more than regular server administration, the LO's won't be able to make that distinction and will associate normal administrative tasks as being problems of which they direct the blame for such... in your direction..
Hope the suggestions help
Last edited by chrisky; 2007-03-26 at 02:26 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks