Wiki 24x7servermanagement - User contributions [en]

Main Page

2018-07-16T10:04:23Z

Jayant:

= Welcome to 24x7 Server Management Wiki ! =

24x7 Server Management wiki is created to explore more aspects of various technical concepts, their overviews, and the other stuffs, which are often overlooked.. This is an effort to explain things the right way as much as possible...


= Our Aim =
<center>'''" The only source of Knowledge is Experience…"''' </center>

# To put years of experience and practical knowledge in a theoretical fashion..
# To bring forth information on various concepts on widely-searched subjects..
# To open discussion on various technologies to understand the subject in a simple way..
# To develop a community to contribute on subjects and open their views for all..
 

As being Systems Administrator, we have to do continuous research on new things for the better advancement in our services and technological approaches. The information is out there on the Internet to be taken, but not all are appropriate to answers our questions that arises from the study and we have to spend hours to find those answers. We know how time is valuable and We came up with an idea of developing a "wiki" that would only focus on these stuffs rather more extensively. But being a wiki, will need help from everyone interested, so we are open to discussion on this...


[[File:cPanel.png|250px]]
[[File:Plesk.png|250px]]
[[File:SolusVM.png|250px]]
[[File:Virtualizor.png|250px]]
[[File:Xen.png|250px]]
[[File:OpenVZ.png|250px]]
[[File:kvm.png|250px]]

= =
{| class="wikitable sortable collapsible"
|+Catalogue 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 25%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 80%; height:6px; color:White" | Description
|-valign="middle"
| [[Server Management]] || What is server management and things you should look for before you hire them to do the job for you..
|-
| [[IP Reputation]] || What is IP reputation and how does it affect the mail server..
|-valign="middle"
| [[IP delisting ]] || How to delist IP address if they are blacklisted..
|-valign="middle"
| [[How Does A Web Server Works|Web Server Functioning]] || How do you get the information you are seeking.
|-valign="middle"
| [[WordPress Security-I]] || Importance of WordPress Security and understanding the security issues..
|-valign="middle"
| [[WordPress Security-II]] || Preventive measures on WordPress Security and improvisation in the security..
|-valign="middle"
| [[Phishing]] || What is Phishing? and what are the most common types? Be aware of those..
|-valign="middle"
| [[Spamming]] || What are spam? How do they work? What are they categories?
|-valign="middle"
|}

{| class="wikitable sortable collapsible"
|+Infrastructure Management 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 26%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 75%; height:6px; color:White" | Description
|-valign="middle"
| [[Load Balancing]] || What is load balancing and what are the different type of load balancing architectures available ?
|-
|}

See '''Other<big>[[Articles|Articles Catalogue]]</big>''' here

Main Page

2018-07-16T10:03:20Z

Jayant:

= Welcome to 24x7 Server Management Wiki ! =

24x7 Server Management wiki is created to explore more aspects of various technical concepts, their overviews, and the other stuffs, which are often overlooked.. This is an effort to explain things the right way as much as possible...


= Our Aim =
<center>'''" The only source of Knowledge is Experience…"''' </center>

# To put years of experience and practical knowledge in a theoretical fashion..
# To bring forth information on various concepts on widely-searched subjects..
# To open discussion on various technologies to understand the subject in a simple way..
# To develop a community to contribute on subjects and open their views for all..
 

As being Systems Administrator, we have to do continuous research on new things for the better advancement in our services and technological approaches. The information is out there on the Internet to be taken, but not all are appropriate to answers our questions that arises from the study and we have to spend hours to find those answers. We know how time is valuable and We came up with an idea of developing a "wiki" that would only focus on these stuffs rather more extensively. But being a wiki, will need help from everyone interested, so we are open to discussion on this...


[[File:cPanel.png|250px]]
[[File:Plesk.png|250px]]
[[File:SolusVM.png|250px]]
[[File:Virtualizor.png|250px]]
[[File:Xen.png|250px]]
[[File:OpenVZ.png|250px]]
[[File:kvm.png|250px]]

