Abstract: Techniques and mechanisms described herein provide for verification of data across cloud-based and on-premises data storage systems. According to various embodiments, a backup client implemented on a first compute node can store a data file in a backup data repository. A data guardianship can store first data file state information describing the data file in a key-value store accessible via the internet. A data verification instance can analyze the backup data repository to verify that the data file is stored intact in the backup data repository.

Abstract: Techniques and mechanisms described herein provide for verifying data across cloud-based and on-premises data storage systems. According to various embodiments, data can be received by a gateway from a client machine and stored in a file data repository accessible via the internet. The stored data can have a common master namespace. Indications of updates to the master namespace can be received. Updated namespace data and metadata can be transmitted to the gateway.

Abstract: In general, certain embodiments of the present disclosure provide techniques or mechanisms for creating efficient and consistent replication of file overwrites. According to various embodiments, a file map with a sequence file number is created for a data file on a source. The file map includes one or more nodes that each include a sequence node number. When an entry in the file map is changed, the sequence file number is incremented, and the corresponding node is updated by, among other things, setting the sequence node number to equal the current sequence file number. All other nodes in the file map that point to the updated node are similarly updated. When replication occurs, only the updated nodes in the file map are replicated and any unreplicated non-updated nodes are maintained.

Abstract: In general, certain embodiments of the present disclosure provide techniques or mechanisms for creating efficient and consistent replication of file overwrites. According to various embodiments, a file map with a sequence file number is created for a data file on a source. The file map includes one or more nodes that each include a sequence node number. When an entry in the file map is changed, the sequence file number is incremented, and the corresponding node is updated by, among other things, setting the sequence node number to equal the current sequence file number. All other nodes in the file map that point to the updated node are similarly updated. When replication occurs, only the updated nodes in the file map are replicated and any unreplicated non-updated nodes are maintained.

Abstract: A workflow management system is provided. The workflow management system comprises a workflow manager that coordinates the activities of business systems to accomplish jobs, the workflow manager associating a state with each job and updating the state of each job as the job progresses, a tracking data store, and a reporting data store. The tracking data store receives the state of the jobs from the workflow manager. The reporting data store receives the state of the jobs from the tracking data store. The reporting data store maintains milestones which correspond to one or more states, and scenarios, which are defined as a group of milestones. The system also includes a processing component that analyzes the plurality of milestones and scenarios to provide a summary of job progress. The system also includes a user interface operable to select and to display a report of job progress.

Abstract: A telecommunications service provisioning method and system are disclosed having customer-want date (CWD) oriented scheduling. In one embodiment, the method comprises: (a) accepting order entry notifications; and (b) initiating an initiator process for each order entry notification. The initiator process initiates multiple processes including a truck roll process that arranges for a visit to the customer premises for installation of equipment. The truck roll process may implement a jeopardy timer that sends an alert message if prerequisites for the truck roll process have not been satisfied by some predetermined time in advance of the installation date. The initiator process may send a customer reminder two days before a prearranged installation date. One or more of the other initiated processes may arrange for activation of a service component (e.g. 911 emergency location service) a predetermined period before the installation date.