FlashCopy for IBM i

There will be a moment of silence while I start the recorder.

*

Chuck Losinski

Director of Automation Technology

Robot

Broadcasting live from Eden Prairie, Minnesota

Chuck Stupca

IBM i Expert

IBM (retired)

FlashCopy for IBM i

*

*

Things to do before the show.

1. Upload the presentation and lobby slides 15-20 minutes ahead of time.

2. Change rights for attendees to only chat with panelist

3. Change event options and get rid of Q&A

4. Auto Advance the lobby Slides

5. Do audio checks very so often, talk about new features, new products, weather, kid sporting events, the Twins, etc. Ice fishing.

There will be a moment of silence while I start the recording.

Agenda

FlashCopy DefinedHow FlashCopy WorksFlashCopy OptionsFlashCopy Space EfficienciesAutomation Opportunities

*

What is FlashCopy?

A function that occurs within a SAN storage deviceProvides a point-in-time copy of the contents of disk volumesCan be a full system or an IASPMany options for the copy process availableDifferences between V7000 and DS8000

Save While Active

Before starting a discussion of FlashCopy, lets review a more familiar
point-in-time copy: Save While Active

When a Save While Active is started, a sync point is reached before
the save operation starts (this may take some time)

The objects to be saved are marked for processing by the save

Users may begin to use the objects being saved

If an object is changed, before it has been saved, the original
information is moved to a shadow area

When the save operation reaches the changed information,
the original information is saved from the shadow area

FlashCopy Basics

A FlashCopy takes place within a single storage unityou cannot flash
from one storage device to anotherFlashCopy is a physical copy of the disk unitthe storage unit has no
concept of objectsLogical saves (SAVOBJ, SAVLIB, etc.) can be taken from the FlashCopy unitsThere are many different options when you take a DS8000 FlashCopyA system or IASP may be quiesced in order to reach a sync point
(usually a matter of seconds)highly recommendedTwo basic forms of FlashCopyFlashCopy with copyFlashCopy no copy

FlashCopy with Copy

The contents of all disk units in the FlashCopy operation are copied
from source volumes to target volumes.

Source Volumes

Target Volumes

FlashCopy with Copy

Force all changes from main storage to the source volumes and issue the FlashCopy command. A bitmap with all zeroes is generated by the DS.

000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy with Copy

Each track is copied from the source volumes to the target volumes. As the tracks are copied, the corresponding bit in the mask is changed from 0 to 1.

111111111100000000000000000000000000000000000000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy with Copy

Since both the source and target volumes are available for use, the bitmap directs users of the target volumes to the location of the information being used:

1 = use the target volume

0 = use the source volume

111111111100000000000000000000000000000000000000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy with Copy

Since the source volumes are in use, what happens when a track that hasnt been copied is changed in the source volumes?

111111111100000000000000000000000000000000000000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy with Copy

Before the change is written to the source volume, the original track
is copied to the target volume and the corresponding bit is set to 1.

111111111100000000000000000000000000000000001000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy with Copy

Since the bit of the changed track is set to 1, the users of the target volumes know that the correct data is in the targetkind of like Save While Active knowing to use the shadow area.

111111111100000000000000000000000000000000001000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy with Copy

Eventually, all tracks are copied from the source to the target. At this point, the default FlashCopy operation is complete and the bitmap is removed. There is
no longer a relationship between the source and target volumes.

11111111111111111111111111111111111111111111111111111111111111111111111111111111

Bitmap

Source Volumes

Target Volumes

FlashCopy with Copy

Now you have a full copy of the original source volumes to use!

Source Volumes

Target Volumes

FlashCopy with Copy

What happens when a track that hasnt been copied is changed in the
target? The change is written to the target volume and the bit is set to 1.
The track will not be copied from the source to the target.

111111111100000000000000000000000000000000001000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy no Copy

Only the contents of changed tracks on disk units in the FlashCopy operation are copied from source volumes to target volumes.