= =
{| class="wikitable sortable collapsible"
|+Catalogue 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 25%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 80%; height:6px; color:White" | Description
|-valign="middle"
| [[Server Management]] || What is server management and things you should look for before you hire them to do the job for you..
|-
| [[IP Reputation]] || What is IP reputation and how does it affect the mail server..
|-valign="middle"
| [[IP delisting ]] || How to delist IP address if they are blacklisted..
|-valign="middle"
| [[How Does A Web Server Works|Web Server Functioning]] || How do you get the information you are seeking.
|-valign="middle"
| [[WordPress Security-I]] || Importance of WordPress Security and understanding the security issues..
|-valign="middle"
| [[WordPress Security-II]] || Preventive measures on WordPress Security and improvisation in the security..
|-valign="middle"
| [[Phishing]] || What is Phishing? and what are the most common types? Be aware of those..
|-valign="middle"
| [[Spamming]] || What are spam? How do they work? What are they categories?
|-valign="middle"
|}

{| class="wikitable sortable collapsible"
|+Infrastructure Management 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 26%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 75%; height:6px; color:White" | Description
|-valign="middle"
| [[Load Balancing]] || What is load balancing and what are the different type of load balancing architectures available ?
|-
|}

<iframe width="1000" height="100" src="flash banner images/728x90/728x90.html" frameborder="0" allowfullscreen></iframe>

See '''Other<big>[[Articles|Articles Catalogue]]</big>''' here

Nginx Web Server

2017-12-08T06:51:47Z

Jayant: Jayant moved page Nginx to Nginx Web Server

= ''' About NGINX ''' =


It is an open source web server software designed for load balancing, reverse proxying, HTTP caching, and media streaming. It was designed for maximum stability and performance with low memory footprints. NGINX uses architecture that is more event driven, which requires less memory footprint than a traditional process driven one.


= ''' Goal behind developing NGINX:''' =


Each connection by a client was handled as a separate thread or a process and with overtime increase in the traffic to the server, the connection rate increased, and the serving capacity was affected. In the backend, additional memory consumption was seen with process spawning that required switching the CPU to a new task from an old one, thus memory and CPU utilization both were high. NGINX was designed to achieve high performance, to give better utilization of the server hardware resource that can scale up with ever increasing need of web hosting..



='''Features of the NGINX:'''=

# Capacity to handle more than 10,000 simultaneous connections with a low memory footprint.
# Handling of static files, index files, and auto-indexing.
# Reverse proxy with caching.
# Load balancing.
# It has FastCGI support with caching.
# IPv6-compatible.

NGINX is the most popular '''modular''', '''event driven''', '''asynchronous''', '''single-threaded''' web servers. We will see what these all terms mean one by one.

In this article, you may have came across a term called '''event driven''' and would be wondering what is it? Well, it is a unique approach made to handle tasks as events. The incoming connection, the disk reads, etc are all events.. Operating systems intimates when the task is started and when it is completed. NGINX worker makes proper utilization of these resources, so the resources can be utilized and released on demand as a result you will see better usage of CPU and memory.. Each worker process of the NGINX has the capacity to serve thousands of requests and connections per second.. It does not create new process for every new connection instead the worker attends the new request from queue and executes runloop on it giving the worker the capacity to process multiple connections per worker..

The runloop that NGINX starts does not hang or get stuck on particular events, this is what we called as '''asynchronous'''.. It creates alarms from the system for particular event(s) and monitors the queue for those alarms.. Once it seems the alarm, NGINX runloop triggers the action. This is how NGINX utilizes the shared resources on the server in an efficient method.

'''Single threaded''' means a single worker can handle many user connections, which lowers the utilization of resources during context switching that requires CPU utilization.

NGINX uses event notifications and appoints specific tasks for separate processes altogether. Connections are efficiently operated in a run-loop for some limited single-threaded processes that are called as workers. Each NGINX worker can handle as many as thousands of concurrent requests and connections per second.
The NGINX worker code is comprised of core and functional modules. The core is responsible to maintain proper runloop. Modules comprises of application layer functionality. The modular architecture facilitates the developers to extend the set of features for the web server, keeping the core untouched..



='''NGINX Architecture:'''=
[[File:NGINX.png|800x600px|center|Nginx]]

='''How Does NGINX Work?'''=


NGINX uses a conventional process:

The master process performs the privileged task like port bindings, reading the configuration, and then it starts creating a small number of child processes like the below 3 types.

