Difference between revisions of "SUNScholar/Upgrading/Hardware"

From Libopedia
Jump to navigation Jump to search
m
 
(25 intermediate revisions by the same user not shown)
Line 1: Line 1:
==Introduction==
+
<center>
{{WARNING}}
+
'''[[SUNScholar/Upgrading|Back to Upgrading]]'''
 
+
</center>
This is the very tricky one, if you are running your server on a bare metal machine.
 
 
 
If your server is virtualised then this procedure is not needed.
 
 
 
To avoid bare metal upgrades in the future, it is highly advised that you virtualise your server. Ask central campus IT to help you with this.
 
 
 
If you are presently running bare metal and are going to upgrade to another bare metal server, then read the guidelines below.
 
 
 
==Bare metal to bare metal==
 
These guidelines are very brief and require someone with Linux experience to execute correctly.
 
===Prep new machine===
 
#[[SUNScholar/Install_Ubuntu|Install Ubuntu]]
 
#[[SUNScholar/Prepare Ubuntu|Prepare Ubuntu]]
 
#The new machine hostname should be temporary. For example: http://irx.sun.ac.za
 
 
 
===Export and import contents===
 
#Export the PostrgeSQL DB from the old machine and import it to the new machine using "pgAdmin". See: http://www.pgadmin.org
 
#Put the old machine into ''maintenance mode''.
 
#Copy the entire '''/home/dspace''' folder from the old machine to the new machines '''/home/dspace''' folder using "rsync". See: http://en.wikipedia.org/wiki/Rsync
 
===Enable Tomcat webapps on new machine===
 
#Follow this procedure to enable the java webapps on the new machine: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Install_Dspace/S08
 
#Check for correct operation of DSpace on the new machine.
 
===Enable "handle server" on new machine===
 
#Follow this step to enable the handle server: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Handle_Server#Step_9_-_Start_handle_server
 
 
 
===Swap hostnames===
 
#Rename the old machine. For example: http://irz.sun.ac.za. Then reboot.
 
#Rename the new machine so that it has the same hostname as the old machine. Then reboot.
 
#Check for correct operation of DSpace and handle server on the new machine.
 
 
 
===Precautionary Principle===
 
Keep the old machine running for a while until the new machine is stabilised. This way you have a live backup in case of big problems.
 
 
 
==Comparison of bare metal versus virtual machine==
 
  
{|class="wikitable" width="95%"
+
{{DISCLAIMER}}
|- align="center"
 
!
 
==ir1.sun.ac.za - Bare metal==
 
!
 
==ir2.sun.ac.za - Virtual machine==
 
|-
 
|
 
==Specifications==
 
*CPU=24
 
*RAM=12
 
*DISK=500GB
 
|
 
==Specifications==
 
*CPU=2
 
*RAM=4GB
 
*DISK=50GB
 
|-
 
|
 
==Load==
 
[[File:Ir1-load-day.png]]
 
|
 
==Load==
 
[[File:Ir2-load-day.png]]
 
|-
 
|
 
==RAM==
 
[[File:Ir1-memory-day.png]]
 
|
 
==RAM==
 
[[File:Ir2-memory-day.png]]
 
|-
 
|
 
==Disk==
 
[[File:Ir1-df-day.png]]
 
|
 
==Disk==
 
[[File:Ir2-df-day.png]]
 
|}
 
  
==Considerations==
+
==[[SUNScholar/Upgrading/Hardware/New Server|Upgrading to a New Server]]==
There is always a performance price when you virtualise. In addition, since DSpace is a java webapp, you should realise java is itself a virtual machine, so if you virtualise the hardware, then you are virtualising an already, virtual machine! For this reason, bare metal machines always have the best performance.
 
  
However, performance is not an issue if you have a small repository and very few people connected at one time as collection submitters/managers. If you anticipate having a big repository then you should consider going bare metal.
+
==[[SUNScholar/Upgrading/Hardware/Add a New Disk|Adding a New Disk]]==
 
+
[[Category:System Administration]]
'''[[SUNScholar/Upgrading|Back to Upgrading]]'''
 
 
__NOTOC__
 
__NOTOC__

Latest revision as of 11:16, 28 May 2016

Back to Upgrading

WE CANNOT ACCEPT RESPONSIBILITY FOR ANY DATA LOSS OR CORRUPTION
BEFORE PROCEEDING, DO EXTENSIVE TESTING ON SPARE INFRASTRUCTURE
*** YOU PROCEED AT YOUR OWN RISK ***

Upgrading to a New Server

Adding a New Disk