The WHM panel provides two options for a server reboot:
The recommended option is Graceful Reboot. This way the reboot will be queued, and when all services are stopped the server will be restarted.
In a case there is a very high load on the server, the Graceful Reboot might not be sufficient. Then you will need to use the Forceful Server Reboot option.
Restarting a VPS or Dedicated server with WHM
Log into WHM. Type "restart" in the search box at the top left to find the "Restart Services" section. To restart Apache, select HTTP Server (Apache) and click yes.
Steps to restart your VPS in AMP
Log into AMP. Locate your server and click the Restart VPS button. Expand the Restart VPS drop box and click the "Restart VPS" button. Then, allow time for the server to restart.
Restarting VPS and dedicated server with command line
Customers can restart their server services through the WHM or through Shell access. Please see the below tutorials on how to restart your services through WHM and through command line. You can shell into your server and stop and start your httpd services for your website. See the following commands.
[email protected]### [~]# service httpd stop
[email protected]### [~]# service httpd start
Checks the Apache server status
[email protected]### [~]# service httpd status
You can also restart MySQL also with the following commands
[email protected]### [~]# service mysql stop
[email protected]### [~]# service mysql start
Checks the MySQL server status
[email protected]### [~]# service mysql status
Plesk 12.5 for Linux
# service sw-engine start /usr/sbin/sw-engine-fpm: error while loading shared libraries: libxmlrpc_cpp.so.4: cannot open shared object file: No such file or directory
3. Library libxmlrpc_cpp.so.4 is missing from the server:
# ls -l /usr/lib64/libxmlrpc_cpp.so.4* #
# rpm -qa | grep xmlrpc xmlrpc-c-1.16.24-1210.1840.el6.x86_64 xmlrpc-c-1.16.24-1210.1840.el6.i686 plesk-php70-xmlrpc-7.0.9-centos6.16072211.x86_64 xmlrpc-c-c++-1.16.24-1210.1840.el6.i686
Missing libxmlrpc_cpp.so.4 library.
# wget ftp://fr2.rpmfind.net/linux/centos/6.8/os/x86_64/Packages/xmlrpc -c-c++-1.16.24-1210.1840.el6.x86_64.rpm
# rpm -ivh xmlrpc-c-c++-1.16.24-1210.1840.el6.x86_64.rpm
# service sw-engine start
Today, we are going to see what exactly DFS is. It is accessible in Microsoft environment under Windows Server. And the DFS acronym stands for Distributed File System or System Distributed File.
This system allows hierarchical file structure for shared files on different servers of logical network. It is used to reference a set of shares that will make available uniformly and to centralize all the space available on this set of shares.
With DFS, the end user does not display the name of the server on which it access read data, it is completely transparent. The advantage is that if the server has to change because of a failure or due to the developmental work, the path will remain the same.
Behind the same DFS path we can hide multiple servers with the same data with synchronization between these servers through DFSR (i.e. DFS Replication). This approach is very useful for high-availability of data and load balancing.
Of course, it is possible to use a path to a server (1 1), where each server will host different data.
Know that the DFS is increasingly present, now it is even used for SYSVOL replication on a domain between domain controllers.
Active directory and DNS are two important prerequisites for DFS; these two are core requirements for DFS with replication and network connectivity throughout DFS root.
Root folder and target
When speaking about DFS, three terms are important to remember and understand the workflow: DFS root, folder and target.
These three elements are essential to the establishment of a DFS infrastructure.
To illustrate the point and for a better understanding for host DFS works, here is a brief example of DFS infrastructure:
On this infrastructure, our DFS server is “RV-AD01, which is also a domain controller in the domain “ESDS” and DNS. The DFS root is “ESDS”.
This DFS root contains two subfolders:
-Computer: which contains no target; there is only an organizational aspect of the namespace. This same contains two sub-folders “Data” and “Resources” that target “SRV01”; this server will be the one hosting the data for these two DFS folders.
-Work: contains two targets: SRV01 and SRV02, which will aim to host the data and ensuring high availability through replication via DFSR.
Benefits of DFS
The use of DFS enterprise has several important advantages.
As the core assets of organizations and enterprises spread across industry verticals, the data storing continues to rise. Lots of companies own their data, be it stored on their own servers in the company or with the data center service providers. It is important for them to make sure the cost-efficiency, high-performance, greater scalability, and reliability for their applications. And for this selection of the best processor based server is necessary.
Basically, the Intel Xeon processors are built to improve the performance and scalability of the server. In order to gain these features, selection of the right Intel Xeon processor based server for your environment is much more important. An ideal way to identify the best xeon processor based server is to prioritize your workload requirements. There are various factors to be considered.
Some of them are:
One of the best Intel processors in the market is the Quad-Core Xeon E5606 processor, mainly used those looking for increased performance on their high-end dedicated servers. The Quad-Core Intel Xeon 5606 processor, code named Westmere-EP, contains four processing cores which is quite enough to boost an application performance.
This E5606 processor is based on the Intel’s core micro-architecture and primarily designed to increase the price/performance and energy efficiency of the existing dual-core processor family. It was also said by Intel, that the chip should provide 4 ½ times increased performance of its single core processor. Since, the launching of the Intel Xeon Quad-Core processors, Dell started offering products with integration of the multi-core processors, which includes Intel’s first Xeon Quad-Core Processor.
The Intel Xeon Quad-Core Processor are designed to meet massive performance headroom that starts with 4 execution cores per socket, and the Hyper-Threading Technology enabled can handle 4 software threads simultaneously.
For mission-critical database solutions, the scalable performance plays a key role. It is very essential for such kind of environments to meet the query response and latency targets, and ability to adopt the benefit of additional server hardware resources as they are added. The E5606 processor based server is perfect for workloads based on the SQL server as well as aids in creating an excellent deployment environment. As testing at Intel, have shown that the SQL server functioning from the E5606 quad core xeon processor provides excellent output in terms of performance and scalability.
The complete sequence of Intel Xeon Processor 5000 provides an opportunity of enabling businesses to get the most possible power from their server hardware as they are energy-efficient and affordable.
A combination of Microsoft SQL Server and Intel Xeon Quad-Core processors could offer you significant benefits not only in terms of performance and scalability, but are also energy efficient.
One of the critical factors in the success of your website is the availability that dedicated web server hosting offers. Since most web hosting providers already offer 99% of uptime, it is webmasters and customers responsibility to optimize the site properly so that the dedicated servers are not overloaded unnecessarily.
If you follow the following tips, it can help you to optimize the performance mode of the pages to load faster for better browsing experience.
Use CSS Sprites
This technique is based on the use of only one big image in your CSS contains all the images used, eg background images, bullets, etc., and then placing it through the CSS. This way your file styles only loads a large image, instead of loading several times the single image. Fewer requests to the server, the faster will be delivered.