'''Cache loader:''' This process executes at start and loads the disk-based cache into the memory, and then closes. This scheduling saves the resources that it may require if it does not exit.

'''Cache manager:''' This process runs sporadically and reduces entries from the disk caches to maintain the configured sizes.

'''Worker processes:''' This is the process that performs all of the major work. It handles reads the disk, write to the disk, handles the network connections, and communicates with upstream the server if configured as revere proxy.



='''Summary:'''=

'''Master:'''
* Monitors the workers.
* Handles all the signals and notifies it to the workers like reconfiguration or update, etc.

'''Worker:'''
* It responds to the client query.
* Get the commands from the master.



I hope this has been informative to you and I would like to thank you for reading..

Nginx

2017-12-08T06:51:47Z

Jayant: Jayant moved page Nginx to Nginx Web Server

#REDIRECT [[Nginx Web Server]]

Nginx Web Server

2017-11-30T14:31:16Z

Jayant: Protected "Nginx" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

Load Balancing

2017-11-30T14:27:42Z

Jayant:

= ''' What is load balancing ?''' =


Load balancing is an effective way of distributing traffic across group of servers in the backend.. We can also refer these group of backend servers as server pool or server farm.. Load balancing can also be seen in the real life situation too.. You must be confused, let me put it in simple with an example of a joint family where there are more helping hands who work and shares their responsibilities to take care of their loves ones, so the load is distributed among them..


= ''' Why is Server Load Balancing necessary?''' =


Server load balancing becomes necessary in situations where there is high traffic on a server than the server can serve. This may be because of the hardware limitation, so load balancing becomes first choice to put a similar of same or higher configuration parallel to the current server and shape the traffic to it, so the traffic is distributed among them..

'''Real-Life examples''':

A family of more members and only one person who works to fulfill the daily needs of the family member. There will be situation when one person's income will not be sufficient for some needs and the family has to compromise on it, however, if another person of the same family starts working, this will take some pressure off from the first person who was working alone for years.. this is nothing but load balancing and now since one more member added to the working member list, the quality of life the family requires can be fulfilled.. Similarly, one server with high number of requests cannot give you the quality of service you are seek at times and the result of this will be that you start losing traffic because of unavailability of service when the user wanted and with load balancing, you will have another server in place to serve those requests which one server was not able to handle on time, i.e., distributed load, so your client's will always get your service when they require, no matter how many users are connected to you at the same time.

If you have a shopping website where you have thousands of products for sale and users coming to your website, ordering the stuff will generate revenue for you and will be the source of income for you.. You will require more and more users to come and shop to increase your earnings and for this, you upgrading your server all the time may not be possible, as it will be considered as ever growing stuff.. One day or the other, you will find your server not capable of serving high requests since your client's did not get to you when they wanted and moved to another shopping site. A web server should always be ready to serve the requests to avoid users going elsewhere because of your server not serving them. Putting such websites on a load balancer infrastructure will make sure that all the requests coming will be serve either by one server or the other, but it will not drop it..

Now, let us know how the load balancing is done and what the different models that can be implemented, of course we can customize it as per our need, but that is based on your requirements..


='''Load Balancing Models'''=

'''Load Balancing Model - 1:''' This is the most standard model available to implement where there are 2 web servers and 1 database server to serve in your infrastructure.. Your server is connected to a load balancer, which will be the first point of contact for your users and the load balancer will then decide where to send the requests based on the configuration we do in it.. Now, the load balancer can be a service from a third-party provider or you can have an independent server or a VPS also.. This is the most effective load balancing scenario, of course, you can customize it to give you more power, but this is the basic one to start with.. Later on if you want you can add in web server and database servers if warranted..

[[File:LoadBalancing-1.png|800x600px|center|Load Balancing Model - 1]]

Users on the Internet connect to your website, your website points to your load balancer IP address. Now, the load balancer will take the user's request and then check its algorithms and then decide what it has to do with the request whether to send it to Server A or Server B.. Now, at this point in time a question may have arrived in your mind if you would have been carefully reading this section of the article, if I said that the load balancer will be sending out the request to the Server A and Server B, what is Server B is down at the very moment? What will happen, will my user lose the connection? then what is the user of load balancer? Cool down buddy, you may be getting carried away.. Let me answer you, load balancer (if configured) does a small check of server availability before it sends in a request to it, so none of your users requests are going to offline server, only the online server will serve it.. This must be satisfying to you now, isn't it.. Once the request reaches the online server, it does process it, sends it to the Database Server, gets it back to same server, to the client back..



