VMWare - Revision history

Davidbrito: /* Installation Phase */

2013-04-18T17:07:13Z

‎Installation Phase

Davidbrito: /* Backup VM */

2013-02-26T14:55:04Z

‎Backup VM

Davidbrito: /* Can't connect to a VM or web services are down */

2012-05-28T12:06:00Z

‎Can't connect to a VM or web services are down

Davidbrito: /* Can't connect to a VM or web services are down */

2012-05-28T12:05:31Z

‎Can't connect to a VM or web services are down

Davidbrito at 11:45, 28 May 2012

2012-05-28T11:45:29Z

Davidbrito at 11:44, 28 May 2012

2012-05-28T11:44:36Z

Davidbrito: /* Production Phase */

2012-04-13T16:39:24Z

‎Production Phase

Davidbrito: /* Can't connect to microsoft.com (can´t connect Messenger) */

2012-04-13T16:35:38Z

‎Can't connect to microsoft.com (can´t connect Messenger)

Davidbrito: /* Cant connect to microsoft.com (messenger not connects) */

2012-04-13T16:35:01Z

‎Cant connect to microsoft.com (messenger not connects)

Davidbrito: /* Production Phase */

2012-04-13T15:46:09Z

‎Production Phase

@@ Line 33: / Line 33: @@
 ===Creating a VM Backup Server===
 [[Creating a BackupServer in VMWare]]
 ==Production Phase==

@@ Line 144: / Line 144: @@
 The backup strategy was implemented in the virtual machine VM-BackupServer created in the ESXi backup server:
 #One Replication for each VM from production ESXi host to ESXi disaster and recovery host (FTPServer and WebServer in disk 1 and OpenDAPServer, DC2 in disk 2 (4 restore points done weekly (saturday morning)).
-#One reverse incremental backup of all initial VM to backup server Davinci and one backup of all machines (above VM's + BackupServer) (2 restore points done monthly (last sunday in the morning)).
+#One reverse incremental backup of all initial VM to backup server Davinci and one backup of all machines (above VM's + BackupServer) (2 restore points done every two months (last sunday in the morning); the picture is dated since it shows monthly backup).
 [[Image:Replication&BackupScheme.png|400px|thumb|center|Virtual Machines Backup and Replication Scheme]]
 ===Restore VM===

@@ Line 231: / Line 231: @@
 If some service is down in FTPServer, WebServer or OpenDAP do this:
-. try to remote desktop or open folders for the VM that some service in not responding. If that works than you need to remote desktop to see if some service (e.g. in IIS in FTPServer or WebServer) is down.
+#. try to remote desktop or open folders for the VM that some service in not responding. If that works than you need to remote desktop to see if some service (e.g. in IIS in FTPServer or WebServer) is down.
+#. if previous fails, ping inside the network for names of the servers (FTPServer, WebServer or OpenDAP). If that works try to use thightVNC for instance and check services.
-. if previous fails, ping inside the network for names of the servers (FTPServer, WebServer or OpenDAP). If that works try to use thightVNC for instance and check services.
+#. if previous fails try with the ip's (could be DNS problem). If that works try to use thightVNC for instance and check services.
+#. if previous fails open vSphere (the software that opens virtual machine manager) and select the ip or name (ESXi1) of the cisco machine that has all the VM (enter user and pass). If that works than have to check if VM that is failing is ON, if not start it.
-. if previous fails try with the ip's (could be DNS problem). If that works try to use thightVNC for instance and check services.
+#. if previous fails make sure that the cisco server is ON (in the ventialted room). If not, turn it on and do the previous steps again from the beggining.
+#. if the previous fails and seems that you do not have connection with cisco server for a while is time to go to disater & recovery site (see '''Restore VM''' chapter and then under '''Failover''').
 ==Links==

@@ Line 241: / Line 241: @@
 . if previous fails make sure that the cisco server is ON (in the ventialted room). If not, turn it on and do the previous steps again from the beggining.