Source Volumes

Target Volumes

FlashCopy no Copy

Force all changes from main storage to the source volumes and issue the FlashCopy command. A bitmap with all zeroes is generated by the DS.

000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy no Copy

No background copy of source tracks to target tracks is performed.

000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy no Copy

When a track in the source volumes is being changed, the track is copied
to the source, and the corresponding bit is set to 1.

000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy no Copy

Only the original contents of changed tracks are moved to the targets.

000000000000100000000000000010000000000000010000000000000000000000000000001000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy no Copy

Changes to the target system cause the copy bit to be set to 1. This will prevent a change to the source from overwriting the target change with original data.

000000000000100000000000000010000000000000010000000000000000000000000100001000000000000000

Bitmap

Source Volumes

Target Volumes

FlashCopy no Copy

The relationship between the source and target remains in place until
all source tracks have been changed (highly unlikely).Usually the flash copy relationship is explicitly removed when the user
has finished using the targets.This form of FlashCopy is typically used to save objects on a partition
that is different from the production partition.Since few of the tracks are likely to change during the save operation,
there may be contention for access to the source volumesusually the interference is not noticeable.

FlashCopy V7000

Source and target volumes are specified using a mapping operationTarget volumes must be identical in size to the source volumesMultiple volumes may be placed in a consistency groupSimilar to a DS FlashCopy of multiple volumesProvides a point-in-time copy for all volumes in the consistency groupRather than copying tracks, V7000 copies grainsUser specifies the size of a grainMay be 64K 256KDefault is 256KFlashCopy on V7000 is with copy

Other DS8000 FlashCopy Options

Persist: keep a FlashCopy relationship in placeRecord: keep track of changes made since the last point in time copyOften used in conjunction with the persist optionTarget inhibit: prevent writing to the target volumesDo not use with IBM i

Using Persist and Record

Most often used to update target volumes copied using FlashCopy with copyAt the completion of the full copy from source to target,
the bitmap between source and target is retainedBecause record is also specified, a second bitmap is used to record the changes on the source volumes and target volumesAt the next instance for FlashCopy, a variation called
Resync flash is used

Resync Flash

Changes to tracks in both sets of volumes are recorded in the bitmapRemember that our original flash was a point-in-time flash of the
source volumes

001000000000100000000000000010000000010000010000000000000001000000000000001000001000000000

Bitmap

Source Volumes

Target Volumes

Resync Flash

In order to restore the changed tracks in the target to the values in the original FlashCopy, the changes will be backed out using the unchanged pages in
the source.

001000000000100000000000000010000000010000010000000000000001000000000000001000001000000000

Bitmap

Source Volumes

Target Volumes

Resync Flash

Full copy of source volumes must be completedWhen a resync flash is issued, a second bitmap of all zeroes
is createdChanges that occur while the resync flash is taking place are recorded in the second bitmapChanges to a track in a source volume will cause the original track to be written to the targetChanges to a track in a target volume are more complicated

Resync FlashChanges to Target Volumes

Condition 1 the track is not scheduled to be copied during the resync flash

The change is made to the target volume and the corresponding bit in the change recording
bitmap for the next resync is set to 1.The track will not be copied from the source volume to the target volume.

Condition 2 the track is scheduled for resync and has already been copied from the source

The track on the target is changed.The corresponding bit in the change recording bitmap for the next resync is set to 1.

Condition 3 the track is scheduled for resync but has not yet been copied from the source

The track on the target is changed and the corresponding bit in the change recording bitmap
for the next resync is set to 1.The track will not be copied from the source volume to the target volume.

Why Use FlashCopy

Clone an IASP or system using FlashCopy with copyUse the target volumes for save operationsIPL the full system flash with special handlingSystem nameIP addressesVary on a FlashCopy IASPIn the event that the source volumes become mucked,
the target volumes provide a quick recovery to the point
in time of the FlashCopy