I hope this has been informative to you and I would like to thank you for reading..

Load Balancing

2017-11-30T14:26:54Z

Jayant:

''' What is load balancing ?''' 


Load balancing is an effective way of distributing traffic across group of servers in the backend.. We can also refer these group of backend servers as server pool or server farm.. Load balancing can also be seen in the real life situation too.. You must be confused, let me put it in simple with an example of a joint family where there are more helping hands who work and shares their responsibilities to take care of their loves ones, so the load is distributed among them..


 ''' Why is Server Load Balancing necessary?''' 


Server load balancing becomes necessary in situations where there is high traffic on a server than the server can serve. This may be because of the hardware limitation, so load balancing becomes first choice to put a similar of same or higher configuration parallel to the current server and shape the traffic to it, so the traffic is distributed among them..

'''Real-Life examples''':

A family of more members and only one person who works to fulfill the daily needs of the family member. There will be situation when one person's income will not be sufficient for some needs and the family has to compromise on it, however, if another person of the same family starts working, this will take some pressure off from the first person who was working alone for years.. this is nothing but load balancing and now since one more member added to the working member list, the quality of life the family requires can be fulfilled.. Similarly, one server with high number of requests cannot give you the quality of service you are seek at times and the result of this will be that you start losing traffic because of unavailability of service when the user wanted and with load balancing, you will have another server in place to serve those requests which one server was not able to handle on time, i.e., distributed load, so your client's will always get your service when they require, no matter how many users are connected to you at the same time.

If you have a shopping website where you have thousands of products for sale and users coming to your website, ordering the stuff will generate revenue for you and will be the source of income for you.. You will require more and more users to come and shop to increase your earnings and for this, you upgrading your server all the time may not be possible, as it will be considered as ever growing stuff.. One day or the other, you will find your server not capable of serving high requests since your client's did not get to you when they wanted and moved to another shopping site. A web server should always be ready to serve the requests to avoid users going elsewhere because of your server not serving them. Putting such websites on a load balancer infrastructure will make sure that all the requests coming will be serve either by one server or the other, but it will not drop it..

Now, let us know how the load balancing is done and what the different models that can be implemented, of course we can customize it as per our need, but that is based on your requirements..


='''Load Balancing Models'''=

'''Load Balancing Model - 1:''' This is the most standard model available to implement where there are 2 web servers and 1 database server to serve in your infrastructure.. Your server is connected to a load balancer, which will be the first point of contact for your users and the load balancer will then decide where to send the requests based on the configuration we do in it.. Now, the load balancer can be a service from a third-party provider or you can have an independent server or a VPS also.. This is the most effective load balancing scenario, of course, you can customize it to give you more power, but this is the basic one to start with.. Later on if you want you can add in web server and database servers if warranted..

[[File:LoadBalancing-1.png|800x600px|center|Load Balancing Model - 1]]

Users on the Internet connect to your website, your website points to your load balancer IP address. Now, the load balancer will take the user's request and then check its algorithms and then decide what it has to do with the request whether to send it to Server A or Server B.. Now, at this point in time a question may have arrived in your mind if you would have been carefully reading this section of the article, if I said that the load balancer will be sending out the request to the Server A and Server B, what is Server B is down at the very moment? What will happen, will my user lose the connection? then what is the user of load balancer? Cool down buddy, you may be getting carried away.. Let me answer you, load balancer (if configured) does a small check of server availability before it sends in a request to it, so none of your users requests are going to offline server, only the online server will serve it.. This must be satisfying to you now, isn't it.. Once the request reaches the online server, it does process it, sends it to the Database Server, gets it back to same server, to the client back..




I hope this has been informative to you and I would like to thank you for reading..

Load Balancing

2017-11-30T14:26:35Z

Jayant:

''' What is load balancing ?''' 


