Part 2.7 - Disaster Recovery with SRM & VNC

Bubblebridge is in place but since its a full fledged CentOs 6.3 desktop distro why not have proper access to it. So I thought I would enable VNC on it.

Installation

Just to make sure check that vnc or rather tigervnc is installed executing the following:

rpm -q tigervnc-server
rpm -q tigervnc


If not present the following should cure that:

yum install tigervnc-server tigervnc

Setup

VNC user accounts. Unless you want to run as an already existing user the following would create a user (or if repeated) users for you. As root.
useradd
passwd
In my case I'll go with the bubblebridge user the above is already fixed.

Next step is to edit the server configuration file /etc/sysconfig/vncservers adding the following at the end.
VNCSERVERS="2:"
VNCSERVERARGS[2]="-geometry 800x600"

Now its time to setup the vncpasswd for the users by su:ing out of root to the users.su -
vncpasswd
exit

Check that the server starts and stops as intended and when it does add it to the set of auto started services.service vncserver stop
service vncserver start
chkconfig vncserver on

 Update iptables to allow access

# Open VNC
-A INPUT -m state --state NEW -m tcp -p tcp -dport 5800

-A INPUT -m state --state NEW -m tcp -p tcp -dport 5900
-A INPUT -m state --state NEW -m tcp -p tcp -dport 6000



 And finally restart iptables to allow access

service iptables restart


Comments

ALEX said…
Cloud DR solutions are essential for data backup recovery of lost data from the system. This blog provide very good information on disaster recovery development.
8:12 AM
Post a Comment

Popular posts from this blog

Possible SYN flooding on port 3306 (MySQL)

The system setup is such that the MySQL servers that put the "Possible SYN flooding on port 3306" in the log files only are exposed to system internal backend services. These in turn aren't exposed to the wild wild web. Fronting the system we have the servers publishing services to internet. Thus I was kind of stunned when the log messages started to appear and even though we had done a release of the system I found it far fetched that we should start to DOS our self. So why did the messages appear? Two different error messages could be identified in the log files and they seem to be related, especially since the Java servers with link failure do communicate with the MySQL servers. Possible SYN flooding on port 3306 @ MySQL server Communication link failure @ Java backend servers After some tcpdumping, head scratching and googling I think I have it down to the root cause, hidden in how TCP works in general, and the OS config in combi...
Read more

Part 1 - Disaster Recovery with SRM and vSphere Replication

Image
Abstract  The company I work for has needs for disaster recovery but there is also external demands for it. The company not being very big has so far not been able to implement any automated disaster recovery solution although we do have a documented disaster recovery plan. The plan regardless of how good or bad it is isn't tested in a long time and the RTO (Recovery Time Objective) is wished by management to be days but I can't see that it is anything else than weeks. Since we virtualized our production system I've been looking at VMware vCenter Site Recovery Manager as a driver but the cost array based replication has stopped any attempts dead in their tracks. VMware vSphere® Replication has been around for a while now and we hope that it's hardened enough for a slightly bigger production critical implementation. In this article I will try to document and explain how we experiment, design and implement disaster recovery and even more important, in my opinion...
Read more

Part 2 - Disaster Recovery with SRM and vSphere Replication

Image
In the previous article we went through the installation and configuration of the SRM and vSphere infrastructure. The time has now come to actually doing some tests and failover some VM's.  In the simple scenario I expect everything to go smoothly but there are a few things that I'm concerned about at this point since the protected environment I'm ultimately is failing over isn't so simple. It has multiple dvSwitches, vLans, load balancer, firewall, ldap, a set of test drivers to verify the integrity of the system and access to the system in a sensible way for administrators so there are a few things that needs to be resolved. Protected Setup Test Failover The small test In this scenario I do a test failover of a single machine and verifies that it starts and that I can log into it. The steps are: Setup the machine running RHEL 5.5.  Install VMware tools  Kick of the vSphere Replication Create a Protection Group and ... no that didn...
Read more