IP Library › Granted Patent US 12,743,349
Granted Patent B2
US 12,743,349 · App. 19/273,222 · Granted Sep 22, 2026

Systems and methods for directory service backup and recovery

Inventors: Andrei Polevoi (Westerville, OH); Robert John Bobel, III (Westerville, OH); Alexander Vadimovich Tsvetkov (Kiev, UA)
Assignee: CAYOSOFT, INC.
G06F11/1469G06F11/1464G06F2201/84
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 12,743,349
App. No.
19/273,222
Granted
Sep 22, 2026
Kind
B2
Abstract

Various implementations implement a standby directory service. For example, an example process may include obtaining user data associated with an activity of a user via a sensor in a physical environment. The process may further include, at a device including one or more processors, determining that an interruption event has occurred at a host directory service, wherein the device and the host directory service are communicatively coupled via a first network protocol associated with a first network, and in response to determining that the interruption event has occurred at the host directory service, implementing a standby directory service, wherein the standby directory service is generated and updated via a second network protocol that is different than the first network protocol.

Claims (45)

1 . A computer-implemented method comprising:

at a backup device comprising one or more processors:

receiving, from a client device, a backup request for a host directory service, wherein the client device, the host directory service, and the backup device are communicatively coupled via a first network protocol associated with a first network;

determining backup and recovery instructions associated with the host directory service, the backup and recovery instructions comprising at least one cloud storage location and at least one cloud-based recovery site;

generating, based on the backup and recovery instructions, a backup of the host directory service;

storing the backup in the cloud storage location associated with a cloud service provider network;

configuring a standby directory service within a cloud-based virtual machine environment, wherein the standby directory service comprises at least one virtual machine and corresponding network infrastructure elements provisioned in the cloud service provider network; and

in response to detecting an interruption event at the host directory service, automatically initiating failover to the standby directory service in the cloud-based virtual machine environment.

2 . The method of claim 1 , wherein the backup of the host directory service comprises directory service data, operating system files, and system configuration data.

3 . The method of claim 2 , wherein the operating system files and the system configuration data are sufficient to restore the host directory service to a virtual machine that does not have a pre-installed operating system.

4 . The method of claim 1 , wherein initiating the failover to the standby directory service in the cloud-based virtual machine environment comprises modifying network settings to redirect authentication and authorization requests to the standby directory service.

5 . The method of claim 1 , wherein the cloud service provider network is communicatively coupled with the cloud-based virtual machine environment via a second network protocol associated with a second network that is different than and isolated from the first network protocol.

6 . The method of claim 5 , wherein the second network comprises an isolated recovery environment that is separated from the first network.

7 . The method of claim 1 , wherein the standby directory service is iteratively generated and updated within the cloud-based virtual machine environment via a second network protocol associated with a second network that is different than and isolated from the first network protocol.

8 . The method of claim 7 , wherein each iteration of generating the standby directory service replaces a previous iteration of the standby service.

9 . The method of claim 1 , further comprising:

in response to initiating the failover to the standby directory service in the cloud-based virtual machine environment, iteratively performing a standby event process for a restored network environment associated with the standby directory service.

10 . The method of claim 9 , wherein the standby event process comprises at least one of installing additional backup and recovery software, performing a potential threat analysis on the first network, performing a data and service consistency check, and sending a notification to a client device.

11 . The method of claim 1 , wherein the interruption event is determined based on detecting changes of one or more objects associated with the host directory service.

12 . The method of claim 1 , wherein determining that the interruption event has occurred is based on at least one of:

determining irreversible changes of schema occurred at the host directory service;

determining a number of irreversible changes of objects at the host directory service exceeded a threshold; or

determining that a natural disaster occurred at a location of the host directory service.

13 . The method of claim 1 , wherein the host directory service comprises a set of domain controllers and metadata corresponding to network infrastructure and additional services associated with the host directory service.

14 . The method of claim 13 , wherein initiating the failover to the standby directory service in the cloud-based virtual machine environment comprises recovering directory data and the metadata corresponding to each domain controller based on determined backup and recovery instructions.

15 . The method of claim 1 , wherein the standby directory service is automatically updated based on a schedule selected from a plurality of backup and recovery options at a client device.

