Hi everyone. I'd like to ask for your help guys.
At my job, we are currently starting to develop software. There are also other people not related to development who need to store information such as purchase records and scanned documents. Initially, we thought about a pair of redundant servers in order to protect information and increase service up-time.
Currently, we are hosting a customized version of bugzilla for attending work orders. This implies that we have the Apache and MySQL services running all the time. Additionally, this service instance is being moderately accessed by people in North and South America via high-speed intra net links so server load at a given time is not a critical factor.
We would like to put this little bugzilla instance on high availability by using a cluster. We would also like to setup a versioning repository for development projects. I initially suggested SubVersion, but I'm open to any other recommended content versioning system.
Finally, some order management folks would like to store information in an SQL server database instance. I still don't have much details on this so, put bluntly, I guess they still haven't figured out from their minds what they need
The key point that my manager is looking for is high-availability, fault-tolerance and redundancy.
I've got mainly these questions:
- What kind of server hardware do I need to set up such system? I believe I can get enough budget authorized for a moderately high Total Cost of Acquisition, so money shouldn't be a problem provided that my specs don't go overkill. Is it ok to go for server boxes, blade servers, NAS storage, etc? Which manufacturers offer good prices/support plans for this type of hardware and applications? Currently, my company tends to buy hardware from Dell or HP if it is of help.
- What kind of tweaks are needed to make the services (databases and repositories) aware of, and expose fault-tolerant functionality via redundant hardware? For example, I read that MySQL needs some kind of clustering extension in order to provide redundancy and HA.
- Most importantly, is there any way in which I could explain all of this in "manager speak", if you know what I mean? hehehe
I'm grateful for any help/references/tips you guys could provide on this.
At my job, we are currently starting to develop software. There are also other people not related to development who need to store information such as purchase records and scanned documents. Initially, we thought about a pair of redundant servers in order to protect information and increase service up-time.
Currently, we are hosting a customized version of bugzilla for attending work orders. This implies that we have the Apache and MySQL services running all the time. Additionally, this service instance is being moderately accessed by people in North and South America via high-speed intra net links so server load at a given time is not a critical factor.
We would like to put this little bugzilla instance on high availability by using a cluster. We would also like to setup a versioning repository for development projects. I initially suggested SubVersion, but I'm open to any other recommended content versioning system.
Finally, some order management folks would like to store information in an SQL server database instance. I still don't have much details on this so, put bluntly, I guess they still haven't figured out from their minds what they need
The key point that my manager is looking for is high-availability, fault-tolerance and redundancy.
I've got mainly these questions:
- What kind of server hardware do I need to set up such system? I believe I can get enough budget authorized for a moderately high Total Cost of Acquisition, so money shouldn't be a problem provided that my specs don't go overkill. Is it ok to go for server boxes, blade servers, NAS storage, etc? Which manufacturers offer good prices/support plans for this type of hardware and applications? Currently, my company tends to buy hardware from Dell or HP if it is of help.
- What kind of tweaks are needed to make the services (databases and repositories) aware of, and expose fault-tolerant functionality via redundant hardware? For example, I read that MySQL needs some kind of clustering extension in order to provide redundancy and HA.
- Most importantly, is there any way in which I could explain all of this in "manager speak", if you know what I mean?
heheheI'm grateful for any help/references/tips you guys could provide on this.
Facebook
Twitter