WO2006108260A1 - Method for validating system changes by use of a replicated system as a system testbed - Google Patents
Method for validating system changes by use of a replicated system as a system testbed Download PDFInfo
- Publication number
- WO2006108260A1 WO2006108260A1 PCT/CA2005/001114 CA2005001114W WO2006108260A1 WO 2006108260 A1 WO2006108260 A1 WO 2006108260A1 CA 2005001114 W CA2005001114 W CA 2005001114W WO 2006108260 A1 WO2006108260 A1 WO 2006108260A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- database
- primary
- tables
- filestore
- server
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2038—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant with a single idle spare processing component
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2097—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements maintaining the standby controller/processing unit updated
Definitions
- version control is another aspect of most document management systems. Version control is an issue of particular importance in situations where different people are able to share documents and have shared access to the documents, including a shared right to independently modify the documents.
- Documentum 1M is a document management system that comprises of three different layers(or technologies) sitting on top of an operating system (server based) such as Unix or Windows 2000 server, a system database, and a filestore.
- server based such as Unix or Windows 2000 server
- system database such as a system database
- filestore such as a filestore
- the layers comprise of a Documentum application server layer that sits on top of the database and serves Documentum client interfaces.
- the reference information i.e. the information pointing to the physical document data
- supplementary document information i.e. the attributes of the types of Documents stored
- the actual physical data is stored in a filestore on either the server, a Storage area network (SAN) or Filer pointed to by the server.
- SAN Storage area network
- One example of a company in which a document management software system would be useful is an engineering company that has many versions of the same part. When a client orders that part the company has to find the correct part version.
- the document management system typically includes a system database that is associated with a filestore.
- the filestore stores the actual document data, while the system database stores reference information that points to the document within the filestore. Also, the system database typically stores supplementary document information regarding each document.
- a replicated server (The replica containing the proprietary document management system software and the system database containing reference data to point to the document data wherein said document data is stored in a separate system filestore associated with a system database) was built, and upgraded, and hence plurality of data was achieved but only at a point in time that allowed a switch or toggle to allow the new replicated server to become the production system.
- the data was copied from the primary filestore using a full backup /restore on the Thursday night to the secondary backup filestore.
- the Primary production server was shutdown and incremental backup of the primary filestore and database export from the primary database taken and these applied to the secondary server. This step ensured the plurality of the data for the point in time when after testing a switch could be made.
- the approach forms one of the foundation stones of this Invention.
- the second foundation stone of this invention is another invention File number CTC002 submitted recently for Patent in Canada, in which the concept of usage of Oracle triggers to record the metadata is developed, using a set of access preservation tables (Oracle tables, SqI Server tables).
- the final foundation stone is the fact that most servers (such as a Unix or Windows 2000 server) on which the Document Management/Oracle software sits on are Networked.
- this invention could additionally be used for the purpose of the secondary server acting as a "Standby" in case of failure of the first system's Server.
- the primary system is operably connected to a network fabric.
- the secondary system is operably connected to a network fabric.
- the primary system has information loaded onto it, and is based on the first server.
- the secondary system has information loaded onto it, and is based on a second server.
- the first system and the second system is configured to allow a client computer operably connected to the network fabric to locate information owned by the first system and information owned by the second system.
- the second system replicates the first system.
- the system comprises a Document Management System residing on a server (Unix or Windows 2000 server) comprising of a filestore storing the actual document data and a system database storing reference information pointing to the documents within a filestore, supplementary information on the document, together with system specific information.
- the second system's system database is configured to mirror the information in that of the first system's system database less a portion of the data which allows the second system to be uniquely identified on the network fabric.
- the filestore containing documents is connected to the network fabric.
- the filestore is based on a Storage Area Network (SAN) or Filer connected to the network fabric.
- the primary system's server can be connected to the filestore.
- the secondary system's server can be connected to the same system filestore it is appreciated that a separate filestore for the secondary system can also be used and this is comprehended by the Invention in this case the second filestore in this case would need to have incremental backups from the first filestore to be continuously applied to it throughout.
- the primary and secondary system share the same system filestore.
- the primary and secondary system databases are linked through the network fabric.
- the method comprises of using Oracle Database software linking primary and secondary system databases on the network fabric by means of an Oracle database link command.
- this link between primary and secondary system databases is by a means of a SQL server linked server command.
- both the primary and secondary systems databases have the required access permissions to access, modify, insert or delete data in each other and are accessible to each other across the network fabric.
- the method comprises document data being added to the filestore and reference data modified within system tables in the primary system database, and wherein the recording step comprises the step of recording reference data from all primary system tables, save those holding system specific data.
- the primary system in response to an insert, update, delete command, inserts, updates, deletes reference data to each of the system tables affected for each particular transaction.
- the recording step comprises recording the reference data using at least one database trigger.
- the recording step comprises recording the reference data using three database triggers associated with each system table, excepting those tables, which allow the first system to be uniquely identified on the network fabric.
- the method comprises adding a first database trigger associated with recording the changes after an insert command on each table, adding a second database trigger associated with recording the changes after an update command on each table and adding a third database trigger associated with recording the changes after a delete command on each database table, excepting those tables that define the primary system on the network fabric.
- the method comprises performing identical changes, to that which can occur after an insert, update, delete command on each primary system database table and are recorded within the respective database trigger pertaining to that particular transaction to the identical replicated secondary system database table, by means of the salient SQL command contained within the three triggers on each of the primary database tables, the transfer, and application of the identical SQL command made possible only by the primary and secondary database systems being linked through a database link on the network fabric.
- the three triggers on each table in the primary database also record the changes on update, insert, delete to access-preservation tables and a single transaction table for all changes on all tables.
- the single transaction table contains the group: the type of transaction (i.e.
- the recording step comprises using at least one access-preservation table.
- the recording step comprises using a set of three access preservation tables for each primary system table to be mirrored in the secondary database tables.
- the method additionally comprises using a database stored procedure to apply the changes and transactions recorded in the access-preservation tables and transaction table, to the secondary system should the database link be severed for any reason including that of maintenance to the secondary system on a time based input parameter, once the database link is restored and user input is halted temporarily.
- a set of database procedures can be used in contingency the database link is severed for any reason to apply the changes and transactions recorded, in order, from the time the link was severed to the secondary system in order to synchronise the two systems once the database link is restored again, user input to be halted at this point until the procedures have finished running , then the system can be returned to the said automated transfer using the SQL command within the triggers on each table, with the user input recommenced.
- the set comprises a first access-preservation table to receive reference data recorded from the insert transaction on each system table, a second access-preservation table to receive reference data recorded from the update transaction on each system table, and a third access preservation table to receive reference data recorded from the delete transaction on each system table.
- the method comprises input restriction until the primary and secondary system databases are re-synchronised.
- the method comprises the contingency of applying the changes through at least a single database procedure using the combination transaction table and access-preservation tables, in order to resynchronise the primary and secondary systems once the database link is restored.
- the method comprises using Documentum as the Document Management System for both the primary and secondary system.
- the method comprises of using the primary system for the user community to store their documents.
- the method comprises of using the secondary system as a testbed for changes which eventually need to be applied to the primary system.
- the method comprises document data being added to the filestore and reference data modified within Documentum system tables in the primary Oracle system database, and wherein the recording step comprises the step of recording reference data from all primary system tables, save those holding server specific data.
- the method requires the secondary system to be used as a testbed, for testing any changes before applying changes to the Primary system.
- the secondary system can be also used as a standby backup system in case of failure of the primary system.
- the primary and secondary systems can be interchanged by adding the database triggers and procedures to both primary and secondary system databases and disabling the triggers and procedures in the designated secondary system.
- the system comprises a Documentum document management system, and wherein the method is carried out additionally it is appreciated that the secondary server be used as a "Standby" this is comprehended by this invention but is not the primary purpose.
- the recording, inserting, updating, deleting and providing steps and standard database constructs are executed by the execution of Oracle database software code.
- the recording, inserting, updating, deleting and providing steps and standard database constructs are executed by the execution of SQL Server database software code.
- Figure 1 shows the preferred form of the invention which allows the invaluable validation, testing of changes due to applying software/hardware patches, maintenance work, and perhaps upgrades on a real-time replica of the system; in this case of a Document management system known as Documentum, without risking the live system.
- a Document management system known as Documentum
- a typical Documentum system database has a number of system tables that store reference information and supplementary document information.
- the Replicated server is set up using the approach presented at the Documentum Conference "Upgrading to Documentum 5i using the toggle "clone” method by myself.
- the primary system is operably connected to a network fabric.
- the secondary system is operably connected to a network fabric.
- the primary system has information loaded onto it, and is based on the first server.
- the secondary system has information loaded onto it, and is based on a second server.
- the first system and the second system is configured to allow a client computer operably connected to the network fabric to locate information owned by the first system and information owned by the second system.
- the second system replicates the first system.
- the system comprises a Document Management System residing on a server (Unix or Windows 2000 server) comprising of a filestore storing the actual document data and a system database storing reference information pointing to the documents within a filestore, supplementary information on the document, together with system specific information.
- the second system's system database is configured to mirror the information in that of the first system's system database less a portion of the data which allows the second system to be uniquely identified on the network fabric.
- the filestore containing documents is connected to the network fabric.
- the filestore is based on a Storage Area Network (SAN) or Filer connected to the network fabric.
- the primary system's server can be connected to the filestore.
- the secondary system's server can be connected to the same system filestore it is appreciated that a separate filestore for the secondary system can also be used and this is comprehended by the Invention in this case the second filestore in this case would need to have incremental backups from the first filestore to be continuously applied to it throughout.
- the primary and secondary system share the same system filestore.
- the primary and secondary system databases are linked through the network fabric.
- the method comprises of using Oracle Database software linking primary and secondary system databases on the network fabric by means of an Oracle database link command.
- this link between primary and secondary system databases is by a means of a SQL server linked server command.
- both the primary and secondary systems databases have the required access permissions to access, modify, insert or delete data in each other and are accessible to each other across the network fabric.
- the method comprises document data being added to the filestore and reference data modified within system tables in the primary system database, and wherein the recording step comprises the step of recording reference data from all primary system tables, save those holding system specific data.
- the primary system in response to a insert, update, delete command, inserts, updates, deletes reference data to each of the system tables affected for each particular transaction.
- the recording step comprises recording the reference data using at least one database trigger.
- the recording step comprises recording the reference data using three database triggers associated with each system table, excepting those tables, which allow the first system to be uniquely identified on the network fabric.
- the method comprises adding a first database trigger associated with recording the changes after an insert command on each table, adding a second database trigger associated with recording the changes after an update command on each table and adding a third database trigger associated with recording the changes after a delete command on each database table, excepting those tables that define the primary system on the network fabric.
- the method comprises performing identical changes, to that which can occur after an insert, update, delete command on each primary system database table and are recorded within the respective database trigger pertaining to that particular transaction to the identical replicated secondary system database table, by means of the salient SQL command contained within the three triggers on each of the primary database tables, the transfer, and application of the identical SQL command made possible only by the primary and secondary database systems being linked through a database link on the network fabric.
- the three triggers on each table in the primary database also record the changes on update, insert, delete to access-preservation tables and a single transaction table for all changes on all tables.
- the single transaction table contains the group: the type of transaction (i.e.
- the recording step comprises using at least one access-preservation table.
- the recording step comprises using a set of three access preservation tables for each primary system table to be mirrored in the secondary's database tables.
- the method additionally comprises using a database stored procedure to apply the changes and transactions recorded in the access-preservation tables and transaction table, to the secondary system should the database link be severed for any reason including that of maintenance to the secondary system on a time based input parameter, once the database link is restored and user input is halted temporarily.
- a set of database procedures can be used in contingency the database link is severed for any reason to apply the changes and transactions recorded, in order, from the time the link was severed to the secondary system in order to synchronise the two systems once the database link is restored again, user input to be halted at this point until the procedures have finished running , then the system can be returned to the said automated transfer using the SQL command within the triggers on each table, with the user input recommenced.
- the set comprises a first access-preservation table to receive reference data recorded from the insert transaction on each system table, a second access-preservation table to receive reference data recorded from the update transaction on each system table, and a third access preservation table to receive reference data recorded from the delete transaction on each system table.
- the method comprises input restriction until the primary and secondary system databases are re- synchronised.
- the method comprises the contingency of applying the changes through at least a single database procedure using the combination transaction table and access-preservation tables, in order to re-synchronise the primary and secondary systems once the database link is restored.
- the method comprises using Documentum as the Document Management System for both the primary and secondary system.
- the method comprises of using the primary system for the user community to store their documents.
- the method comprises of using the secondary system as a testbed for changes which eventually need to be applied to the primary system.
- the method comprises document data being added to the filestore and reference data modified within Documentum system tables in the primary Oracle system database, and wherein the recording step comprises the step of recording reference data from all primary system tables, save those holding server specific data.
- the method requires the secondary system to be used as a testbed, for testing any changes before applying changes to the Primary system.
- the secondary system can be also used as a standby backup system in case of failure of the primary system.
- the primary and secondary systems can be interchanged by adding the database triggers and procedures to both primary and secondary system databases and disabling the triggers and procedures in the designated secondary system.
- the system comprises a Documentum document management system, and wherein the method is carried out additionally it is appreciated that the secondary server be used as a "Standby" this is comprehended by this invention but is not the primary purpose.
- the recording, inserting, updating, deleting and providing steps and standard database constructs are executed by the execution of Oracle database software code.
- the recording, inserting, updating, deleting and providing steps and standard database constructs are executed by the execution of SQL Server database software code.
- the triggers are added to the relevant Documentum tables and they automatically fire to capture the salient information needed to apply a SQL command to keep two systems synchronised, where the secondary system is a replica of the first.
- This transfer is made possible by the setting up of a Database link between the primary and secondary database systems across the network fabric.
- an Oracle Database link Permissions to the user schema or database on the secondary system need to be granted to the primary system's schema or database, and visa versa in case of the secondary system taking over the role of the primary.
- the database link could be set up using other databases of course using the relevant construct, as I have some experience with SqI Server I can at least provide the database mechanism to link two SqI server databases together namely the "linked server" construct. Though my experience is mainly within the Oracle database orena, most large database of any stature have to have similar constructs through common standards such as the SQL command language itself. So this method is very much multi-database.
- the Invention can be embodied in a multi-operating system embodiment.
- the invention can be embodied in a multi-document management system embodiment.
- the invention can be implemented in a multi-database embodiment.
- the first command of the above trigger shows the SQL command and the "after delete row" trigger on the primary database automatically deletes the row in the secondary table.
- the insert statement is necessary in case the link is severed which can happen from time to time in case of maintenance, or in case of failure.
- As the above Oracle code shows this can be used in order to preserve the data in access preservation tables and the transaction table.
- the access- preservation tables and transaction table are used instead at a later point by database procedures that can run in the transactions in sequence to the Secondary Database, or visa versa.
- the triggers and procedures being "Enabled" in the designated Primary.
- a "after row insert” and “after row update” is preferably used, meaning that the data values of the row that have been, inserted or updated are actually captured notice the new values . inserted are always used. On a “before insert "old values do not exist. This ensures that all salient and/or relevant information is captured.
- An oracle database procedure or stored procedure is a piece of oracle execution code and carries out logical instructions.
- An oracle trigger is a piece of application code that can be applied to an oracle "table" (a storage unit like a filling cabinet) which when particular transactions are carried out on the table it fires automatically to execute the code within it.
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2005330533A AU2005330533A1 (en) | 2005-04-14 | 2005-06-28 | Method for validating system changes by use of a replicated system as a system testbed |
EP05770530A EP1869553A1 (en) | 2005-04-14 | 2005-06-28 | Method for validating system changes by use of a replicated system as a system testbed |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA2,504,070 | 2005-04-14 | ||
CA002504070A CA2504070C (en) | 2005-04-14 | 2005-04-14 | Method for preserving access to deleted and overwritten documents |
CA2,506,303 | 2005-05-04 | ||
CA002506303A CA2506303A1 (en) | 2005-04-14 | 2005-05-04 | Method for validating system changes safely by use of a replicated system as a system testbed |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006108260A1 true WO2006108260A1 (en) | 2006-10-19 |
Family
ID=37086551
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA2005/001114 WO2006108260A1 (en) | 2005-04-14 | 2005-06-28 | Method for validating system changes by use of a replicated system as a system testbed |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1869553A1 (en) |
AU (1) | AU2005330533A1 (en) |
GB (1) | GB2445367A (en) |
WO (1) | WO2006108260A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009058427A1 (en) * | 2007-10-31 | 2009-05-07 | Hewlett-Packard Development Company L.P. | Testing disaster recovery elements |
WO2009117202A1 (en) * | 2008-03-21 | 2009-09-24 | Qualcomm Incorporated | Pourover journaling |
US20130073516A1 (en) * | 2011-06-23 | 2013-03-21 | Alibaba Group Holding Limited | Extracting Incremental Data |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040098425A1 (en) * | 2002-11-15 | 2004-05-20 | Sybase, Inc. | Database System Providing Improved Methods For Data Replication |
WO2005111783A2 (en) * | 2004-04-29 | 2005-11-24 | Filenet Corporation | Enterprise content management network-attached system |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0678812A1 (en) * | 1994-04-20 | 1995-10-25 | Microsoft Corporation | Replication verification |
US6820099B1 (en) * | 2001-04-13 | 2004-11-16 | Lsi Logic Corporation | Instantaneous data updating using snapshot volumes |
US20030009752A1 (en) * | 2001-07-03 | 2003-01-09 | Arvind Gupta | Automated content and software distribution system |
US6874103B2 (en) * | 2001-11-13 | 2005-03-29 | Hewlett-Packard Development Company, L.P. | Adapter-based recovery server option |
-
2005
- 2005-06-28 WO PCT/CA2005/001114 patent/WO2006108260A1/en not_active Application Discontinuation
- 2005-06-28 AU AU2005330533A patent/AU2005330533A1/en not_active Abandoned
- 2005-06-28 EP EP05770530A patent/EP1869553A1/en not_active Withdrawn
- 2005-08-18 GB GB0516997A patent/GB2445367A/en not_active Withdrawn
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040098425A1 (en) * | 2002-11-15 | 2004-05-20 | Sybase, Inc. | Database System Providing Improved Methods For Data Replication |
WO2005111783A2 (en) * | 2004-04-29 | 2005-11-24 | Filenet Corporation | Enterprise content management network-attached system |
Non-Patent Citations (5)
Title |
---|
"EMC MirrorView Software", EMC PRODUCT DATA SHEET, XP008116062, Retrieved from the Internet <URL:http://www.emc.com/pdf/products/clariion/mirrorview.pdf> * |
"Enabling Business Continuity for Enterprise Content Infrastructure", DOCUMENTUM TECHNICAL WHITE PAPER, July 2003 (2003-07-01), pages 9, XP008116063, Retrieved from the Internet <URL:http://www.documentum.co.uk/products/collateral/platform/wp_biz_continuity.pdf> * |
"Network Appliance SnapMirror Software", product data sheet, 2003 http://www.netapp.com/ftp/snapmirror.pdf * |
"Overview of Documentum 5 Server with NetApp Storage Solutions", NETWORK APPLIANCE INC. TECHNICAL REPORT BY GANGOOR SRIDHARA, May 2004 (2004-05-01), pages 17, XP008112213, Retrieved from the Internet <URL:http://www.netapp.com/library/tr/3316.pdf> * |
"Upgrading to Documentum 5i using the clean build toggle clone approach", 13 May 2004 (2004-05-13), Retrieved from the Internet <URL:http://www.momentumeurope.com/conf_track3.shtml> * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009058427A1 (en) * | 2007-10-31 | 2009-05-07 | Hewlett-Packard Development Company L.P. | Testing disaster recovery elements |
US8984326B2 (en) | 2007-10-31 | 2015-03-17 | Hewlett-Packard Development Company, L.P. | Testing disaster recovery elements |
WO2009117202A1 (en) * | 2008-03-21 | 2009-09-24 | Qualcomm Incorporated | Pourover journaling |
US8700574B2 (en) | 2008-03-21 | 2014-04-15 | Omnitracs, Llc | Pourover journaling |
US20130073516A1 (en) * | 2011-06-23 | 2013-03-21 | Alibaba Group Holding Limited | Extracting Incremental Data |
Also Published As
Publication number | Publication date |
---|---|
EP1869553A1 (en) | 2007-12-26 |
AU2005330533A1 (en) | 2006-10-19 |
GB0516997D0 (en) | 2005-09-28 |
GB2445367A (en) | 2008-07-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20060235905A1 (en) | Method and system for preserving real-time access to a system in case of a disaster | |
US20060253500A1 (en) | Method for validating system changes by use of a replicated system as a system testbed | |
CN108475271B (en) | Application container of container database | |
US10891067B2 (en) | Fast migration of metadata | |
US5778390A (en) | Method and systems for creating duplicating, and archiving database files | |
US20060235904A1 (en) | Method for preserving access to system in case of disaster | |
US10120767B2 (en) | System, method, and computer program product for creating a virtual database | |
CN103119590B (en) | The method and system of integrity is managed in distributed data base | |
US20170116334A1 (en) | Application containers in container databases | |
EP1675007B1 (en) | Fault management system in multistage copy configuration | |
US8046329B2 (en) | Incremental backup of database for non-archive logged servers | |
US20200272492A1 (en) | Deploying a cloud instance of a user virtual machine | |
US20080263079A1 (en) | Data recovery in an enterprise data storage system | |
WO2006108260A1 (en) | Method for validating system changes by use of a replicated system as a system testbed | |
US20230267103A1 (en) | Database Schema Branching Workflow, with Support for Data, Keyspaces and VSchemas | |
CA2506100C (en) | Method for preserving access to system in case of disaster | |
Dell | ||
GB2445584A (en) | Database backup and retrieval using transaction records and a replicated data store | |
EP1896991A1 (en) | Method for preserving access to deleted and overwritten documents | |
GB2425376A (en) | Method and system for producing a data backup system of a primary system in a document management system | |
Baransel | Oracle Data Guard 11gR2 Administration Beginner's Guide | |
CA2531714C (en) | A method and system for preserving access to a system in case of a disaster | |
CA2545532A1 (en) | Method and system for providing network attached system for disaster recovery and upgrade testing | |
Malcher et al. | RMAN Restore and Recovery | |
WO2024078677A1 (en) | Mapping identifiers to maintain name and location coherency in file system objects |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
DPE2 | Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2005770530 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 562709 Country of ref document: NZ Ref document number: 2005330533 Country of ref document: AU |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: RU |
|
ENP | Entry into the national phase |
Ref document number: 2005330533 Country of ref document: AU Date of ref document: 20050628 Kind code of ref document: A |
|
WWP | Wipo information: published in national office |
Ref document number: 2005330533 Country of ref document: AU |
|
WWP | Wipo information: published in national office |
Ref document number: 2005770530 Country of ref document: EP |