Browse Prior Art Database

Identifying the Most Recent Backup with Persistent Flashcopy

IP.com Disclosure Number: IPCOM000010240D
Original Publication Date: 2002-Nov-11
Included in the Prior Art Database: 2002-Nov-11
Document File: 1 page(s) / 39K

Publishing Venue

IBM

Abstract

A method for determining the status of the most recent backup when multiple backup copies are desired.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 78% of the total text.

Page 1 of 1

Identifying the Most Recent Backup with Persistent Flashcopy

Disclosed is a method for determining the status of the most recent backup copy of a volume, when multiple backup copies are desired.

Current technology for Point-in-Time (PIT) copy causes the relationship between the Source and Target volumes to dissolve once the data is actually copied. This problem exists for implementations such as IBM *FlashCopy, where copy completion ends the relationship. A query of the volumes once the copy is complete would indicate that there is no relationship active. Thus, a user cannot determine if:

He or she actually invoked a FlashCopy command

The FlashCopy completed successfully and therefore, the relationship automatically


1.


2.

ended

Furthermore, a user that is keeping multiple backups (targets) cannot determine which backup is the most recent. In order to solve this problem, it is useful to retain knowledge of the relationship long after the backup copy is actually formed. This invention describes a solution for IBM FlashCopy, in which the FlashCopy relationship is marked as "Persistent". When a FlashCopy relationship is marked as Persistent, the relationship between the source and target volumes remains intact until an explicit "withdraw FlashCopy" command is submitted. This allows a user to query the FlashCopy relationship well after it completes and determine with a high level of confidence that the copy actually occurred. Furthermore, since the source and target v...