Load balancing is an effective way of distributing traffic across group of servers in the backend.. We can also refer these group of backend servers as server pool or server farm.. Load balancing can also be seen in the real life situation too.. You must be confused, let me put it in simple with an example of a joint family where there are more helping hands who work and shares their responsibilities to take care of their loves ones, so the load is distributed among them..


 ''' Why is Server Load Balancing necessary?''' 


Server load balancing becomes necessary in situations where there is high traffic on a server than the server can serve. This may be because of the hardware limitation, so load balancing becomes first choice to put a similar of same or higher configuration parallel to the current server and shape the traffic to it, so the traffic is distributed among them..

'''Real-Life examples''':

A family of more members and only one person who works to fulfill the daily needs of the family member. There will be situation when one person's income will not be sufficient for some needs and the family has to compromise on it, however, if another person of the same family starts working, this will take some pressure off from the first person who was working alone for years.. this is nothing but load balancing and now since one more member added to the working member list, the quality of life the family requires can be fulfilled.. Similarly, one server with high number of requests cannot give you the quality of service you are seek at times and the result of this will be that you start losing traffic because of unavailability of service when the user wanted and with load balancing, you will have another server in place to serve those requests which one server was not able to handle on time, i.e., distributed load, so your client's will always get your service when they require, no matter how many users are connected to you at the same time.

If you have a shopping website where you have thousands of products for sale and users coming to your website, ordering the stuff will generate revenue for you and will be the source of income for you.. You will require more and more users to come and shop to increase your earnings and for this, you upgrading your server all the time may not be possible, as it will be considered as ever growing stuff.. One day or the other, you will find your server not capable of serving high requests since your client's did not get to you when they wanted and moved to another shopping site. A web server should always be ready to serve the requests to avoid users going elsewhere because of your server not serving them. Putting such websites on a load balancer infrastructure will make sure that all the requests coming will be serve either by one server or the other, but it will not drop it..

Now, let us know how the load balancing is done and what the different models that can be implemented, of course we can customize it as per our need, but that is based on your requirements..


='''Load Balancing Models'''=

'''Load Balancing Model - 1:''' This is the most standard model available to implement where there are 2 web servers and 1 database server to serve in your infrastructure.. Your server is connected to a load balancer, which will be the first point of contact for your users and the load balancer will then decide where to send the requests based on the configuration we do in it.. Now, the load balancer can be a service from a third-party provider or you can have an independent server or a VPS also.. This is the most effective load balancing scenario, of course, you can customize it to give you more power, but this is the basic one to start with.. Later on if you want you can add in web server and database servers if warranted..

[[File:LoadBalancing-1.png|800x600px|center|Load Balancing Model - 1]]

Users on the Internet connect to your website, your website points to your load balancer IP address. Now, the load balancer will take the user's request and then check its algorithms and then decide what it has to do with the request whether to send it to Server A or Server B.. Now, at this point in time a question may have arrived in your mind if you would have been carefully reading this section of the article, if I said that the load balancer will be sending out the request to the Server A and Server B, what is Server B is down at the very moment? What will happen, will my user lose the connection? then what is the user of load balancer? Cool down buddy, you may be getting carried away.. Let me answer you, load balancer (if configured) does a small check of server availability before it sends in a request to it, so none of your users requests are going to offline server, only the online server will serve it.. This must be satisfying to you now, isn't it.. Once the request reaches the online server, it does process it, sends it to the Database Server, gets it back to same server, to the client back..





I hope this has been informative to you and I would like to thank you for reading..

2017-11-26T18:48:28Z

Jayant: Blanked the page

Nginx Web Server

2017-11-26T18:47:19Z

Jayant: /* Features of the NGINX: */

= ''' About NGINX ''' =


It is an open source web server software designed for load balancing, reverse proxying, HTTP caching, and media streaming. It was designed for maximum stability and performance with low memory footprints. NGINX uses architecture that is more event driven, which requires less memory footprint than a traditional process driven one.


= ''' Goal behind developing NGINX:''' =


Each connection by a client was handled as a separate thread or a process and with overtime increase in the traffic to the server, the connection rate increased, and the serving capacity was affected. In the backend, additional memory consumption was seen with process spawning that required switching the CPU to a new task from an old one, thus memory and CPU utilization both were high. NGINX was designed to achieve high performance, to give better utilization of the server hardware resource that can scale up with ever increasing need of web hosting..



