Apparatus and methods for controlling a data tapping session in a storage area network

• US 8,239,477 B2
• Filed: 02/16/2006
• Issued: 08/07/2012
• Est. Priority Date: 07/08/2005
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Sharma, Samar, D'Cruz, Roy M., Krishnan, Jhaanaki M., Billore, Prashant, Dutt, Dinesh G.
• Primary Examiner(s): Lin, Kenny
• Assistant Examiner(s): LI, GUANG W
• Application Number:
  US11/356,914
• Publication Number:
  US 20070192526A1
• Time in Patent Office: 2,364 Days
• Field of Search: 709/212
• US Class Current: 709/212
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

Disclosed is a session modification mechanism for altering a data tapping process in a storage area network (SAN). In general, a data tapping mechanism is set up so that an appliance receives SAN data that is tapped from a particular SAN session. That is, the data tapping mechanism provides to a particular appliance a copy of the SAN data that is being written from a particular host to a particular storage device. The session modification mechanism allows the appliance to alter various aspects of the SAN session that is to be (or is being) tapped. Examples of various modification features includes (i) redirecting READ commands initiated by the host to the appliance and not sending such command to the storage device, (ii) redirecting both READ and WRITE commands initiated by the host to the appliance and not sending such commands to the storage device, (iii) halting redirection and thereby causing READ commands initiated by the host to be sent to the storage device and WRITE commands initiated by the host to be mirrored to both the storage device and appliance, (iv) quiescing and unquiescing all data I/O'"'"'s for the particular storage device and appliance, and (v) stopping and starting the data tapping mechanism.

Claims

1. A method of modifying a data tapping process in a storage area network (SAN), the method comprising:

at a network device of the SAN, providing a data tapping mechanism for an appliance to receive SAN data that is being sent from a host to a storage device, wherein the appliance and the storage device are both physical devices and providing the data tapping mechanism includes creating a control virtual target (CVT) for receiving requests from the appliance to modify the tapping mechanism for the appliance, a data virtual target (DVT) for intercepting data sent from the host to the storage device, one or more virtual initiators (VIs) for mirroring the intercepted data to both the storage device and the appliance, wherein the DVT has an identifier for use by the host for writing and reading data with respect to the DVT, which such data are then handled by the one or more VIs so as to write and read such data with respect to the storage device or appliance or both;

the network device receiving a request at the CVT to modify operation of the data tapping mechanism; and

the network device modifying the data tapping mechanism based on the request.

2. The method as recited in claim 1, wherein the request is:

(i) a Read Only Redirect Request and the data tapping mechanism is modified so as to redirect a READ command to the appliance when the host is sending a READ command to the storage device so that the READ command is not sent to the storage device,

(ii) a READ and WRITE Redirect Request and the data tapping mechanism is modified so as to redirect a READ command to the appliance when the host is sending the READ command to the storage device so that the READ command is not sent to the storage device and for redirecting a WRITE command to the appliance when the host is sending the WRITE command to the storage device so that the WRITE command is not sent to the storage device,

an Undo Redirect Request and the data tapping mechanism is modified so as to resume sending a READ command to the storage device when the host is sending the READ command to the storage device and mirror a WRITE command to both the storage device and appliance when the host is sending the WRITE command to the storage device, or

a Quiesce Request and the data tapping mechanism is modified so as to suspend the SAN data from being sent to the appliance and the storage device, as well as any subsequent handshaking data from being sent between the host and the storage device.

3. The method as recited in claim 1, wherein the identifier of the DVT comprises a new world wide name (WWN) and a new fibre channel network identifier (FCID) that differ from a WWN and FCID, respectively, of the storage device, wherein the new WWN and the new FCID of the DVT are configured in or obtained by the host, wherein the one or more VIs have one or more FCIDs that differ from the new FCID of the DVT.

4. The method as recited in claim 1, wherein the identifier of the DVT comprises a same world wide name (WWN) as a WWN of the storage device and a new fibre channel network identifier (FCID) that differs from an FCID of the storage device, wherein the new FCID is obtained by the host based on the WWN of the DVT, wherein the one or more VIs comprise a first VI having a first FCID for writing to the storage device and a second VI having a second FCID for writing to the appliance, wherein the first and second FCIDs of the first and second VIs differ from the FCID of the DVT, wherein the first VI has a different WWN than a WWN of the second VI.

5. The method as recited in claim 4, wherein the appliance is in a different VSAN than a VSAN of the storage device, and wherein the first VI is in a different VSAN than a VSAN of the second VI, and wherein the first and second FCIDs of the first and second VIs differ from each other.

6. The method as recited in claim 5, wherein the identifier of the DVT comprises a same world wide name (WWN) as a WWN of the storage device and a same fibre channel network identifier (FCID) as an FCID of the storage device.

7. The method as recited in claim 1, wherein the request is a Stop Request and the data tapping mechanism is modified so as to stop the SAN data from being sent to the appliance.

8. The method as recited in claim 7, further comprising:

receiving a Start Request; and

modifying the data tapping mechanism so as to start the sending of the SAN data to the appliance.

9. The method as recited in claim 8, further comprising logging any WRITE data sent by the host to the storage device as WRITE errors for the appliance;

and sending the logged WRITE errors to the appliance when the appliance requests the logged WRITE errors.

10. An apparatus for modifying a data tapping process in a storage area network (SAN), comprising:

one or more processors;

one or more memory, wherein at least one of the processors and memory are adapted for;