Saving Objects from a FlashCopy

The save is taking place on a different systemAn IBM i has an operating system option for saving from a full systemThe production system will not have the date of last save changedIBM i will adjust the catalog to spoof a save from the production systemSaving from an IASP attached to a different partition is much easierThe save is still done on a different system/partitionIBM i has an option to update the last saved information in the source IASPLab Services Toolkit provides an automated process for both full system and IASP FlashCopy

Space Efficient FlashCopy

To this point, the target volumes in either a DS8000 or a V7000 have been the same size as the source volumes (fully provisioned).Do we need fully provisioned targets?FlashCopy no copy will not copy everythingOften times, target volumes have a short life span, e.g., they exist only until a save operation is completeIn a DS8000, we can use targets that are smaller than the source volumes (thin provisioning).

Space Efficient FlashCopy

The DS8000 targets are configured differently.

Space is allocated for the target volumes.

Allocated space is a percentage of the space for the source volumes.

Choose a percentage that will not overflow during the save operation.

Source Volumes

Space Efficient FlashCopy

Virtual target volumes are defined to be the same size as the source volumes.

There is a mapping between the tracks of the target volumes and the actual disk space used for the FlashCopy.

The DS8000 targets are configured differently.

Source Volumes

Target Volumes

Space Efficient FlashCopy

A change to a track in the source causes the original track to be written to the allocated area.

The bitmap between source and target indicates that the original page is in the virtual target disk.

Source Volumes

Target Volumes

The DS8000 targets are configured differently.

Space Efficient FlashCopy

When a user of the target volumes accesses the changed page, the bitmap directs the read to the target volume.

The changed track in the target volume is mapped to original information in the allocated area.

Source Volumes

Target Volumes

The DS8000 targets are configured differently.

FlashCopy Summary

Contained within a single storage unitA fast way to establish a point-in-time image of volumes
(disk units) in IBM iCopies are physical, not logical i.e., there is no way to restore individual objects from a FlashCopyCan make full system or IASP copiesSave operations can be performed on the target unitsSpace efficient FlashCopy reduces storage requirements

Resources

RedbooksSG24-7938 Overview of the IBM Storwize V7000SG24-8886 IBM System Storage DS8000: Architecture and ImplementationSG24-7120 IBM i and IBM System StorageSG24-7103 IBM System Storage Copy Services and IBM iSG24-6788 IBM System Storage DS8000 Copy Services for Open SystemsIBM EducationAS541 IBM PowerHA for IBM i, Clustering, and IASP Implementation (4 days)OS830 System Storage DS6000 and DS8000 on I (3 days)STG Lab Services IASP Copy Services Toolkit (2 versions)Full System FlashCopy Toolkit

Automation Opportunities

Many of the Robot products can exploit this technologyRobot/SCHEDULE to automate the FlashCopy executionRobot/SAVE to execute and track your backup to mediaRobot/CONSOLE to monitor for FlashCopy messagesRobot/ALERT to notify you of any issuesRobot/SPACE to track disk usage statistics, notify of growth thresholds and automate cleanup tasks

Automated Job Scheduling

- Improve uptime

- Eliminate errors

- Avoid overtime

- Save time with automated documentation

- Event-based scheduling more effective

Performance Management

- Dynamic expert tuning

- Proactive disk saving

- Capture runaway jobs fast

- Managed impact of change

- Easy to show that SLAs have been met

Message Management

- View only important messages

- Acknowledge important messages

- Single pane of glass view

- Maximize uptime

- Easy to locate cause of errors

Disaster Recovery

- Automate save and restore

- Flexible tape management

- Reliable, unattended backups

- Powerful data security and audit

- Simplified disaster recovery planning

Robot systems management solutions save money and help improve competitiveness.

Automation Opportunities

Robot/SCHEDULE, Enterprise, and Replay

Event-driven scheduling | Flexibility to react to changing events

Schedule Activity Monitor | Powerful scheduling dashboard