='''Features of the NGINX:'''=

# Capacity to handle more than 10,000 simultaneous connections with a low memory footprint.
# Handling of static files, index files, and auto-indexing.
# Reverse proxy with caching.
# Load balancing.
# It has FastCGI support with caching.
# IPv6-compatible.

NGINX is the most popular '''modular''', '''event driven''', '''asynchronous''', '''single-threaded''' web servers. We will see what these all terms mean one by one.

In this article, you may have came across a term called '''event driven''' and would be wondering what is it? Well, it is a unique approach made to handle tasks as events. The incoming connection, the disk reads, etc are all events.. Operating systems intimates when the task is started and when it is completed. NGINX worker makes proper utilization of these resources, so the resources can be utilized and released on demand as a result you will see better usage of CPU and memory.. Each worker of the NGINX has the capacity to handle thousands of concurrent requests and connections per second.. It does not create new process for every new connection instead the worker attends the new request from queue and executes runloop on it giving the worker the capacity to process multiple connections per worker..

The runloop that NGINX starts does not hang or get stuck on particular events, this is what we called as '''asynchronous'''.. It creates alarms from the system for particular event(s) and monitors the queue for those alarms.. Once it seems the alarm, NGINX runloop triggers the action. This is how NGINX utilizes the shared resources on the server in an efficient method.

'''Single threaded''' means a single worker can handle many user connections, which lowers the utilization of resources during context switching that requires CPU utilization.

NGINX uses event notifications and dedicates specific tasks to separate processes. Connections are efficiently processed in a run-loop for a limited number of single-threaded processes called workers. Each nginx worker can handle as many as thousands of concurrent connections and requests per second.
The NGINX worker code is comprised of core and functional modules. The core is responsible to maintain proper runloop. Modules comprises of application layer functionality. The modular architecture facilitates the developers to extend the set of features for the web server, keeping the core untouched..



='''NGINX Architecture:'''=
[[File:NGINX.png|800x600px|center|Nginx]]

='''How Does NGINX Work?'''=


NGINX uses a conventional process:

The master process performs the privileged task like port bindings, reading the configuration, and then it starts creating a small number of child processes like the below 3 types.

'''Cache loader:''' This process executes at start and loads the disk-based cache into the memory, and then closes. This scheduling saves the resources that it may require if it does not exit.

'''Cache manager:''' This process runs sporadically and reduces entries from the disk caches to maintain the configured sizes.

'''Worker processes:''' This is the process that performs all of the major work. It handles reads the disk, write to the disk, handles the network connections, and communicates with upstream the server if configured as revere proxy.



='''Summary:'''=

'''Master:'''
* Monitors the workers.
* Handles all the signals and notifies it to the workers like reconfiguration or update, etc.

'''Worker:'''
* It responds to the client query.
* Get the commands from the master.


I hope this has been informative to you and I would like to thank you for viewing..

Nginx Web Server

2017-10-27T07:00:22Z

Jayant:

File:Virtualizor.png

2017-10-27T06:59:43Z

Jayant:

File:SolusVM.png

2017-10-27T06:59:11Z

Jayant:

File:Xen.png

2017-10-27T06:58:57Z

Jayant:

Main Page

2017-10-27T06:46:53Z

Jayant:

= Welcome to 24x7 Server Management Wiki ! =

24x7 Server Management wiki is created to explore more aspects of various technical concepts, their overviews, and the other stuffs, which are often overlooked.. This is an effort to explain things the right way as much as possible...


= Our Aim =
<center>'''" The only source of Knowledge is Experience…"''' </center>

# To put years of experience and practical knowledge in a theoretical fashion..
# To bring forth information on various concepts on widely-searched subjects..
# To open discussion on various technologies to understand the subject in a simple way..
# To develop a community to contribute on subjects and open their views for all..
 

As being Systems Administrator, we have to do continuous research on new things for the better advancement in our services and technological approaches. The information is out there on the Internet to be taken, but not all are appropriate to answers our questions that arises from the study and we have to spend hours to find those answers. We know how time is valuable and We came up with an idea of developing a "wiki" that would only focus on these stuffs rather more extensively. But being a wiki, will need help from everyone interested, so we are open to discussion on this...


