Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claim Objections
Claims 19 and 20 objected to because of the following informalities: Claim 19 and claim 20 depend on claim 1. This appears to be a typographical error. Appropriate correction is required.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1, 3, 4, 6-8, and 10 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 2, 3, 4, 8, and 10 of US 12450129 B2 in view of Bezbaruah US 20220398163 A1
Although the claims at issue are not identical, they are not patentably distinct from each other because the bolded elements of claim 1, 2, 3, 4, 8, and 10 of ‘129 teaches the corresponding bolded elements in instant claim 1, 3, 4, 6-8, and 10. See chart below.
It appears ‘129 fails to explicitly teach “enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO for the first database.
However, Bezbaruah teaches “enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO for the first database” in para. 11
The embodiments described herein are directed to a high frequency snapshot technique configured to reduce duration of data replication and improve recovery point objectives (RPO) in a disaster recovery (DR) environment. A data object (e.g., a virtual disk) at a primary site is designated for failover to a secondary site in the event of failure of the primary site. . .
A temporary staging file is provided at the secondary site to continually apply the replicated LWSs (“high-frequency snapshots”) as incremental changes to synthesize snapshots of those changes at the secondary site prior to completion of the base snapshot replication. In such a manner, the base snapshot and the synthesized snapshots capturing changes during the transfer of the base snapshot become available at the secondary site at substantially a same time once replication of the base snapshot completes because the incremental changes and the base snapshot are transferred concurrently. Notably, the staging file is populated with the LWSs in parallel with the replication of the base snapshot at the placeholder file. At a subsequent predetermined time interval (e.g., hourly interval), the accumulated LWSs may be combined (synthesized) to capture a “checkpoint” snapshot by applying (processing) the accumulated LWSs at the staging file to, e.g., “prune” or eliminate any overwrites or stale data associated with the accumulated LWSs within the file. Once the base snapshot is fully replicated (completes), the pruned LWSs (deltas) are applied to the base snapshot to synchronize the replicated failover data so that the base snapshot is up to date with a latest LWS.
Bezbaruah and claims 1, 2, 3, 4, 8, and 10 of ‘129 are analogous art because they are from same field of endeavor as the claimed invention.
It would have been obvious to one skilled in the art before the effective filing date of the invention to modify the method in claim 1 of
129 to include ““enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO for the first database” as taught by Bezbaruah.
The motivation would have been to “reduc[e] convergence time and improve RPO in a disaster recovery (DR) environment.” Bezbaruah para. 11.
US 12450129 B2
Instant
1. A system comprising: a first computing device comprising one or more first hardware processors, wherein the first computing device is in communication with a second computing device comprising one or more second hardware processors; and wherein the second computing device is configured to
1. A computer-implemented method comprising enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO for the first database comprises:
by a first computing device comprising one or more first hardware processors:
host a database management system that comprises a first database,
hosting a database management system that comprises the first database,
convert a first set of transaction logs generated by the database management system into a first set of temporary backup files, wherein the first set of temporary backup files are in a backup format that that is distinct from a data format that is native to the database management system,
converting first transaction logs generated by the database management system into first temporary backup files that are configured in a backup format that that is distinct from a data format that is native to the database management system, and
based on a time interval of a recovery point objective (RPO) that is associated with the first database,
transmit the first set of temporary backup files to the first computing device;
(It would have been obvious to modify the first device in ‘129 to include a second device. The motivation would have been to maintain data integrity and decrease the possibility of data loss. )
based on a time interval of the RPO,
transmitting the first temporary backup files to a second computing device that comprises one or more second hardware processors and is distinct from the first computing device; and
and wherein the first computing device is configured to:
store the first set of temporary backup files at a first data storage,
by the second computing device:
storing the first temporary backup files at a first data storage, which is distinct from the first computing device
based on a second time interval that is greater than the time interval of the RPO,
make a determination that the first data storage comprises at least one temporary backup file received from the second computing device, and based on the determination:
based on a second time interval that is greater than the time interval of the RPO,
making a determination that the first data storage comprises at least
one temporary backup file received from the first computing device, and based on the determination:
(i) convert the at least one temporary backup file into one or more secondary copies,
(i) converting the at least one temporary backup file into one or more secondary copies, and
(ii) store the one or more secondary copies at a secondary storage that is distinct from the first data storage, and
storing the one or more secondary copies at a secondary storage that is distinct from the first data storage.
(iii) index the one or more secondary copies in an index.
2. The system of claim 1, wherein the system further comprises a third computing device
3. The computer-implemented method of claim 1, further comprising, by a third computing device
comprising one or more third hardware processors, which is configured to:
host a storage manager,
comprising one or more third hardware processors:
hosting a third computing device,
receive, from the first computing device, information about a data storage job performed by the first computing device,
(Examiner finds storage job teaches secondary copies)
receiving, from the second computing device, information about the one or more secondary copies,
wherein the data storage job comprises the (i) convert operation, the (ii) store operation at the secondary storage, and the (iii) index operation, which are performed by the first computing device,
and store the information about the data storage job at a management database
maintained by the storage manager, wherein the management database is distinct from the first database.
and storing the information at a management database
maintained by the third computing device, wherein the management database is distinct from the first database.
3. The system of claim 2, wherein the storage manager is further configured to:
4. The computer-implemented method of claim 3, further comprising: by the third computing device that hosts the third computing device:
receive a request to restore data to the first database,
initiate a restore job at the first computing device,
wherein the restore job is based on a second set of temporary backup files that comprise the data to be restored to the first database;
receiving a request to restore first data to the first database,
causing the second computing device to identify a set of temporary backup files that comprise the first data to be restored,
wherein the first computing device is further configured to
transmit the second set of temporary backup files to the second computing device;
and causing the second computing device to
transmit the set of temporary backup files to the first computing device;
and wherein the second computing device is further configured to
convert the second set of temporary backup files into a second set of transaction logs,
and by the first computing device:
converting the set of temporary backup files into a corresponding set of transaction logs,.
wherein the second set of
transaction logs are in the data format
that is native to the database management system.
wherein the corresponding set of transaction logs are in the data format that is native to the database management system
4. The system of claim 1, wherein a first data agent hosted by the second computing device is configured to
6. The computer-implemented method of claim 1, further comprising: by a first data agent hosted by the first computing device:
convert the first set of transaction logs generated by the database management system into the first set of temporary backup files,
converting the first transaction logs generated by the database
management system into the first temporary backup files
and to transmit the first set of temporary backup files
to the first computing device.
and transmitting the first
temporary backup files
to the second computing device.
6. The system of claim 4, wherein the first data agent is configured to:
7. The computer-implemented method of claim 6, further comprising, by the first data agent:
receive the RPO from a storage manager that is hosted by a third computing device,
receiving the RPO from a third computing device that is hosted by a third computing device,
and subsequently, based on the RPO, to
(Claim 1 of ‘129 teaches time interval)
and subsequently, based on the time interval of the RPO,
transmit the first set of temporary backup files to the first computing device
transmitting the first temporary backup files to the second computing device
without receiving instructions to do so from the storage manager.
without receiving instructions to do so from the third computing device.
8. The system of claim 1,
wherein the first computing device is further configured to determine,
based on the second time interval, that the first computing device should initiate a data storage job that comprises the
8. The computer-implemented method of claim 1, further comprising,
by the second computing device:
based on the second time interval, determining that the second computing device should initiate a data storage operation that comprises
(i) convert operation, the (ii) store operation at the secondary storage, and the (iii) index operation.
(The convert operation and store operation in claim 1 of ‘129 recites the remaining portions of the convert and store elements in instant claim 8)
(i) converting the at least one temporary backup file into the one or more secondary copies, and (ii) storing the one or more secondary copies at the secondary storage.
10. The system of claim 1,
wherein the first data storage comprises one or more of a data storage volume
10. The computer-implemented method of claim 1,
wherein the first data storage comprises
and a folder configured at the first computing device,
a folder configured at the second computing device,
and wherein a second data agent, which is
hosted by the first computing device, is associated with a file system that comprises the one or more of the data storage volume and
the folder.
and wherein a second data agent,
which is
hosted by the second computing device, is associated with a file system that
comprises
the folder.
Claims 11, 13, 14 16, 19 and 20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1 and 11 of U.S. Patent No. 12056018 B2 in view of Bezbaruah US 20220398163 A1
Although the claims at issue are not identical, they are not patentably distinct from each other because the bolded elements of claims 1 and 11 of ‘018 teaches the corresponding bolded elements in instant claim 11, 13, 16 19 and 20. See chart below.
It appears ‘claims 1 and 11 of ‘018 fails to explicitly teach “and enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO”
“and wherein the RPO for the first database is enforced based on the second computing device storing the first temporary backup files at the first data storage”
However, Bezbaruah teaches “and enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO and wherein the RPO for the first database is enforced based on the second computing device storing the first temporary backup files at the first data storage” in para. 11
The embodiments described herein are directed to a high frequency snapshot technique configured to reduce duration of data replication and improve recovery point objectives (RPO) in a disaster recovery (DR) environment. A data object (e.g., a virtual disk) at a primary site is designated for failover to a secondary site in the event of failure of the primary site. . .
A temporary staging file is provided at the secondary site to continually apply the replicated LWSs (“high-frequency snapshots”) as incremental changes to synthesize snapshots of those changes at the secondary site prior to completion of the base snapshot replication. In such a manner, the base snapshot and the synthesized snapshots capturing changes during the transfer of the base snapshot become available at the secondary site at substantially a same time once replication of the base snapshot completes because the incremental changes and the base snapshot are transferred concurrently. Notably, the staging file is populated with the LWSs in parallel with the replication of the base snapshot at the placeholder file. At a subsequent predetermined time interval (e.g., hourly interval), the accumulated LWSs may be combined (synthesized) to capture a “checkpoint” snapshot by applying (processing) the accumulated LWSs at the staging file to, e.g., “prune” or eliminate any overwrites or stale data associated with the accumulated LWSs within the file. Once the base snapshot is fully replicated (completes), the pruned LWSs (deltas) are applied to the base snapshot to synchronize the replicated failover data so that the base snapshot is up to date with a latest LWS.
(Examiner finds temporary staging file and LWS teaches temp backup files stored at the first data storage).
Bezbaruah and claim 1 and 11 of ‘018 are analogous art because they are from same field of endeavor as the claimed invention.
It would have been obvious to one skilled in the art before the effective filing date of the invention to modify the method in claim 1 and 11 of ‘018 to include “and enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO and wherein the RPO for the first database is enforced based on the second computing device storing the first temporary backup files at the first data storage as taught by Bezbaruah.
The motivation would have been to “reduc[e] convergence time and improve RPO in a disaster recovery (DR) environment.” Bezbaruah para. 11.
US 12056018 B2
Instant
1. A computer-implemented method performed by one or more hardware processors, the method comprising:
11. A computer-implemented method comprising enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO for the first database comprises: by a first computing device comprising one or more first hardware processors:
activating a first data agent at a first computing device,
wherein the first computing device hosts a database management system that comprises a first database, wherein the first data agent is associated with the database management system
hosting a database management system that comprises the first database,
by the first data agent,
converting a first set of transaction logs generated by the database management system into a first set of temporary backup files,
converting first transaction logs generated by the database management system into first temporary backup files
,
wherein the first set of temporary backup files are in a backup format that comprises encryption;
(Examiner finds encryption suggests a distinct format)
that are configured in a backup format that that is distinct from a data format that is native to the database management system
based on a time interval of a recovery point objective (RPO) associated with the first database,
transmitting the first set of temporary backup files over a persistent data pipeline connection to a second computing device;
and based on a time interval of the RPO,
transmitting the first temporary backup files to a second computing device that comprises one or more second hardware processors and is distinct from the first computing device;
by the second computing device, storing the first set of temporary backup files persistently at a data repository of the second computing device;
and by the second computing device:
storing the first temporary backup files at a first data storage, which is distinct from the first computing device, by a third computing device comprising one or more third hardware processors:
based on a second time interval that is greater than the time interval of the RPO, determining by the second computing device whether the data repository comprises any temporary backup files;
13. The computer-implemented method of claim 11, further comprising, by the second computing device:
based on a second time interval that is greater than the time interval of the RPO, making a determination that the first data storage comprises at least one temporary backup file
received from the first computing device,
based on the second computing device determining that the data repository comprises at least one temporary backup file, performing a data storage job that
converts the at least one temporary backup file into one or more secondary copies and storing the one or more secondary copies at a secondary storage that is distinct from the data repository,
and based on the determination:(i) converting the at least one temporary backup file into one or more secondary copies, and(ii) storing the one or more secondary copies at a secondary storage that is distinct from the first data storage.
wherein the data storage job comprises indexing the one or more secondary copies in an index maintained at the second computing device,
and wherein the data storage job further comprises
reporting information about the data storage job to a storage manager that executes
on a third computing
device,
14. The computer-implemented method of claim 13, further comprising, by the third computing device:
receiving, from the second computing device, information about the one or more secondary copies, and storing the information at a management database maintained by the third computing device,
which is distinct from the first computing device and from the second computing device.
wherein the management database is distinct from the first database.
11. The method of claim 1, further comprising: by the storage manager, receiving a request to restore data to the first database;
receiving, by the third computing device, a request to restore first data to the first database,
by the second computing device, determining whether the data repository comprises a second set of temporary backup files that comprise the data to be restored to the first database; initiating, by the storage manager, a restore job at the second computing device, wherein the restore job is based on the second set of temporary backup files;
causing the second computing device to identify the first temporary backup files, at the first data storage wherein the first temporary backup files comprise the first data requested to be restored,
by the second computing device, transmitting the second set of temporary backup files over the persistent data pipeline connection to the first data agent at the first computing device;
and causing the second computing device to transmit the first temporary backup files to the first computing device;
by the first data agent, converting the second set of temporary backup files into a second set of transaction logs, wherein the second set of transaction logs are in a format that is native to the database management system.
by the first computing device:
converting the first temporary backup files into a corresponding set of transaction logs, wherein the corresponding set of transaction logs are in the data format that is native to the database management system;
and wherein the RPO for the first database is enforced based on the second computing device storing the first temporary backup files at the first data storage
Taught by claim 1 above:
based on a second time interval that is greater than the time interval of the RPO, determining by the second computing device whether the data repository comprises any temporary backup files; based on the second computing device determining that the data repository comprises at least one temporary backup file, performing a data storage job that converts the at least one temporary backup file into one or more secondary copies and storing the one or more secondary copies at a secondary storage that is distinct from the data repository,
13. The computer-implemented method of claim 11, further comprising, by the second computing device :based on a second time interval that is greater than the time interval of the RPO, making a determination that the first data storage comprises at least one temporary backup file received from the first computing device, and based on the determination:(i) converting the at least one temporary backup file into one or more secondary copies, and(ii) storing the one or more secondary copies at a secondary storage that is distinct from the first data storage.
Taught by claim 1 above:
by the first data agent,
converting a first set of transaction logs generated by the database management system into a first set of temporary backup files,
transmitting the first set of temporary backup files over a persistent data pipeline connection to a second computing device;
16. The computer-implemented method of claim 11, further comprising: by a first data agent hosted by the first computing device: converting the first transaction logs generated by the database management system into the first temporary backup files, and
transmitting the first temporary backup files to the second computing device.
9. The method of claim 8, wherein the data repository comprises one or more of a data storage volume and a folder configured at the second computing device, and wherein the second data agent is associated with a file system that comprises the one or more of the data storage volume and the folder.
19. The computer-implemented method of claim [11], wherein the first data storage comprises a data storage volume at the second computing device, and wherein a second data agent, which is hosted by the second computing device, is associated with a file system that comprises the data storage volume.
9. The method of claim 8, wherein the data repository comprises one or more of a data storage volume and a folder configured at the second computing device, and wherein the second data agent is associated with a file system that comprises the one or more of the data storage volume and the folder.
20. The computer-implemented method of claim [11], wherein the first data storage comprises a folder configured at the second computing device, and wherein a second data agent, which is hosted by the second computing device, is associated with a file system that comprises the folder.
Allowable Subject Matter
Claims 2, 5, 9, 12, 15, 17 and 18 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
If a terminal disclaimer is filed, then claims 1-20 would be allowed.
Reasons for Indicating Allowable Subject Matter
The following prior art teaches the corresponding elements of claim 1. See chart below.
Claim
Prior Art
1. A computer-implemented method comprising enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO for the first database comprises:
by a first computing device comprising one or more first hardware processors:
US 20180137139 A1, abstract
hosting a database management system that comprises the first database,
US 20180137139 A1, abstract, para. 362
[0362] At block 808, container manager 530 activates an appropriate DBMS-specific data agent 142 within the storage management software 527 in the container. In other words, though the storage management software 527 in the container comprises numerous kinds of data agents 142 and media agents 144, only a suitable data agent 142 is activated for participating in the storage/test operations contemplated for the DBMS software in the container. The others remain inactive in “decoupled mode.” Illustratively, an Oracle data agent 142 is activated to support an Oracle version 1.3.1 DBMS software in the container. Likewise, a suitable media agent 144 is activated for accessing secondary storage device 108. Once activated, data agent 142 in the container establishes communications with storage manager 340 (e.g., based on information supplied by container manager 530) and registers as a client with storage manager 340. Registering as a client of system 300 enables the storage/test operations to proceed. Storage manager 340 accordingly stores the client information in management database 146.
converting first transaction logs generated by the database management system into first temporary backup files
US 5842222 in col. 2:53-col. 3:8
3) Periodically a conversion process is applied to all the data bases to facilitate re-establishing a clean and synchronized set of databases. Shown in FIG. 2 is the database conversion process which utilizes the backup database 10 to minimize down time of the production information system as the conversion process takes place. A temporary database is established using spare disk space and the backup database is converted to the temporary database 20. Then the backup data base files are deleted 21 and the converted files in the temporary database are copied to the backup database 22. Then the primary transaction log is applied to both the temporary database and the backup database 23 to bring these databases up to date with the most recent changes to the primary database. Next the secondary production information system is shut down 24 while maintaining the secondary database 25. The backup database is assigned to the secondary system and the secondary transaction log file is renamed as *.OLD 26. The secondary system is restarted 27. The secondary database files are deleted 28, and the converted files in the temporary database are copied to the secondary database 29. Then the secondary and temporary databases are further updated by applying the transaction log 30
that are configured in a backup format that that is distinct from a data format that is native to the database management system, and
US 20220083685 A1
[0044] A method according to an embodiment of the present invention uses cloud API integration and includes the following operations (not necessarily in the following order): (i) the Backup/Restore Server looks up data from its catalog; (ii) calculates required storage to state data; (iii) spins up a temporary cloud storage container; (iv) copies required legal data; (v) the legal data is collected and encrypted at rest on the temporary stating cloud storage to reduce risk and impact on IT (information technology); (vi) upon legal request for data, a link is provided to the lawyers to download the data; (vii) once the data is downloaded by intended user the data is retained for duration of legal hold, protected, and then deleted; and (viii) the temporary cloud storage is deprovisioned using cloud native APIs once the data is accessed.
(encrypted format is different than native format)
based on a time interval of the RPO,
US 20230333777 A1
[0087] In at least one existing data storage system, the remote replication can be performed by a remote replication facility executing on the source system where the remote replication facility can use a technique referred to as a snapshot difference or snap diff technique. The snap diff technique provides for taking two successive snapshots of the logical device or other storage object on the source system that is replicated on the target system, and then determining the data difference with respect to the two successive snapshots. The data difference denotes the data blocks that have been written or modified in the time interval from a first point in time to a second later point in time, where a first snapshot is taken at the first point in time and a second successive snapshot is taken at the second point in time. The time interval may correspond, for example, to a recovery point objective (RPO) defined as the maximum amount of allowable data loss, as measured by time, that can be lost after a recovery from a disaster, failure, or comparable event before data loss will exceed what is acceptable to an organization. The snap diff technique can provide for taking a snapshot at each RPO interval. For example, for an RPO of 5 hours, a snapshot of the logical device can be taken on the source system every 5 hours and compared to the immediately prior snapshot to determine the data differences including data blocks that have been modified since the immediately prior snapshot. The data differences including the modified or newly written data blocks of the logical device are then transferred from the source system to the target system and applied to the remote copy of the logical device on the target or remote system.
transmitting the first temporary backup files to a second computing device that comprises one or more second hardware processors and is distinct from the first computing device; and
US 20190087285
[0331] For example, the secondary storage computing devices 106 may perform secondary copy operations in response to receiving primary data from the client computing devices 102, as described above. In particular, the media agent 144 may perform secondary copy operations to convert primary data into secondary copies and then store the secondary copies in one or more secondary storage devices 108. The primary data processed during a single secondary copy operation (e.g., a single backup job) may each be associated with the same backup job identifier (e.g., the same archive file identifier) because the resulting secondary copies may be grouped into a single backup file (e.g., a single archive file) corresponding to the backup job identifier. In the process of performing secondary copy operations, the media agent 144 may generate a data structure associated with the particular media agent 144 that includes information about the stored data associated with the particular media agent 144 (e.g., index 153). For instance, for each secondary copy, the index 153 may include metadata such as an identification of the respective secondary copy (e.g., file/subdirectory, database object, mailbox object, etc.), a logical path to the respective secondary copy on the corresponding secondary storage device 108, location information (e.g., offsets) indicating where the respective secondary copy is stored in the secondary storage device 108, when the respective secondary copy was created or modified, etc. As described above, the media agent 144 may store the indices 153 in the media agent database 152. However, alternatively or in addition, the media agent 144 may transmit the indices 153 to the indexing storage system 320 for storage in one or more backup and content indexing (CI) databases 324 stored locally by the indexing storage system 320. The indexing storage system 320 may include an index manager 322 that determines in which backup and CI database 324 the received indices 153 should be stored. Because the secondary copies may be grouped into an archive file when stored in the one or more secondary storage devices 108, the received indices 153 may be stored in entries associated with the corresponding archive file identifier.
by the second computing device:
storing the first . . . backup files at a first data storage, which is distinct from the first computing device
US 20190087285
0331] For example, the secondary storage computing devices 106 may perform secondary copy operations in response to receiving primary data from the client computing devices 102, as described above. In particular, the media agent 144 may perform secondary copy operations to convert primary data into secondary copies and then store the secondary copies in one or more secondary storage devices 108. The primary data processed during a single secondary copy operation (e.g., a single backup job) may each be associated with the same backup job identifier (e.g., the same archive file identifier) because the resulting secondary copies may be grouped into a single backup file (e.g., a single archive file) corresponding to the backup job identifier. In the process of performing secondary copy operations, the media agent 144 may generate a data structure associated with the particular media agent 144 that includes information about the stored data associated with the particular media agent 144 (e.g., index 153). For instance, for each secondary copy, the index 153 may include metadata such as an identification of the respective secondary copy (e.g., file/subdirectory, database object, mailbox object, etc.), a logical path to the respective secondary copy on the corresponding secondary storage device 108, location information (e.g., offsets) indicating where the respective secondary copy is stored in the secondary storage device 108, when the respective secondary copy was created or modified, etc. As described above, the media agent 144 may store the indices 153 in the media agent database 152. However, alternatively or in addition, the media agent 144 may transmit the indices 153 to the indexing storage system 320 for storage in one or more backup and content indexing (CI) databases 324 stored locally by the indexing storage system 320. The indexing storage system 320 may include an index manager 322 that determines in which backup and CI database 324 the received indices 153 should be stored. Because the secondary copies may be grouped into an archive file when stored in the one or more secondary storage devices 108, the received indices 153 may be stored in entries associated with the corresponding archive file identifier.
based on a second time interval that is greater than the time interval of the RPO,
making a determination that the first data storage comprises at least
one temporary backup file received from the first computing device, and based on the determination:
Not taught by prior art of record
(i) converting the at least one temporary backup file into one or more secondary copies, and
Not taught by prior art of record
storing the one or more secondary copies at a secondary storage that is distinct from the first data storage.
Not taught by prior art of record
The following prior art teaches the corresponding elements of claim 11.
With respect to claim 11, US 20230333777 A1 teaches “11. A computer-implemented method comprising enforcing a recovery point objective (RPO) for a first database, wherein enforcing the RPO for the first database comprises: by a first computing device comprising one or more first hardware processors” in para. 87 (time interval corresponds to RPO; this is an enforcement mechanism);
“hosting a database management system that comprises the first database” in paras 1-2, para. 20 (hosts systems 14a-14n comprise data storage system 12 (database));
US 5842222 teaches “converting first transaction logs generated by the database management system into first temporary backup files” in col. 2:53-col. 3:8 (“A temporary database is established using spare disk space and the backup database is converted to the temporary database 20. Then the backup data base files are deleted 21 and the converted files in the temporary database are copied to the backup database 22. Then the primary transaction log is applied to both the temporary database and the backup database 23 to bring these databases up to date with the most recent changes to the primary database”);
“that are configured in a backup format that that is distinct from a data format that is native to the database management system” in col. 1:55-57; col. 4:54-56; and Figs. 4- 5 and col. 3:25-43 (archive or backup format is distinct in that is an archive format (e.g. tape or compressed) rather than native database format).
US 20230333777 A1 teaches “and based on a time interval of the RPO” in para. 15 (“the time interval may correspond, for example, to a recovery point objective (RPO) defined as the maximum amount of allowable data loss, as measured by time, that can be lost after a recovery from a disaster, failure, or comparable event before data loss will exceed what is acceptable to an organization. . .”)l
US 20190087285 teaches “transmitting the first temporary backup files to a second computing device that comprises one or more second hardware processors and is distinct from the first computing device” in para. 331 (“For example, the secondary storage computing devices 106 may perform secondary copy operations in response to receiving primary data from the client computing devices 102, as described above. In particular, the media agent 144 may perform secondary copy operations to convert primary data into secondary copies and then store the secondary copies in one or more secondary storage devices 108”);
US 20190087285 teaches “and by the second computing device:
storing the first temporary backup files at a first data storage, which is distinct from the first computing device” in para. 331 (“ For example, the secondary storage computing devices 106 may perform secondary copy operations in response to receiving primary data from the client computing devices 102”).
Prior art of record fails to teach or suggest:
by a third computing device comprising one or more third hardware processors:
receiving, by the third computing device, a request to restore first data to the first database,
causing the second computing device to identify the first temporary backup files, at the first data storage, wherein the first temporary backup files comprise the first data requested to be restored, and
causing the second computing device to transmit the first temporary backup files to the first computing device;
by the first computing device: converting the first temporary backup files into a corresponding set of transaction logs, wherein the corresponding set of transaction logs are in the data format that is native to the database management system; and
wherein the RPO for the first database is enforced based on the second computing device storing the first temporary backup files at the first data storage.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ALBERT M PHILLIPS, III whose telephone number is (571)270-3256. The examiner can normally be reached 10a-6:30pm EST M-F.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ann J Lo can be reached at (571) 272-9767. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/ALBERT M PHILLIPS, III/Primary Examiner, Art Unit 2159
Prosecution Insights