Replay | Automates interactive green-screen tasks

Cross Partition Dependencies | Add Robot/NETWORK

Cross Platform Dependencies | Add Robot/SCHEDULE Enterprise

Sophisticated calendars | Adapt to any schedule or fiscal year

Dynamic parameters | Support unattended job submission

Good Morning Report | Keeps you posted on nightly activity

Job blueprints | Generate graphical views of job flow

Database | All data and schedules are stored on the IBM i

Job Blueprint shows you job dependencies between jobs, partitions and platforms!

The worlds most advanced job scheduler for IBM i.

Robot Plug-In Modules:

Robot/SCHEDULE SAP Interface Robot/SCHEDULE Oracle E1 Interface Robot/REPLAY Robot/NETWORK

Event-Driven Job Scheduling for IBM i and Windows, Unix, Linux and Interactive Tasks

ROBOT/SCHEDULE

*

Related Robot products: Robot/ALERT and Robot/NETWORK

Robot/CONSOLE and Robot/ALERT

System Message and Resource Management

Message management | Handle messages automatically

Message notification | Escalate only important messages

OPAL | Defines complex message processing

SNMP SMS SMTP 2-way | Add Robot/ALERT

Consolidated monitoring | Add Robot/NETWORK

Resource monitoring | Keep resources healthy

System log monitoring | Maintain security and compliance

Message history | Detailed historical message analysis

Good Morning Report | Keeps you posted on nightly activity

Powerful interface | Easy to use

Message set creation wizard | Easy to install

Automate message responses and resource monitoring such as: CPU, subsystem, line, job queue, and output queue. Escalate only the exceptions and reply remotely.

Automated system monitoring. Dont be tied to your screen.

ROBOT/CONSOLE

*

Robot/SAVE

Automated backup | Eliminate save errors

IFS groups | Easily manage IFS backups and restores

Data encryption | Secure mission critical data

Save media management | Error-free media handling

Data centre management | Multi-system/data centre support

Centralized scratch pool | Reuse media across multiple systems

Guided restoration | Improves Recovery Time Objective (RTO)

Object archive | Easy to restore prior versions of data/objects

Restricted State Utility | Safe, unattended system-level saves

Ad hoc operations | Management of media outside of DR

Reports | Comprehensive DR documentation suitable for audit

Move Sets help manage the location of save media at all times.

Disaster Recovery

ROBOT/SAVE

Related Robot products: Robot/SCHEDULE Robot/ALERT Robot/NETWORK

Its more than save and restore, its a whole DR solution.

*

Robot/SPACE

Critical Storage Investigator | Identify storage problem causes

Collection explorer | Graphical storage statistics and trends

Storage audits | Automated disk cleanup

ASP monitors | Monitor ASPs individually

Active job storage monitoring | Identify out of control jobs fast

Storage collections | Flexible, user-defined statistical groupings

Robot/QUERY | Flexible, user-defined storage analysis

Reports | Assist in monitoring storage space

Critical Storage Investigator (CSI) allows easy identification of storage problems.

Proactive Storage Management

ROBOT/SPACE

Related Robot products: Robot/SCHEDULE Robot/ALERT Robot/NETWORK

Save disk space. Predict future space requirements. Avoid critical storage conditions.

*

Questions?

PRESENTATION RECAP:

FlashCopy DefinedHow FlashCopy WorksFlashCopy OptionsWith and without copyResync flashPersist and recordRunning savesFlashCopy Space EfficienciesRobot automation opportunities

*

*

Thank you for joining us today!

Telephone: 800-328-1000 sales

952-933-0609 support

Website: www.helpsystems.com

Presenters: chuck.losinski@helpsystems.com | 952-563-2790

jcstupca@msn.com

Contact Information

Chuck Losinski

Director of Automation

Technology, Robot

Chuck Stupca

IBM i Expert

IBM (retired)

*

That concludes our show.