[[File:cPanel.png|frameless|left|cPanel]] [[File:Plesk.png|frameless|Plesk]] [[File:OpenVZ.png|frameless]]

= =
{| class="wikitable sortable collapsible"
|+Catalogue 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 25%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 80%; height:6px; color:White" | Description
|-valign="middle"
| [[Server Management]] || What is server management and things you should look for before you hire them to do the job for you..
|-
| [[IP Reputation]] || What is IP reputation and how does it affect the mail server..
|-valign="middle"
| [[IP delisting ]] || How to delist IP address if they are blacklisted..
|-valign="middle"
| [[How Does A Web Server Works|Web Server Functioning]] || How do you get the information you are seeking.
|-valign="middle"
| [[WordPress Security-I]] || Importance of WordPress Security and understanding the security issues..
|-valign="middle"
| [[WordPress Security-II]] || Preventive measures on WordPress Security and improvisation in the security..
|-valign="middle"
| [[Phishing]] || What is Phishing? and what are the most common types? Be aware of those..
|-valign="middle"
| [[Spamming]] || What are spam? How do they work? What are they categories?
|-valign="middle"
|}

{| class="wikitable sortable collapsible"
|+Infrastructure Management 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 26%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 75%; height:6px; color:White" | Description
|-valign="middle"
| [[Load Balancing]] || What is load balancing and what are the different type of load balancing architectures available ?
|-
|}

See '''Other<big>[[Articles|Articles Catalogue]]</big>''' here

Main Page

2017-10-27T06:46:03Z

Jayant:

= Welcome to 24x7 Server Management Wiki ! =

24x7 Server Management wiki is created to explore more aspects of various technical concepts, their overviews, and the other stuffs, which are often overlooked.. This is an effort to explain things the right way as much as possible...


= Our Aim =
<center>'''" The only source of Knowledge is Experience…"''' </center>

# To put years of experience and practical knowledge in a theoretical fashion..
# To bring forth information on various concepts on widely-searched subjects..
# To open discussion on various technologies to understand the subject in a simple way..
# To develop a community to contribute on subjects and open their views for all..
 

As being Systems Administrator, we have to do continuous research on new things for the better advancement in our services and technological approaches. The information is out there on the Internet to be taken, but not all are appropriate to answers our questions that arises from the study and we have to spend hours to find those answers. We know how time is valuable and We came up with an idea of developing a "wiki" that would only focus on these stuffs rather more extensively. But being a wiki, will need help from everyone interested, so we are open to discussion on this...


[[File:cPanel.png|frameless|left|cPanel]] [[File:Plesk.png|frameless|Plesk]]

= =
{| class="wikitable sortable collapsible"
|+Catalogue 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 25%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 80%; height:6px; color:White" | Description
|-valign="middle"
| [[Server Management]] || What is server management and things you should look for before you hire them to do the job for you..
|-
| [[IP Reputation]] || What is IP reputation and how does it affect the mail server..
|-valign="middle"
| [[IP delisting ]] || How to delist IP address if they are blacklisted..
|-valign="middle"
| [[How Does A Web Server Works|Web Server Functioning]] || How do you get the information you are seeking.
|-valign="middle"
| [[WordPress Security-I]] || Importance of WordPress Security and understanding the security issues..
|-valign="middle"
| [[WordPress Security-II]] || Preventive measures on WordPress Security and improvisation in the security..
|-valign="middle"
| [[Phishing]] || What is Phishing? and what are the most common types? Be aware of those..
|-valign="middle"
| [[Spamming]] || What are spam? How do they work? What are they categories?
|-valign="middle"
|}

{| class="wikitable sortable collapsible"
|+Infrastructure Management 
|+General Category 
! style="background-color:#FF7A32; margin: 1px; width: 26%; height:6px; color:White" |Topics !! style="background-color:#FF7A32; margin: 1px; width: 75%; height:6px; color:White" | Description
|-valign="middle"
| [[Load Balancing]] || What is load balancing and what are the different type of load balancing architectures available ?
|-
|}

See '''Other<big>[[Articles|Articles Catalogue]]</big>''' here