16 . The method of claim 1 , wherein the backup and recovery instructions are configured to automatically modify network settings associated with the host directory service to use the standby directory service in place of the host directory service.

17 . The method of claim 1 , wherein the standby directory service comprises a virtual machine or a set of virtual machines and corresponding network infrastructure elements, wherein the corresponding network infrastructure elements comprises at least one of network switches, storages, and firewalls.

18 . A backup device comprising:

a non-transitory computer-readable storage medium; and

one or more processors coupled to the non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium comprises program instructions that, when executed on the one or more processors, cause the one or more processors to perform operations comprising:

receiving, from a client device, a backup request for a host directory service, wherein the client device, the host directory service, and the backup device are communicatively coupled via a first network protocol associated with a first network;

determining backup and recovery instructions associated with the host directory service, the backup and recovery instructions comprising at least one cloud storage location and at least one cloud-based recovery site;

generating, based on the backup and recovery instructions, a backup of the host directory service;

storing the backup in the cloud storage location associated with a cloud service provider network;

configuring a standby directory service within a cloud-based virtual machine environment, wherein the standby directory service comprises at least one virtual machine and corresponding network infrastructure elements provisioned in the cloud service provider network; and

in response to detecting an interruption event at the host directory service, automatically initiating failover to the standby directory service in the cloud-based virtual machine environment.

19 . The backup device of claim 18 , wherein initiating the failover to the standby directory service in the cloud-based virtual machine environment comprises modifying network settings to redirect authentication and authorization requests to the standby directory service.

20 . A non-transitory computer-readable storage medium, storing program instructions executable on a backup device including one or more processors to perform operations comprising:

receiving, from a client device, a backup request for a host directory service, wherein the client device, the host directory service, and the backup device are communicatively coupled via a first network protocol associated with a first network;

determining backup and recovery instructions associated with the host directory service, the backup and recovery instructions comprising at least one cloud storage location and at least one cloud-based recovery site;

generating, based on the backup and recovery instructions, a backup of the host directory service;

storing the backup in the cloud storage location associated with a cloud service provider network;

configuring a standby directory service within a cloud-based virtual machine environment, wherein the standby directory service comprises at least one virtual machine and corresponding network infrastructure elements provisioned in the cloud service provider network; and

in response to detecting an interruption event at the host directory service, automatically initiating failover to the standby directory service in the cloud-based virtual machine environment.

Assignments (2)
SECURITY INTEREST Recorded Sep 29, 2025
From: CAYOSOFT, INC.
To: CANADIAN IMPERIAL BANK OF COMMERCE
Reel/Frame 072409/0501 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2025
From: POLEVOI, ANDREI; BOBEL, ROBERT JOHN, III; TSVETKOV, ALEXANDER VADIMOVICH
To: CAYOSOFT, INC.
Reel/Frame 071753/0518 →
Continuity (4)
Continuation 18808532 · Aug 19, 2024
Continuation 18116573 · Mar 2, 2023
Provisional Application 63315748 · Mar 2, 2022
Related Publication 20250342092A1 · Nov 6, 2025
References Cited (11)
US 7159234B1 · Murphy et al. · 2007 [cited by applicant]
US 8191078B1 · Cullen et al. · 2012 [cited by applicant]
US 8332442B1 · Greene · 2012 [cited by applicant]
US 9053236B1 · Covarrubias et al. · 2015 [cited by applicant]
US 10346085B1 · Teverovsky et al. · 2019 [cited by applicant]
US 20040153709A1 · Burton-Krahn · 2004 [cited by applicant]
US 20180103033A1 · Kalitin et al. · 2018 [cited by applicant]
WIPO, International Search Report and Written Opinion issued Jun. 21, 2023, which pertains to PCT Application No. PCT/US2023/014339. 18 pages. [cited by applicant]
IP Australia, Notice of Acceptance for Patent Application, Australian Patent Application No. 2023228872, 3 pages, Jan. 22, 2026. [cited by applicant]
Intellectual Property India, Examination Report, Indian Patent Application No. 202417065115, 8 pages, Nov. 14, 2025. [cited by applicant]
IP Australia, Examination Report No. 1 for Standard Patent Application issued in Australian Patent Application No. 2026202188 dated Jun. 4, 2026 (Two (2) pages). [cited by applicant]