IP Library Granted Patent US 10,592,133
Granted Patent B1
US 10,592,133 · App. 15/856,216 · Granted Mar 17, 2020

Managing raw device mapping during disaster recovery

Inventors: Sujay Bothe (Ahmadnagar, IN); Aditya Deshpande (Pune, IN)
Assignee: VERITAS TECHNOLOGIES LLC
G06F3/0619G06F3/065G06F3/067G06F3/0665G06F9/45558G06F2009/45583
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,592,133
App. No.
15/856,216
Granted
Mar 17, 2020
Kind
B1
Abstract

Disclosed herein are methods, systems, and processes for managing raw device mapping during disaster recovery. A raw device mapping (RDM) file operation is assigned to a virtual device associated with a virtual machine that is replicated from a premise site. A determination is made that a RDM file associated with the virtual device is invalid or is not replicated after the virtual machine is replicated to a target site. Based on the determination that the RDM file is invalid or is not replicated, the virtual device is removed from the virtual machine and the assigned RDM file operation is performed.

Claims (98)

1. A computer-implemented method, comprising

assigning a raw device mapping (RDM) file operation to a virtual device, wherein

the virtual device is associated with a virtual machine, and

the virtual machine is replicated from a premise site;

determining that a RDM file associated with the virtual device is invalid or is not replicated after the virtual machine is replicated to a target site; and

based on the determining that the RDM file is invalid or is not replicated,

removing the virtual device from the virtual machine, and

performing the assigned RDM file operation.

2. The computer-implemented method of claim 1 , wherein the assigned RDM file operation comprises

a create operation,

a replace operation, or

a no operation.

3. The computer-implemented method of claim 2 , wherein determining that the RDM file is invalid comprises

determining that a source Logical Unit Number (LUN) and a target LUN associated with the virtual device have different World Wide Number Identifiers (WWN IDs), or

determining that the RDM file is not stored with the virtual machine.

4. The computer-implemented method of claim 3 , wherein determining that the RDM file is valid and can be utilized comprises

determining that the source LUN and the target LUN of the virtual device share a WWN ID, and

determining that the RDM file is stored with the virtual machine.

5. The computer-implemented method of claim 2 , further comprising:

creating the virtual device on the target site;

generating a new RDM file if the assigned RDM file operation is the create operation;

replacing the RDM file with the new RDM file if the assigned RDM file operation is the replace operation;

utilizing the RDM file if the assigned RDM file operation is the no operation; and

attaching the virtual device to the virtual machine that is replicated from the premise site to the target site.

6. The computer-implemented method of claim 2 , further comprising:

determining that the RDM file is shared between the virtual machine and one or more virtual machines;

assigning the create operation or the replace operation to a first virtual device of a plurality of virtual devices;

assigning the no operation to the plurality of virtual devices other than the first virtual device; and

creating the first virtual device prior to creating the plurality of virtual devices other than the first virtual device.

7. The computer-implemented method of claim 2 , further comprising:

determining that the virtual machine is replicated from the premise site to the target site as part of a hypervisor-based replication process; and

assigning the create operation to the virtual device associated with the virtual machine.

8. The computer-implemented method of claim 2 , further comprising:

receiving information indicating that the source LUN and the target LUN have different WWN IDs, that source LUN and the target LUN share the WWN ID, that the RDM file is not stored with the virtual machine, or that the RDM file is stored with the virtual machine, from a premise computing device executing on the premise site.

9. A non-transitory computer readable storage medium comprising program instructions executable to:

assign a raw device mapping (RDM) file operation to a virtual device, wherein

the virtual device is associated with a virtual machine, and

the virtual machine is replicated from a premise site;

determine that a RDM file associated with the virtual device is invalid or is not replicated after the virtual machine is replicated to a target site; and

based on a determination that the RDM file is invalid or is not replicated,

remove the virtual device from the virtual machine, and

perform the assigned RDM file operation.

10. The non-transitory computer readable storage medium of claim 9 , wherein the assigned RDM file operation comprises

a create operation,

a replace operation, or

a no operation.

11. The non-transitory computer readable storage medium of claim 10 , wherein the program instructions executable to determine that the RDM file is invalid comprise further program instructions executable to

determine that a source Logical Unit Number (LUN) and a target LUN associated with the virtual device have different World Wide Number Identifiers (WWN IDs), or

determine that the RDM file is not stored with the virtual machine, or the program instructions executable to determine that the RDM file is valid and can be utilized comprise further program instructions executable to

determine that the source LUN and the target LUN of the virtual device share a WWN ID, and

determine that the RDM file is stored with the virtual machine.

12. The non-transitory computer readable storage medium of claim 10 , further comprising further program instructions executable to:

create the virtual device on the target site;

generate a new RDM file if the assigned RDM file operation is the create operation;

