Are you disgusted or disappointed with your current web host? Have you switched web hosting fellowships too many times? Have you conception of hosting your own website(s)? Do you have the ambition to control and manage your own web server?
If you answered 'yes' to the questions above, then you may be ready to host your own sites. This narrative will give you things to consider while development the switch.
When being your own web host you should be technically inclined and have basic knowledge of operating systems, understand technical terms, understand how to setup a server environment (such as: Dns, Iis, Apache, etc.) have basic knowledge of scripting languages and databases (Php, Perl, MySql, etc.), be customary with current technologies, and have a basic understanding of hardware and server components.
You should perceive the pros & cons. It is one thing to say, you want to host your own web server and it is another thing to no ifs ands or buts do it.
Pros:
Own sense of accountability
Awareness level raised (you are at the frontline of all server happenings)
No monthly hosting fees/accounts
Incompetence no longer exist
Non-shared environment (dedicated server)
Unlimited websites, databases, content, storage, etc.
More bandwidth
No more waiting on someone else time
Complete control
Cons:
Exhausting at times
Faced with server/hardware problems
Isp firm account (monthly business/broadband expense)
If server goes down then the website is offline
No technical preserve team
Software, hardware, and network expenses
There could be many more pros & cons but I've pointed out some of the major ones. Managing a web server starts as a full time job, you must constantly monitor its operation and security. This can sometimes be an exhausting task, especially if you currently have other responsibilities. Though, the control you will have over your website and its operation is rewarding enough. You no longer have to wait for technical preserve or approval to install a script onto the server. You can have as many websites and databases you want, as long as your hardware can deal with it. You no longer have to go into the discussion forums and search for the best web host or rant about how much you hate your current host. You can even begin hosting family & friends personal websites.
Ask yourself, how technically advanced are you? Many times you do not have to be a tech guru or anything of the sort, but you must be very resourceful. You must know how to find resolutions and answers to problems, quickly and efficiently. This means you must be internet savvy. Not just the midpoint surfer, who surfs aimlessly, but you must be the surfer who can all the time find what they are looking for. This is key, because with any server environment you are going to run into problems and looking the answers are most terminated online, using multiple resources, search techniques, and engines. Sure you can hire someone to fix your problems, but as we should have learned from the "web hosting", having someone do it for you isn't all the time the best option. Here is a test to see if you are ready to find solutions. I need a clarification to a Microsoft Windows 2003 Server Event Error - "Event Id: 1056" it's a Dhcp Server Error. How would you search? Go ahead find the solution.
Did you first go to Google? If you did, that was a nice attempt and coarse for most, plus a good place to start, but regularly it is best to start at the developers' website. In this case "microsoft.com" would have been the first option. Why? Google would more than likely provide you with the talk from Microsoft and other sources, but you don't want to get inaccurate data from other sources. It is coarse to get data from Microsoft that would not specifically conclude your problem, but the developer should all the time be your first place to search for the answers. Now search the error again and go to the Microsoft site and find the solution.
You should had found this (Event Id 1056 is Logged after installing Dhcp)
What search phrase did you use? It should have been Event Id: 1056, because the Event Id is the exact error, it pinpoints your exact problem without broadening your search. Sometimes the error narrative is also approved to search, just the error narrative by itself or in aggregate with the Event Id. It depends on your error, your search feedback, your ability, and technique. For this example I did not include the error description.
Google or Yahoo! should have been your second selection (the two largest search engines). Then search other smaller and niche search engines. A good search site which makes use of Google's operator tags is http://www.soople.com Next you should search within forums and discussion groups. If you are pretty internet savvy and have a plentiful or few forums and discussion groups which you frequent then you might no ifs ands or buts visit those places before visiting Google or Yahoo!. You can even visit those before visiting the developer site since it is a trusted source, but I wouldn't propose it, I still would go to the developers' site first. Okay, so now we have planted our feet and have familiarized ourselves with being internet (search) savvy. We are ready to buy a server!
When development a server buy you need to consider a few things before doing so. What to buy? A top of the line, quadruple processor, and super fast turbo server is all the time ideal, but many times it is not logical or affordable. Therefore, you need to weigh your options (sensibly).
What to buy?
First conclude your budget. Be realistic and expect to spend at least ,500 for a low-end server. For a low-end, ability server with other needed tool and services I spent a limited over ,500 easily.
Determine your Isp (broadband) provider. Study and speak with several separate vendors before choosing which broadband clarification best suit your needs. Each provider plan is separate and has separate benefits, conclude the best one which fits your needs. Bandwidth should be put into observation when choosing your Isp.
A backup gismo should be purchased before implementing a server install. The backup gismo should be duplicate the server warehouse space. This could be a standalone unit like an external hard drive or network warehouse gismo or the backup gismo could be multiple devices such as: backup tapes, disc, etc. The presume the backup gismo should be larger is because you want to be able to have months worth of backups and not just weekly or monthly backups. You should have at least 24 weeks of backups without the concern of warehouse space. The backup gismo or safe deposits should also be external, removable, and portable. This is so the backups can be stored in a remote location. regularly for safe-keeping, in event of a theft or disaster.
Determine your daily traffic goal (the daily traffic which you hope to see within 1 year - be realistic), divide that amount by the daily traffic you currently receive, and then multiply that amount by 5. That is the total amount of Gb space you need.
Example:
Daily Traffic Goal: 10,000 (Divided by) Current Daily Traffic: 500 (Times X) 5 = 100Gb
In the example you should buy a 100Gb Hard Drive, it is best to buy 2 or more drives oppose to 1. In this case, since 50Gb drives do not exist or harder to find, you would buy two 60Gb drives giving you a total of 120Gb. 2 or more drives are regularly needed in a server to configure the proper Raid option, in some cases 3 or more are needed. Your backup warehouse space should be a minimum capacity of 200Gb (or 240Gb, optional).
Determine your memory. If your web server daily traffic goal is 500,000 then I would propose at least 2Gb worth of memory. If it is a shared server, meaning it also has other server services running on the machine, especially a mail server or database server (which is not recommended) then your memory should at least be 3Gb or more. Otherwise you can think small and upgrade as needed, a 1Gb memory stick should be fine for starters.
Determine your network components, which Nic card best performs under high traffic levels and which router best performs for your Lan / web server. It is best to get a router which has a built-in firewall (commonly known as a "hardware firewall"). Your Isp may provide you with a router or hardware firewall, this is how they are able to authorize your traffic on their network. Like a cable box does for cable television. The router also shares your Ip address with other clients on your network. This enables you to share your internet relationship without having to get a separate Ip from your Isp. The hardware firewall is plainly a router with a built-in firewall, which means it shares your Ip address as well as provides added protection to your network. It blocks bad addresses and ports at the forefront, before it can even make it to your computer. It is not recommended to rely only on a hardware firewall for security, this is just the first step. It is recommended to also include a software firewall (firewall software which installs on your computer) and it is recommended to continue timely protection practices, such as updating and patching your ideas on a scheduled routine.
Determine your processor speed and power. Regardless of the amount of traffic you are expecting I would propose a dual processor or greater. A dual processor or greater is best because if your website unexpectedly take off then you will be well ready and if you host other server options or websites on the same server then you will have best performance. At the time of this writing the 64-bit platform is the processor direction. 3.8Ghz is the most ready speed. If your pockets can afford the latest technologies then that is ideal, but keep in mind at this singular time a 64-bit compatible processor is not necessary, without having many applications that want or deliver on that platform. That is a lot of speed going no where fast. Also, remember the power of the 64-bit platform and the greater the processor speed the more heat it produces, therefore it must be cooled much more rapidly and efficiently. At this time a dual 32-bit, 2.8Ghz - 3.2Ghz processor will suffice (even that is way more than enough). Though, if your pockets can afford it then the latest and greatest would be fine, you will be well prepared. Otherwise, do like most population and upgrade when the time comes.
Make sure you have a Cd/Rw drive. A floppy disk drive is not needed, but I do propose it for development ideas restore disk. The Cd/Rw drive is needed because you need some type of movable warehouse device. You never know when you need to install a driver from a separate location...like a ethernet driver. An external Cd/Rw drive is the best option, especially if you have multiple machines.
Choose your operating ideas carefully. Choose the vendor which you are most comfortable with. Do not Choose a Mac if you never used a Mac before. Just because your friend suggests it and says it is a piece of cake does not mean it will be for you. You are trying to get a web server online not re-learn a whole new system. Stay focused and grounded. If you are comfortable with Microsoft then go with Microsoft, regardless if the It someone at your job says Microsoft products are unsecure, Linux or Unix is more obtain and much best for a web server. If you have never used Linux or (especially) Unix then you will be in for a ride of your life. Your web server perceive will soon become a horror and you will have wasted thousands of dollars on equipment. Go with what you know, not what you are told. Each platform has its pros and cons: Microsoft is the user-friendly of them all; Mac is the web/graphic developer of them all; Linux is the open-source/developers paradise of them all; Unix is the most obtain of them all. Each of them can be tweaked in ways to provide a solid, ability platform, it is best to stick with what you already know.
You should install on your ideas all the web services (such as: Apache, Iis, etc.), applications (such as: backup gismo software, Raid (Array) Manager), scripting languages (such as: Php, Perl, etc.), Cgi, Database (such as: MySql, Microsoft Sql, etc.), and a web log analyzer (such as: weblog expert, nihuo, etc.). It is also recommended to accomplish ideas updates, protection patches, and firewall installs and configurations. It is sometimes best to leave the protection installs and configurations for after you have the ideas functioning properly to avoid any uncalculated problems. This way when you install the firewall and something stops working properly like connecting to your website from face your network, you can troubleshoot assuming that it is the firewall, therefore you would begin by chance port 80 on the firewall. This formula can save you a lot of hassle, but can sometimes be considered the unsecure method, especially if you don't have a hardware firewall already in place.
Next, there are a few things to consider before installing and configuring a server. Where to put it? A secluded, cool location is ideal, but if this cannot be terminated then adjustments can be made.
Where to put it?
Locate a location within your home that is static-free, we do not want to put the server on the carpet, near curtains, or anything else that can produce a static reaction. The presume for this is that you do not want the server internal components to receive a static fee and short circuit.
The location should be a cool environment, preferably below room temperature. The presume for a cool area is because servers (as well as desktop computers) produce large amounts of heat, the more heat it produces the more it needs to cool off. If the server is not kept cool, then this can lead to the server hanging and then finally crashing. It's the same supervene of when a car overheats, it stops running. You can keep a server internal components cool by retention the room cool, additionally you can add more fans to the server which cools the server internal components, you can also position a standalone fan directly at the server back panel and constantly have the fan cool the server internal components. Depending on how cool your room is and how much heat your server produces, getting more fans for your server may be a must and not an option.
It is recommend that the server is at a higher level within your house (mid-floor), because if it is in the basement and a flood occurs it could ruin it. If it is in the attic and the sun beams on the attic for hours the server could overheat. Mid-floor level is regularly the cooler place within the home, but these recommendations is optional and you should put the server in the most comfortable and favorable space following the rest of the guidelines.
Be sure the area you Choose is not damp or wet (no leaks, moisture, near any liquids, or near a window "especially open"). We all know what can happen when electrical components get wet.
The server should sit at least 4" inches from the ground
Be sure a working electrical outlet is near. It is an foremost to have a power supply, a good brand is Apc. Having a power provide can save you from electrical outages, blackouts, and brownouts. Having a power provide helps the server keep its power, remain stable, and unaffected when there is an outage, as well it protects your server against electrical shock. If your outage remains more than 5 minutes it is recommended to begin backing up anything deemed foremost and shut the computer down voluntarily as well as any other electrical attached devices.
Have a Lan line near and also a phone jack (if you plan on using the server for any dial-up services). It is not recommended to use your web service with a dial-up connection. A broadband relationship or greater is propose for optimal performance. The Lan line should never come from your wall and plug directly into your server, it should plug into a hardware firewall (usually a router with a built-in firewall).
Depending on the size of the server and the internal components the server may be very noisy and loud, especially with the fans going. It is recommend to have the server in a secluded location which is not near any peaceful area of the house, such as: bedroom.
Those are all some basic things to consider before hosting your own server. Hosting your own server is not an easy task, but once you have had some time and perceive with it, it becomes a breeze. You will have a best web hosting experience, you will be more in tune and reliant to your customers, and you will gain greater technical aptitude. Hosting your own web server is rewarding, useful, and gives you the chance to host unlimited websites, databases, services, etc.
If your web traffic becomes too great for your server then it is recommended to Choose an offsite web host. It is propose to buy a dedicated server with a ability web host. If you Choose a server with the above recommendations then your server traffic should be fine for at least up to 25,000,000 page views per month. It could be greater or less depending on your operating system, your server configuration, performance, applications, and services. The point is you should be well in a position to buy dedicated server space by the time your traffic gets too high, because if you are getting anything close to 1,000,000 page views a month you should have some competitive advertising or ecommerce income. And plus, with the knowledge you will gain from the perceive you will be able to preserve your own server at a dedicated server (remote) location, thus cutting more overhead.
The biggest disadvantage of hosting your own web server is the uptime reliability. If your web server powers down for any presume then your website is offline. regularly web hosting fellowships have methods and networks to forestall this failure from affecting your website. regularly if the ideas goes down they have a mirror location where your site is rejuvenated and doesn't perceive much downtime. Some web hosts do not practice this formula or any other fault tolerance. Imagine if a blackout or power outage occurs, then your web server could be down for hours or even days, this can influence your firm greatly. There are some hosting fellowships who provide mirror web hosting for a small fee, I haven't found one that is dependable yet. Or you could cross your fingers and hope for the best, until you are able to host your server face your home on a larger network.
Hosting your own server regularly is not a money-saving experience. It sometimes cost more to host your own server, when you total the up keep and maintenance. The advantage of hosting your own server is regularly a best platform for your customers, because it is no longer a shared server and it gives you the ability to make global changes approximately instantaneously. When your customers invite more operation or specific applications, then you will be able to implement this immediately. Customers like to know that you are in control. If you tell your customers that the server will be down for maintenance from 6 a.m. - 7 a.m. Then it would be best if that is when your server is down, not from 5 a.m. - 10 a.m. You know how your web host will tell you one thing and then you have to try explaining it to your customer. In the end it will advantage you to host your own web server as a web business, this helps you and your customers.
Mail Server Host
No comments:
Post a Comment