Abstract:
A non-transitory computer readable storage medium storing therein a control program that causes a computer to execute a process, the process includes selecting an operation execution log of an operation which is finished normally among a plurality of operation execution logs stored in a first storage in response to an operation which is executed for a second storage, and storing the operation execution log which is selected in a third storage for backup.
Abstract:
The embodiments relate to performing a write operation in a filesystem. Replica files embedded with respective sets of data are stored are on persistent storage local to replica nodes of the filesystem. The storage includes atomically updating the replica files to the replica nodes. Each set of data has information for self-characterizing each replica file. A map stored at persistent storage local to a remote node is updated. The map maintains information for identifying each replica file stored at each replica node.
Abstract:
A system and method are provided for the recovery and restoration of software records of a database server to record iterations previous to the current state of the selected records. This action may be taken in order to overcome the consequences of database corruption. An event-time maybe designated which is applied to select some or all of the earlier but most recent versions of each selected record. The system and method presented include a local target database for the purpose of recording software records to an archive, and may include a remote source database, from which records may be transmitted to the local target database. A restore command may be detected by the database server as sent from the remote source server, as received in an electronic message, as received via an electronics communications network, or as directly input. The local target database may have access to multiple iterations or versions of a software record including the original record version as stored in an archive, and may, upon instruction or command, revert to a previous iteration of a software record stored in the archive if corruption of later iterations is suspected. Alternatively or additionally, the local target database may not be restored with earlier versions of records but the remote source database may be restored with the selected record versions. The software records may optionally be updated in a batch method, or may alternatively be updated in real time, as the software records are created.
Abstract:
A method and devices for providing secure data backup from a mobile communication device to an external computing device is described. In one embodiment, there is provided a method of backing up data from a mobile communication device, the method comprising: receiving from an enterprise server an information technology (IT) policy message which includes an encryption key; storing the encryption key in a protected memory of the mobile communication device; receiving a request to backup data stored on the mobile communication device; encrypting the data using the encryption key stored in the protected memory; and transferring the encrypted data from the mobile communication device to an electronic device for storage.
Abstract:
A first compute node of a plurality of compute nodes of a database cluster may receive a request for a database transaction from a client application. The client application may be located within the first compute node. A first connection may be established, without regard to whether another compute node has a lighter workload than the first compute node, between the client application and a first database of the database cluster. The first connection may be a local connection, wherein the first database is located within the first compute node. The first compute node may detect that a failure associated with the first database has occurred. The first compute node may execute a failover operation to continue servicing the request for the data. The executing of a failover operation may include establishing a second connection between the client application and a second database of the database cluster.
Abstract:
A method of identifying duplicate crash dumps in a computer system may include receiving a first crash dump caused by an application crash, extracting a first function signature of a function that caused the first crash dump, and searching a datastore of crash dumps for function signatures that substantially match the first function signature. The searching may include performing an approximate string-match between each of the function signatures the first function signature and performing an exact string match between each of the function signatures and the first function signature. The searching may also include combining weighted results of the approximate string-match with weighted results of the exact string match to generate match scores for each of the function signatures, and identifying the function signatures that substantially match the first function signature based on the match scores.
Abstract:
Recovering data to a point in time before pending definition changes are materialized in a relational database management system. One or more definition changes to a database schema are received. Original data base schema attributes are saved and maintained as point in time metadata in a catalog table until the one or more definition changes have been materialized. During recovery processing, it is determined for each object being recovered whether the object is being recovered to a point in time prior to which the one or more definition changes were materialized. In response to determining that an object is being recovered to a point in time prior to which the one or more definition changes were materialized, the saved point in time metadata is used for the object in the recovery process.
Abstract:
Resiliency in file replication scenarios via maintenance of multiple replication queues with differing susceptibility to various sources of data loss. A plurality of requests are received at a first file system location to write to one or more file system objects at the first file system location. Details about the plurality of requests are recorded in at least two replication queues which differ, at least in part, as to types of failures which will cause data loss. Responsive to detection of data loss in one of the replication queues, details about the plurality of requests are retrieved from another of the replication queues.
Abstract:
Read data blocks based on a read-amount multiplied by an increment-amount from data storage and write the data blocks to the read-ahead buffer. If the total number of data blocks written to the read-ahead buffer is greater than or equal to the request-amount, then returning to the host the total number of data blocks written to the read-ahead buffer. If the total the number of data blocks written to the read-ahead buffer is less than the request-amount, repeating incrementing the increment-amount and reading data blocks equal to the read-amount multiplied by the increment-amount from the data storage, and writing the read data blocks to the read-ahead buffer until the total number of data blocks written to the read-ahead buffer is greater than or equal to the request-amount.
Abstract:
In an executing database instance including a plurality of database nodes, creation of a backup of the executing database instance includes creation of a current savepoint in one of the plurality of database nodes by storing first modified pages of a cache of the database node in a datastore of the database node, transmitting a confirmation after storing the first modified pages, repeatedly identifying second modified pages of the cache and storing the identified second modified pages in the datastore, receiving an instruction to enter a critical phase and stopping the repeated identifying and storing in response to the instruction, blocking updates to the database node and transmitting a second confirmation, and receiving a second instruction and, in response to receiving the second instruction, identifying third modified pages of the cache and storing the third modified pages of the cache in the datastore. Pages associated with the current savepoint are identified and stored in the datastore, and the pages associated with the current savepoint are stored in a persistent media.