replace the RDM file with the new RDM file if the assigned RDM file operation is the replace operation;

utilize the RDM file if the assigned RDM file operation is the no operation; and

attach the virtual device to the virtual machine that is replicated from the premise site to the target site.

13. The non-transitory computer readable storage medium of claim 10 , further comprising further program instructions executable to:

determine that the RDM file is shared between the virtual machine and one or more virtual machines;

assign the create operation or the replace operation to a first virtual device of a plurality of virtual devices;

assign the no operation to the plurality of virtual devices other than the first virtual device; and

create the first virtual device prior to creating the plurality of virtual devices other than the first virtual device.

14. The non-transitory computer readable storage medium of claim 10 , further comprising further program instructions executable to:

determine that the virtual machine is replicated from the premise site to the target site as part of a hypervisor-based replication process; and

assign the create operation to the virtual device associated with the virtual machine.

15. A system comprising:

one or more processors; and

a memory coupled to the one or more processors, wherein the memory stores program instructions executable by the one or more processors to

assign a raw device mapping (RDM) file operation to a virtual device, wherein

the virtual device is associated with a virtual machine, and

the virtual machine is replicated from a premise site;

determine that a RDM file associated with the virtual device is invalid or is not replicated after the virtual machine is replicated to a target site; and

based on a determination that the RDM file is invalid or is not replicated,

remove the virtual device from the virtual machine, and

perform the assigned RDM file operation.

16. The system of claim 15 , wherein the assigned RDM file operation comprises

a create operation,

a replace operation, or

a no operation.

17. The system of claim 16 , wherein the program instructions executable by the one or more processors to determine that the RDM file is invalid comprise further program instructions executable by the one or more processors to

determine that a source Logical Unit Number (LUN) and a target LUN associated with the virtual device have different World Wide Number Identifiers (WWN IDs), or

determine that the RDM file is not stored with the virtual machine, or the program instructions executable by the one or more processors to determine that the RDM file is valid and can be utilized comprise further program instructions executable by the one or more processors to

determine that the source LUN and the target LUN of the virtual device share a WWN ID, and

determine that the RDM file is stored with the virtual machine.

18. The system of claim 16 , further comprising further program instructions executable by the one or more processors to:

create the virtual device on the target site;

generate a new RDM file if the assigned RDM file operation is the create operation;

replace the RDM file with the new RDM file if the assigned RDM file operation is the replace operation;

utilize the RDM file if the assigned RDM file operation is the no operation; and

attach the virtual device to the virtual machine that is replicated from the premise site to the target site.

19. The system of claim 16 , further comprising further program instructions executable by the one or more processors to:

determine that the RDM file is shared between the virtual machine and one or more virtual machines;

assign the create operation or the replace operation to a first virtual device of a plurality of virtual devices;

assign the no operation to the plurality of virtual devices other than the first virtual device; and

create the first virtual device prior to creating the plurality of virtual devices other than the first virtual device.

20. The system of claim 16 , further comprising further program instructions executable by the one or more processors to:

determine that the virtual machine is replicated from the premise site to the target site as part of a hypervisor-based replication process; and

assign the create operation to the virtual device associated with the virtual machine.

Assignments (11)
AMENDMENT NO. 1 TO PATENT SECURITY AGREEMENT Recorded Apr 8, 2025
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 070779/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2025
From: VERITAS TECHNOLOGIES LLC
To: COHESITY, INC.
Reel/Frame 070335/0013 →
RELEASE OF SECURITY INTEREST Recorded Dec 16, 2024
From: ACQUIOM AGENCY SERVICES LLC, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069697/0238 →
RELEASE OF SECURITY INTEREST Recorded Dec 13, 2024
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 069634/0584 →
SECURITY INTEREST Recorded Dec 9, 2024
From: VERITAS TECHNOLOGIES LLC; COHESITY, INC.
To: JPMORGAN CHASE BANK. N.A.
Reel/Frame 069890/0001 →
ASSIGNMENT OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Nov 25, 2024
From: BANK OF AMERICA, N.A., AS ASSIGNOR
To: ACQUIOM AGENCY SERVICES LLC, AS ASSIGNEE
Reel/Frame 069440/0084 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS AT R/F 052426/0001 Recorded Nov 30, 2020
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 054535/0565 →
SECURITY INTEREST Recorded Aug 20, 2020
From: VERITAS TECHNOLOGIES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
Reel/Frame 054370/0134 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Apr 16, 2020
From: VERITAS TECHNOLOGIES, LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 052426/0001 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Mar 18, 2020
From: VERITAS TECHNOLOGIES LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 052189/0311 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 2, 2018
From: BOTHE, SUJAY
To: VERITAS TECHNOLOGIES LLC
Reel/Frame 045243/0780 →