Abstract: A system and method for providing data protection services and lifecycle management in a Platform as a Service (PaaS) platform having cloud-based applications and data, by discovering an application installed on the PaaS platform using mechanisms native to the PaaS platform, associating the application and an associated data service used by the application to identify data created by the application, and performing a backup/restore operation on the application and the identified data in accordance with a defined schedule. The native mechanisms may comprise application programming interfaces (APIs) provided by the PaaS platform, or metadata associated with containers used by the PaaS platform. The schedule may be defined by RTO and RPO requirements of a user.

Abstract: Techniques for epoch pipelining are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for epoch pipelining comprising the steps of beginning a first epoch, determining for one or more pages of memory if the pages of memory are likely to be modified in a subsequent epoch, performing a first operation on the pages of memory that are likely to be modified in a subsequent epoch, beginning a second epoch, subsequent to the first epoch, performing a second operation on the pages of memory that are not likely to be modified in a subsequent epoch, and ending the first epoch, wherein the first operation and the second operation are dissimilar.

Abstract: A system, method, and computer-accessible medium are disclosed for efficient generation of application snapshots. Execution of an application is stopped, wherein a plurality of memory pages are accessible to the application. By altering page permissions of the plurality of memory pages, a state of the plurality of memory pages is preserved while the execution of the application is stopped. The execution of the application may be restarted after the state of the plurality of memory pages has been preserved. The state of the plurality of memory pages may be captured after the execution of the application has been restarted.

Abstract: Method and apparatus for transactional fault tolerance in a client-server system is described. In one example, output data generated by execution of a service on a primary server during a current epoch between a first checkpoint and a second checkpoint is buffered. A copy of an execution context of the primary server is established on a secondary server in response to the second checkpoint. The output data as buffered is released from the primary server in response to establishment of the copy of the execution context on the secondary server.

Abstract: Method and apparatus for transactional fault tolerance in a client-server system is described. In one example, output data generated by execution of a service on a primary server during a current epoch between a first checkpoint and a second checkpoint is buffered. A copy of an execution context of the primary server is established on a secondary server in response to the second checkpoint. The output data as buffered is released from the primary server in response to establishment of the copy of the execution context on the secondary server.