-. if the previous fails and seems that you do not have connection with cisco server for a while is time to go to disater & recovery site (see '''Restore VM''' chapter and then under '''Failover'''.
+. if the previous fails and seems that you do not have connection with cisco server for a while is time to go to disater & recovery site (see '''Restore VM''' chapter and then under '''Failover''').
 ==Links==

@@ Line 211: / Line 211: @@
 With Veeam Backup & Replication, you can run a VM copy job to create an independent fully-functioning copy of a virtual machine on a selected storage.
-====TroubleShooting====
+===TroubleShooting===
-=====Can't connect to microsoft.com (can´t connect Messenger)=====
+====Can't connect to microsoft.com (can´t connect Messenger)====
 '''First Symptons:''' Messenger can't connect; cant access microsoft sites.
@@ Line 226: / Line 226: @@
 Note: also in this case there was IP problems in DHCP server (also vm-dc2) leases and the problematic ip's were removed.
 ====Can't connect to a VM or web services are down====
 Remind that FTPserver runs the ftp.mohid.com, WebServer has 2 sites (datacenter.mohid.com (this root does not show a webpage, is used for WW3 wave model repository) and forecast.maretec.org) and Opendap has opendap files and site opendap.mohid.com:8080/thredds/catalog.html

@@ Line 35: / Line 35: @@
 ==Production Phase==
 ===Changing the bridging between the LAN and the DMZ===
@@ Line 224: / Line 210: @@
 ====VM Copy====
 With Veeam Backup & Replication, you can run a VM copy job to create an independent fully-functioning copy of a virtual machine on a selected storage.
 ==Links==

@@ Line 41: / Line 41: @@
 '''Cause:''' This occured because microsoft.com was not accepting our connections and all the services downstream would fail. DNS server PTR record (that translates ips to hosts, or reverse DNS) was corrupted and so microsoft.com was not accepting connections. this could have happened also with e-mail not being accepted by e-mail providers.
-'''Check if this is the case:''' To see if this may be happening in cmd do '''nslookup microsoft.com''' and if message says "DNS Request Timed Out" than this is the case. See http://support.microsoft.com/kb/242906 where "When Nslookup starts, it attempts to resolve the IP address of its host's DNS server to its fully qualified domain name (FQDN). If the DNS server does not respond or if the DNS server's reverse lookup zones do not contain a PTR record for the DNS server's IP address, the error message is displayed."
+'''Check if this is the case:''' To see if this may be happening in cmd do '''nslookup microsoft.com''' and if message says "DNS Request Timed Out" or doing '''tracert microsoft.com''' and the response at the end is "Destination net unreachable." than this is the case. See http://support.microsoft.com/kb/242906 where "When Nslookup starts, it attempts to resolve the IP address of its host's DNS server to its fully qualified domain name (FQDN). If the DNS server does not respond or if the DNS server's reverse lookup zones do not contain a PTR record for the DNS server's IP address, the error message is displayed."
 '''Solution:''' go to DNS server (vm-dc2) and do in cmd:

← Older revision		Revision as of 15:46, 13 April 2012
Line 35:		Line 35:

	==Production Phase==		==Production Phase==
		+
		+	===Cant connect to microsoft.com (messenger not connects)===
		+	'''First Symptons:''' Messenger can't connect; cant access microsoft sites.
		+	'''Cause:''' This occured because microsoft.com was not accepting our connections and all the services downstream would fail
		+	DNS server PTR record (that translates ips to hosts, or reverse DNS) was corrupted and so microsoft.com was not accepting connections. this could have happened also with e-mail not being accepted by e-mail providers.
		+	'''Check if this is the case:''' To see if this may be happening in cmd do '''nslookup microsoft.com''' and if message says "DNS Request Timed Out" than this is the case. See http://support.microsoft.com/kb/242906 where "When Nslookup starts, it attempts to resolve the IP address of its host's DNS server to its fully qualified domain name (FQDN). If the DNS server does not respond or if the DNS server's reverse lookup zones do not contain a PTR record for the DNS server's IP address, the error message is displayed."
		+	'''Solution:''' go to DNS server (vm-dc2) and do in cmd:
		+	> ipconfig /registerdns
		+	The register should reload the PTR and remove the problem
		+
		+
		+	Note: also in this case there was IP problems in DHCP server (also vm-dc2) leases and the problematic ip's were removed.
		+

	===Changing the bridging between the LAN and the DMZ===		===Changing the bridging between the LAN and the DMZ===