lesson plan for canes 7.4 restore virtual machine

LESSON PLAN
FOR
CANES
7.4 RESTORE VIRTUAL MACHINE (VM)
PREPARED BY
MANTECH
SAN DIEGO, CA
PREPARED FOR
PROGRAM EXECUTIVE OFFICE (PEO) COMMAND, CONTROL, COMPUTERS, COMMUNICATIONS, AND
INFORMATION (C4I)
AND
SPAWAR SYSTEMS CENTER (SSC) ATLANTIC
MARCH 2017
LESSON PLAN
CHANGE RECORD
Number and Description of Change(s)
Entered By
Date
i
LESSON PLAN
TABLE OF CONTENTS
CHANGE RECORD.................................................................................................................................................................................... i
SECURITY AWARENESS NOTICE ....................................................................................................................................................... iii
TERMINAL OBJECTIVE(S)..................................................................................................................................................................... v
SECTION 1: RESTORE VIRTUAL MACHINES IN CANES ................................................................................................................. 3
SECTION 2: PROCEDURES FOR RESTORING VMs ..........................................................................Error! Bookmark not defined.
ii
LESSON PLAN
SECURITY AWARENESS NOTICE
All personnel involved in operation or maintenance of electronic equipment must be thoroughly familiar with the electronic equipment
safety precautions contained in Electronic Installation and Maintenance Book, General, NAVSEA SE000-00-EIM-100, Section 3, and
Naval Ships' Technical Manual, Chapter 300, S9086-KC-STM-010/CH- 300, Section 2. In addition, attention is directed to the Navy
Safety Program Instructions, OPNAVINST 5100.19 (series) and 5100.23 (series), and the safety training requirements contained in
CNETINST 1500.20 (series).
This equipment employs voltages, which are dangerous and may be fatal if contacted by operating or maintenance personnel. There
are mechanical safety devices associated with this equipment that must be maintained in a constant state of readiness to preclude
causing injury to personnel and/or damage to equipment. Extreme caution must be exercised when working with or handling this
equipment. Some components are extremely heavy. Rigid pre- inspections must be made to handling equipment to ensure their safety
and safety summaries must be read to the handling teams prior to conducting dangerous evolutions. Hazard awareness dictates that
this equipment must always be viewed as an integral part of a system and not as a component. While every practical precaution has
been incorporated into this equipment, it is not possible or practical to try to list every condition or hazard that you may encounter.
Therefore, all operating or maintenance personnel must at all times observe as a minimum, the following:
DON’T SERVICE OR ADJUST ALONE
Under no circumstances will a person operate or maintain equipment without the immediate presence or assistance of another person
capable of rendering aid. Unless under direct supervision of a qualified person, no person shall operate or maintain equipment for
which he is unqualified.
DON’T TAMPER WITH INTERLOCKS
Reliance on interlock circuits to remove power from the equipment is never to be assumed. Until operation of the interlock is verified,
equipment is assumed to be in the hazardous mode of operation. Under no circumstances will any access gate, door, or interlock
switch be removed, bypassed, or modified in any way by other than authorized maintenance personnel and then only after observing
proper tag-out procedures.
REPORT ALL HAZARDS
If at any time, you detect a hazard, it is your responsibility to report the hazard to ensure that it is corrected. If at any time, you detect a
"new" or "suspected new" hazard, particularly due to equipment installation, modification, or repair, it is your responsibility to ensure
that a SAFETYGRAM is submitted to the Naval Safety Center, Norfolk, VA, in accordance with OPNAVINST 5102.1 (series). This
will ensure that this hazard will be investigated, publicized, or corrected, as required.
iii
LESSON PLAN
Additionally, SSPINST 3100.1 (series) requires SWS personnel to submit special check TFRs when a potential or actual unsafe
condition is noticed that could cause injury to personnel and/or damage to equipment. When a problem/failure occurs involving the
safety of personnel or equipment and it cannot be immediately resolved by command/technical assistance on-site, the TFR data shall
be transmitted to SSP and others by Naval Message.
SAFETY – “TRAINING TIME OUT”
In any training situation when a student or instructor expresses concern for personal safety, it is an indication that a need for
clarification of procedures or requirements exists and a "Training Time Out" shall be called. An individual should verbally call
"TRAINING TIME OUT" (TTO) if they detect a hazardous condition during any teaching session (lab or theory), or raise a clenched
fist to indicate a "TRAINING TIME OUT" (TTO) if the verbal command cannot be heard. Training activities will be suspended until
the hazardous situation has been examined and additional explanation and instruction has been provided to allow safe resumption of
training. Caution should be used to ensure a halt to a procedure does not result in additional hazards. TTO follow-up procedures will
be performed in accordance with CNET Instruction 1500.20(Series).
PRE-MISHAP PLAN
The Pre-Mishap plan explains the procedures to follow and essential telephone numbers to call in case of an accident or emergency. It
is located by the emergency exit in the laboratory.
iv
LESSON PLAN
TERMINAL OBJECTIVE(S)
Given a CANES network or CANES TTE, and CANES technical documentation, manage CANES maintenance associated with
virtual machines adhering to all safety precautions and in accordance with all applicable technical procedures
v
LESSON PLAN
LESSON 7.4 Virtual Machines (VMs) RESTORE AND RECOVERY
__________________
CLASS PERIODS: 1.0
LAB PERIODS: 0.0
PA PERIODS: 0.0
Enabling Objectives
Trainee Preparation Materials
Upon successful completion of this topic, the trainee will be Trainee Guide:
able to:
Outline Sheet 7-4-1-1, Virtual Machines (VMs) Restore and
GIVEN ACCESS TO CANES TTE AND CANES Recovery
TECHNICAL
DOCUMENTATION
IDENTIFY Information Sheet 7-4-1-2, Virtual Machines (VMs) Restore
PROCEDURES TO RESTORE AND RECOVER
VIRTUAL MACHINES ADHERING TO ALL SAFETY Information Sheet 7-4-1-3, Virtual Machine (VMs) Recovery
PRECAUTIONS AND APPLICABLE TECHNICAL Reference Publications:
PROCEDURES
Consolidated Afloat Network and Enterprise Services (CANES)
AN/USQ-208(V) SW1.2 Interactive Electronic Technical Manual
(IETM), EE689-2X-IEM-020
Instructor Preparation:
A. Review Assigned Trainee Material
B. Reference Publications:
1. Consolidated Afloat Network and Enterprise Services
(CANES)
AN/USQ-208(V)
SW1.2
Interactive
Electronic Technical Manual (IETM), EE689-2X-IEM020
C. Training Materials Required:
1. Outline Sheet
a. Outline Sheet 7-4-1-1, Virtual Machines (VMs)
Restore and Recovery
2. Information Sheet
a. Information Sheet 7-4-1-2, Virtual Machines (VMs)
1
LESSON PLAN
LESSON 7.4 Virtual Machines (VMs) RESTORE AND RECOVERY
__________________
Restore
b. Job Sheet 7-4-1-3, Virtual Machine (VMs) Recovery
2. IMI
a. PowerPoint Presentation:
Restore and Recovery.ppt
CANES 7.4 PPT
VMs
2
SECTION 1: VIRTUAL MACHINES (VMs) RESTORE
DISCUSSION POINT
1. Introduction
As an IT monitoring CANES 1.2 networks, each technician
will be required to understand and can perform Virtual
Machine (VM) restoration. This lesson will provide an
overview and the procedures needed to conduct VM restore in
response to loss or corruption of a domain.
RELATED INSTRUCTOR ACTIVITY
Display PowerPoint Slide 7-4-1, Virtual Machines (VMs) Restore
and Recovery.
Display PowerPoint Slide 7-4-2, Introduction.
Establish readiness.
Motivating statements.
Tell trainees how they will use the material.
Tell trainees why they need to know lesson.
Refer trainees to Outline Sheet 7-4-1-1, Virtual Machines (VMs)
Restore and Recovery.
2. Enabling Objective:
a. IDENTIFY procedures to restore and recover virtual
machines
3. References:
a. Consolidated Afloat Network and Enterprise Services
(CANES) AN/USQ-208(V) SW1.2 Interactive Electronic
Technical Manual (IETM), EE689-2X-IEM-020
4. Restoring Virtual Machines (VMs) in CANES 1.2
Display PowerPoint Slide 7-4-3, Enabling Objective.
Read Enabling Objectives to trainees.
Display PowerPoint Slide 7-4-4, References.
Refer trainees to Information Sheet 7-4-1-2, Virtual Machines
(VMs) Restore.
Discuss references with trainees and explain how they will be
used throughout the lesson.
Display PowerPoint slide 7-4-5, Restoring VM in CANES.
3
a. Site Recovery Manager provides administrators with
several tools to manage the restoration of VMs.
1) It provides a disaster recovery solution that helps
you to plan, test, and run the recovery of VMs
between a protected vCenter Server site and a
recovery vCenter Server site.
a) The development of this new MRC is due to the
software change in CANES 1.2. CANES SW1
used EATON Intelligent Power Manager and
CANES SW1.2 uses NetAgent IX.
5. Disaster Recovery Plan
a. To minimize system downtime when a system crash
occurs, System Administrators must establish a disaster
recovery plan for the various servers, workstations, and
services on CANES network.
Display PowerPoint slide 7-4-6, Restoring VM in CANES
(cont.).
b. Backing up the information is the first part of completing
a successful restore. Knowing what specific steps to take
to recover the system to full functionality is the other half
of the equation.
c. Since CANES hosts a wide range of data and computer
functionality, System Administrators may need to
institute a unique restore strategy for each machine type
or server function.
d. Since CANES hosts a wide range of data and computer
functionality, System Administrators may need to
institute a unique restore strategy for each machine type
or server function.
4
6. Recovery Plan
a. After Site Recovery Manager, has been configured at the
protected and recovery sites, the protection groups are
created and are used to control the steps of the recovery
process. This plan will include the order in which VMs
are recovered and any IP address changes.
Display PowerPoint slide 7-4-7, Restoring VM in CANES
(cont.).
1) Protection groups are created at the protected site,
while recovery plans are created at the recovery site
2) A recovery plan must contain one or more protection
groups. A protection group can be part of more than
one recovery plan.
b. For example, if there are two protection groups:
Accounting and Email, three recovery plans can be
created.
1) The three recovery plans
a) Accounting recovery plan
Accounting protection group.
containing
the
b) Email recovery plan containing the Email protection
group.
c) The Entire Site recovery plan containing both
protection groups.
c. When creating a recovery plan, configuration of a
network test should be done for each of the recovery
networks at the recovery site.
1) When testing a recovery plan, recovered VMs are
connected to a corresponding test network, as defined
in a recovery plan.
a) By default, Site Recovery Manager uses an isolated
5
network - a virtual switch with no external
connectivity that is created dynamically when a
recovery plan is tested.
b) This is a simple and effective approach, but
connectivity between VMs is limited to the VMs
running on the same vSphere host.
d. Testing a recovery plan is beneficial in ensuring the
effectiveness of the plan.
Display PowerPoint slide 7-4-8, Restoring VM in CANES
(cont.).
1) Site Recovery Manager features a non-disruptive
testing mechanism to facilitate testing at any time. It is
common for an organization to test a recovery plan
multiple times after creation to resolve any issues
encountered the first time the recovery plan was tested.
2) Verify the recovery plan is ready for testing or running
by checking the “Plan status”.
3) Click the green arrow below “Description” to begin the
test process.
a) Array snapshots (or clones) are created with array
replication.
b) Virtual machine
vSphere.
snapshots
are
created
with
4) This approach allows powering on and modifying VMs
recovered as part of the test while replication continues
to avoid a Recovery Point Objective (RPO) violations.
Display PowerPoint slide 7-4-9, Restoring VM in CANES
(cont.).
5) VMs that are in a recovery plan that is being tested will
display unique icons in the vCenter Server inventory at
the recovery site, as shown in Figure 3.
6) Operating system administrators and application
owners can log into their recovered VMs to verify
6
functionality and perform additional testing. Site
Recovery Manager easily supports recovery plan
testing periods of varying lengths - from a few minutes
to several days.
7) Longer tests tend to consume more storage capacity at
the recovery site. This is due to the nature of snapshot
growth as data is written to the snapshot.
8) Recommendation: Closely monitor storage capacity
utilization at the recovery site during recovery plan
tests, if capacity is limited. Configure vCenter Server
alarms to alert administrators when free space is
getting low on datastores at the recovery site.
9) When testing is complete, a recovery plan must be
“cleaned up”. This operation powers off VMs and
removes snapshots associated with the test. Once the
cleanup workflow is finished, the recovery plan is
ready for testing or running.
7. Running a Recovery Plan
Display PowerPoint slide 7-4-10, VM in CANES (cont.).
a. Running a recovery plan differs from testing a recovery
plan. Testing a recovery plan does not disrupt VMs at the
protected site. When running a recovery plan, Site
Recovery Manager will attempt to shut down VMs at the
protected site before the recovery process begins at the
recovery site.
b. Recovery plans are run when a disaster has occurred and
failover is required or when a planned migration is
desired by selecting the Run Recovery Plan button.
c. Site Recovery Manager provides two types of recovery;
Display PowerPoint slide 7-4-11, Restoring VM in CANES
7
Planned Migration and Disaster Recovery.
(cont.).
1) The Planned Migration recovers VMs to the recovery
site when both sites are running.
a) If errors occur on the protected site during a planned
migration, the planned migration operation fails.
2) Disaster Recovery recovers the VMs to the recovery
site if the protected site experiences a problem.
a) If errors occur on the protected site during a disaster
recovery, the disaster recovery continues and does
not fail.
b) The priority is recovering workloads as quickly as
possible after disaster strikes.
c) The workflow will continue even if errors occur.
The default selection is a planned migration.
3) In both cases, Site Recovery Manager will attempt to
replicate recent changes from the protected site to the
recovery site.
d. After a recovery type is selected, the operator must also
populate a confirmation checkbox as an additional safety
measure.
Display PowerPoint slide 7-4-12, Restoring VM in CANES
(cont.).
1) The idea behind this checkbox is to make sure the
operator knows that he or she is running (not testing) a
recovery plan.
e. The first step in running a recovery plan is the attempt to
synchronize storage. Then, protected VMs at the
protected site are shut down.
1) This effectively copies the VMs and commits any final
changes to disk as the VMs complete the shutdown
8
process.
2) Storage is synchronized again to replicate any changes
made during the shutdown of the VMs.
3) Replication is performed twice to minimize downtime
and data loss. Once these steps have been completed,
the recovery process at the recovery site is started.
f. If the protected site is offline due to a disaster, for
example, the disaster recovery type should be selected.
g. Site Recovery Manager will still attempt to synchronize.
Since the protected site is offline, Site Recovery Manager
will begin recovering VMs at the recovery site using the
most recently replicated data.
8. Virtual Machine Recovery Properties
a. Site Recovery Manager includes several features to
customize recovery for VMs.
Display PowerPoint
Properties.
7-4-13,
Virtual
Machine
Recovery
1) Examples include the options to change the IP address
of virtual network interface cards, run scripts, and
control the power state of VMs after they are
recovered.
b. VMs are separated into one of five priority groups. Since
these are recovery settings, these settings are accessed in
the recovery plan user interface of Site Recovery
Manager by selecting the VM Recovery Settings button.
c. There are five priority groups in Site Recovery Manager
that are created to allow VMs be grouped from 1 to 5
with the 1 being the highest priority and 5 being the least.
Display PowerPoint slide 7-4-14, Virtual Machine Recovery
Properties (cont.).
d. VMs in the same priority group are started in parallel.
1) There is no startup order guaranteed within a priority
9
group unless one or more dependencies are defined. A
dependency simply instructs one virtual machine to
start before another.
9. Recovery a Point-in-Time (PIT) Snapshot of a VM
a. In addition to the full recoveries, Site Recovery Manager
can be used to select individual VMs to restore from PIT
snapshots.
Display PowerPoint slide 7-4-15, Virtual Machine Recovery
Properties (cont.).
b. You can configure Site Recovery Manager to recover a
number of point PIT snapshots of a virtual machine when
you run a recovery plan.
c. Configure the retention of PIT snapshots when to
configure vSphere Replication on a virtual machine.
d. To enable PIT snapshots, configure replication of a
virtual machine by using the vSphere Replication
interface in the vSphere Web Client.
e. Site Recovery Manager only recovers the most recent PIT
snapshot during a recovery. To recover older snapshots,
you
must
enable
the
vrReplication
>
preserveMpitImagesAsSnapshots option in Advanced
Settings in the Site Recovery Manager interface.
Display PowerPoint slide 7-4-16, Recovery from PIT.
1) If you recover a PIT snapshot of a virtual machine for
which you have configured IP customization, Site
Recovery Manager only applies the customization to
the most recent PIT snapshot.
2) If you recover a virtual machine with IP customization
and revert to an older PIT snapshot, you must
configure the IP settings manually.
f. Point-in-time recovery is not available with array-based
replication.
10
g. Procedure to Recover a PIT Snapshot of a VM
1) Configure Site Recovery Manager to retain older PIT
snapshots by setting the vrReplication >
preserveMpitImagesAsSnapshots option.
Display PowerPoint slide 7-4-17, Recovery from PIT.
2) Use the vSphere Replication interface to configure
replication of a virtual machine, selecting the option to
retain several PIT snapshots.
3) In the Site Recovery Manager interface, add the virtual
machine to a vSphere Replication protection group.
4) Include the vSphere Replication protection group in a
recovery plan.
5) Run the recovery plan.
6) When the recovery plan is finished, the virtual machine
is recovered to the recovery site, with the number of
PIT snapshots that you configured.
7) In the VMs and Templates view, right-click the
recovered virtual machine and select Snapshot >
Snapshot Manager.
8) Select one of the PIT snapshots of this virtual machine
and click “Go To”.
9) The recovered virtual machine reverts to the PIT
snapshot that was selected.
10. MAC-1 Fail-Over
Display PowerPoint slide 7-4-18, MAC-1 Fail-Over.
a. Fail-over allows Site Recovery Manager to perform the
cross-vCenter vMotion of VMs allowing for zerodowntime disaster avoidance.
11
b. For CANES 1.2 SW, MAC-1 Fail-over functionality is
installed on Secret Enclave Data Centers to recover
previously defined protected system VMs to a defined
recovery site in the case of a failure. Recovery Plans are
defined to fail-over the Primary Data Center (VC01) to
the Alternate Data Center (VC02).
c. At installation, Primary storage is configured for Remote
Site Mirroring and both Data Centers are installed with
vCenter Site Recovery Manager Server.
1) The two Data Centers and their storage are paired for
fail-over.
2) VC01 and VC02 are designated as Protected Groups
using the Site Recovery Manager and the installed Site
Recovery Manager (SRM) Plugin.
Display PowerPoint slide 7-4-19, MAC-1 Fail-Over (cont.).
3) Recovery Plans created on VC01 and VC02 associate
the two as Protected Site and Recovery Site to support
fail-over in both directions.
d. Fail-over is manually initiated through VC01 using
vSphere Client by selecting and running the Primary Data
Center to Alternate Data Center on VC02 Recovery Plan.
At fail-over the mirrored Datastores map to the
corresponding ESX hosts.
CAUTION: Failing back to the original configuration
selects the Alternate Data Center to Primary Data Center on
VC01 Recovery Plan. It is not recommended that fleet
administrators attempt the fall back operation. Following a
fail-over. Contact the Help Desk or ISEA for assistance to
fail-back the system.
12
11. Procedures for Recovering Virtual Machines
a. Open a vSphere Client session with VC01 and select Site
Recovery from the Solutions and Applications tab of the
Home page.
Display PowerPoint slide 7-4-20, Procedures for recovering VMs.
Refer trainees to Information Sheet 7-4-1-3, Virtual Machines
(VMs) Recovery.
b. The Site Recovery Manager plugin opens.
c. Select Recovery Plans from the left column of the SRM,
plugin as shown in Figure 6
d. Select the Primary Data Center to Alternate Data Center
on VC02 recovery plan from the right pane and click
Recovery.
e. The Recovery Confirmation/Recovery Type screen
appears.
f. Run Recovery Plan in VMware.
Refer trainee to Figure 6: Recovery Plans.
Display PowerPoint slide 7-4-21, Procedures for recovering VMs
(cont.)
Display PowerPoint slide 7-4-22, Procedures for recovering VMs
(cont.).
1) On the Recovery Confirmation and Recovery Type
screen, the confirmation information is displayed and
the recovery type selection.
Refer trainee to Figure 7: Recovery Confirmation and Recovery
Type Selection Screen.
2) The recovery confirmation will display the protected
and recovery site names, the server connection status,
and the number of VM associated to that site.
Display PowerPoint slide 7-4-23, Procedures for recovering VMs
(cont.).
3) The selectable recovery types are planned migration
and disaster recovery.
4) Check the box next to “I understand that this process
will permanently alter the VMs and infrastructure of
both the protected and recovery datacenters.”
5) Select Planned migration or Disaster recovery then ok.
Display PowerPoint slide 7-4-24, Procedures for recovering VMs
(cont.).
6) Review the recovery information then click Start.
7) Select the Recovery Steps tab.
13
a) The Recent Tasks pane shows the plan execution
progress.
8) Complete the Renaming Datastores Following a MAC1 Fail-Over procedure.
Display PowerPoint slide 7-4-25, Procedures for recovering VMs
(cont.).
9) Verify that the recovered VMs are operational in the
Recovery Site by consoling into each one to ensure
they have booted correctly.
12. Summary and Review.
Display PowerPoint slide 7-4-26, Summary and Review.
a. IDENTIFY procedures to restore and recover virtual
machines.
14