providing a data tapping mechanism for an appliance to receive SAN data that is being sent from a host to a storage device, wherein the appliance and the storage device are both physical devices and providing the data tapping mechanism includes creating a control virtual target (CVT) for receiving requests from the appliance to modify the tapping mechanism for the appliance, a data virtual target (DVT) for intercepting data sent from the host to the storage device, one or more virtual initiators (VIs) for mirroring the intercepted data to both the storage device and the appliance, wherein the DVT has an identifier for use by the host for writing and reading data with respect to the DVT, which such data are then handled by the one or more VIs so as to write and read such data with respect to the storage device or appliance or both;

receiving a request at the CVT to modify operation of the data tapping mechanism; and

modifying the data tapping mechanism based on the request.

11. The apparatus as recited in claim 10, wherein the request is:

(i) a Read Only Redirect Request and the data tapping mechanism is modified so as to redirect a READ command to the appliance when the host is sending a READ command to the storage device so that the READ command is not sent to the storage device,

(ii) a READ and WRITE Redirect Request and the data tapping mechanism is modified so as to redirect a READ command to the appliance when the host is sending the READ command to the storage device so that the READ command is not sent to the storage device and for redirecting a WRITE command to the appliance when the host is sending the WRITE command to the storage device so that the WRITE command is not sent to the storage device,

an Undo Redirect Request and the data tapping mechanism is modified so as to resume sending a READ command to the storage device when the host is sending the READ command to the storage device and mirror a WRITE command to both the storage device and appliance when the host is sending the WRITE command to the storage device, or

a Quiesce Request and the data tapping mechanism is modified so as to suspend the SAN data from being sent to the appliance and the storage device, as well as any subsequent handshaking data from being sent between the host and the storage device.

12. The apparatus as recited in claim 10, wherein the identifier of the DVT comprises a new world wide name (WWN) and a new fibre channel network identifier (FCID) that differ from a WWN and FCID, respectively, of the storage device, wherein the new WWN and the new FCID of the DVT are configured in or obtained by the host, wherein the one or more VIs have one or more FCIDs that differ from the new FCID of the DVT.

13. The apparatus as recited in claim 10, wherein the identifier of the DVT comprises a same world wide name (WWN) as a WWN of the storage device and a new fibre channel network identifier (FCID) that differs from an FCID of the storage device, wherein the new FCID is obtained by the host based on the WWN of the DVT, wherein the one or more VIs comprise a first VI having a first FCID for writing to the storage device and a second VI having a second FCID for writing to the appliance, wherein the first and second FCIDs of the first and second VIs differ from the FCID of the DVT, wherein the first VI has a different WWN than a WWN of the second VI.

14. The apparatus as recited in claim 13, wherein the applicance is in a different VSAN than a VSAN of the storage device, and wherein the first VI is in a different VSAN than a VSAN of the second VI, and wherein the first and second FCIDs of the first and second VIs differ from each other.

15. The apparatus as recited in claim 14, wherein the identifier of the DVT comprises a same world wide name (WWN) as a WWN of the storage device and a same fibre channel network identifier (FCID) as an FCID of the storage device.

16. The apparatus as recited in claim 10, wherein the request is a Stop Request and the data tapping mechanism is modified so as to stop the SAN data from being sent to the appliance.

17. The apparatus as recited in claim 16, wherein at least one of the processors and memory are further adapted for:

receiving an Start Request; and

modifying the data tapping mechanism so as to start the sending of the SAN data to the appliance.

18. An apparatus as recited in claim 17, wherein at least one of the processors and memory are further adapted for logging any WRITE data sent by the host to the storage device as WRITE errors for the appliance;

and sending the logged WRITE errors to the appliance when the appliance requests the logged WRITE errors.

19. An apparatus for modifying a data tapping process in a storage area network (SAN), comprising:

means for providing a data tapping mechanism for an appliance to receive SAN data that is being sent from a host to a storage device, wherein the appliance and the storage device are both physical devices and the data tapping mechanism is provided by creating a control virtual target (CVT) for receiving requests from the appliance to modify the tapping mechanismfor the appliance, a data virtual target (DVT) for intercepting data sent from the host to the storage device, one or more virtual initiators (VIs) for mirroring the intercepted data to both the storage device and the appliance, wherein the DVT has an identifier for use by the host for writing and reading data with respect to the DVT, which such data are then handled by the one or more VIs so as to write and read such data with respect to the storage device or appliance or both;

means for receiving a request at the CVT to modify operation of the data tapping mechanism; and

means for modifying the data tapping mechanism based on the request.

20. A system for modifying a data tapping process in a storage area network (SAN), comprising:

a host;

a storage device for storing data;

an appliance for tapping data in the SAN;

a network device in the SAN operable to;

provide a data tapping mechanism for an appliance to receive SAN data that is being sent from a host to a storage device, wherein the appliance and the storage device are both physical devices and the data tapping mechanism is provided by creating a control virtual target (CVT) for receiving requests from the appliance to modify the tapping mechanism for the appliance, a data virtual target (DVT) for intercepting data sent from the host to the storage device, one or more virtual initiators (VIs) for mirroring the intercepted data to both the storage device and the appliance, wherein the DVT has an identifier for use by the host for writing and reading data with respect to the DVT, which such data are then handled by the one or more VIs so as to write and read such data with respect to the storage device or appliance or both;

receive a request at the CVT to modify operation of the data tapping mechanism; and

modify the data tapping mechanism based on the request.