<--- Back to Details
First PageDocument Content
Information technology management / Fault-tolerant computer systems / Computer storage / Data synchronization / Replication / Backup / Continuous availability / Disaster recovery / Business continuity planning / Computing / System software / Backup software
Date: 2004-01-12 15:36:51
Information technology management
Fault-tolerant computer systems
Computer storage
Data synchronization
Replication
Backup
Continuous availability
Disaster recovery
Business continuity planning
Computing
System software
Backup software

Add to Reading List

Source URL: m.sybase.com

Download Document from Source Website

Share Document on Facebook

Similar Documents

Fair Synchronization∗ Gadi Taubenfeld† June 30, 2016 Abstract Most published concurrent data structures which avoid locking do not provide any fairness guarantees. That is, they allow processes to access a data struc

DocID: 1vnGU - View Document

A Fence Placement for Legacy Data-Race-Free Programs via Synchronization Read Detection ANDREW J. MCPHERSON, University of Edinburgh VIJAY NAGARAJAN, University of Edinburgh SUSMIT SARKAR, University of St. Andrews

DocID: 1tIbA - View Document

Data Synchronization in Privacy-Preserving RFID Authentication Schemes S´ebastien CANARD and Iwen COISEL Orange Labs R&D - Caen - France RFIDSec 08 - 10th July 2008

DocID: 1seae - View Document

Fault-tolerant computer systems / Computing / Computer architecture / Concurrent computing / Data synchronization / State machine replication / Byzantine fault tolerance / Replication / Clientserver model / Microkernel / Server

Attested Append-Only Memory: Making Adversaries Stick to their Word Byung-Gon Chun† Petros Maniatis⋆ Scott Shenker†‡ †

DocID: 1rqQM - View Document

Computing / Inter-process communication / Computer memory / Input/output / Data buffer / Synchronization / Circular buffer / Blocking / Multiple buffering / SIMPL

Lecture 23: More on Pointto-Point Communication William Gropp www.cs.illinois.edu/~wgropp Cooperative Operations for Communication

DocID: 1rqJb - View Document