1. A mat for use on an underlying surface including at least one of a carpeted surface and a hard floor surface, the mat comprising:
a body comprising a substantially planar upper surface, a perimeter defining an outer edge of the body, and a lower surface substantially parallel to the upper surface, and
a slip-resistant layer bonded to the lower surface of the body, the slip-resistant layer having a thickness not greater than 0.020 inches and having a static coefficient of friction of at least 0.50 to facilitate stable placement of said mat with respect to said underlying surface.
2. The mat of claim 1, wherein the body of the mat further comprises at least one of polyvinyl chloride (PVC), polypropylene, high density polyethylene, polyester copolymers, or polycarbonate.
3. The mat of claim 1, wherein the slip-resistant layer further comprises at least one of ethylene vinyl acetate or polyurethane.
4. The mat of claim 1, wherein the slip-resistant layer has a static coefficient of friction of at least 0.60.
5. The mat of claim 1, wherein the slip-resistant layer is in the form of a series of strips.
6. The mat of claim 5, wherein the series of strips longitudinally extend along the body to form a layer that includes voids between the strips.
7. The mat of claim 1, wherein the slip-resistant layer is coextensive with the mat body.
8. A mat comprising:
a body formed with a predetermined thickness between a first planar surface of the body formed opposite to a second planar surface of the body; and
a slip-resistant layer formed with a predetermined thickness that is less than the predetermined thickness of the body, the slip-resistant layer contiguously coupled in parallel with only one of the first planar surface and the second planar surface such that the body and the slip-resistant layer form a single unitary member for use on an underlying floor comprising at least one of a carpeted floor surface or a hard floor surface;
the slip-resistant layer alignable with the underlying floor to create a static coefficient of friction between the slip resistant layer and the underlying floor of at least 0.50.
9. The mat of claim 8, wherein the body and the slip-resistance layer are coupled by an extrusion process.
10. The mat of claim 8, wherein the body and the slip-resistance layer are coupled by a lamination process.
11. The mat of claim 8, wherein the slip resistant layer comprises a high coefficient of friction polymeric material.
12. The mat of claim 11, where the polymeric material comprises at least one of a polyurethane or a poly vinyl acetate.
13. The mat of claim 8, wherein the static coefficient of friction between the slip-resistant layer and the underlying floor is higher than the static coefficient of friction between the body and the underlying floor.
14. The mat of claim 8, wherein the slip resistant layer separates the body from the underlying floor.
15. The mat of claim 8, wherein the slip resistant layer separates only a portion of the body from the underlying floor.
16. A mat comprising:
a slip-resistant layer formed to include a first planar surface and a second planar surface that is parallel and opposite the first planar surface; and
a body coupled with only the first planar surface of the slip-resistant layer such that the body and the slip-resistant layer are layers formed as a single unitary structure having a thickness, in which a first portion of the thickness is the body and a second portion of the thickness is the slip-resistant layer, the first portion being greater than the second portion; and
wherein the single unitary structure is alignable with an underlying floor to create a static coefficient of friction between second planar surface of the slip-resistant layer and the underlying floor of greater than 0.50.
17. The mat of claim 16, wherein the body comprises at least one of polyvinyl chloride (PVC), polypropylene, high density polyethylene, polyester copolymers, or polycarbonate, and the slip resistant layer comprises at least one of ethylene vinyl acetate or polyurethane.
18. The mat of claim 16, wherein any form of adhesive substance is absent from the second planar surface.
19. The mat of claim 16, wherein the slip-resistant layer is bonded to a lower surface of the body by extrusion of the slip-resistant layer and the body.
20. The mat of claim 16, wherein a thickness between the first planar surface and the second planar surface is not greater than 0.020 inches.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A system for providing assured recovery and replication, comprising:
a master data source configured to store application data;
a replica data source configured to replicate the application data stored in the master data source;
a volume snapshot service configured to create a master snapshot associated with the master data source, wherein the master snapshot copies the application data stored in the master data source; and
a replication server in communication with the master data source and the replica data source, wherein the replication server includes one or more processors configured to:
confirm that the master data source can be recovered from the replica data source in response to validating that the application data copied in the master snapshot and the application data replicated in the replica data source have a consistent state;
create a replica snapshot associated with the replica data source in response to a request to recover the master data source from the replica data source, wherein the replica snapshot copies the application data replicated in the replica data source;
assign an identity associated with the master data source to the replica data source to transfer control over storing the application data from the master data source to the replica data source;
resume replicating the application data on a virtual machine disk file associated with the replica snapshot.
2. The system of claim 1, wherein the volume snapshot service records a bookmark associated with the master snapshot to distinguish the master snapshot from one or more additional master snapshots created with the volume snapshot service.
3. The system of claim 1, wherein the one or more processors associated with the replication server are further configured to:
compare metadata that describes the master snapshot to metadata that describes the replica data source;
validate the consistent state between the master snapshot and the replica data source in response to confirming that no differences exist between the metadata that describes the master snapshot and the metadata that describes the replica data source; and
establish the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to determining that one or more differences exist between the metadata that describes the master snapshot and the metadata that describes the replica data source.
4. The system of claim 1, wherein the one or more processors associated with the replication server are further configured to:
perform a binary difference comparison between the master snapshot and the replica data source;
validate the consistent state between the master snapshot and the replica data source in response to the binary difference comparison confirming that no differences exist between the master snapshot and the replica data source; and
establish the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to the binary difference comparison identifying one or more differences between the master snapshot and the replica data source.
5. The system of claim 4, wherein the one or more processors associated with the replication server limit the binary difference comparison to one or more files that have changed in the master snapshot or the replica data source.
6. The system of claim 1, wherein the one or more processors associated with the replication server are further configured to:
suspend replicating the application data stored in the master data source to the replica data source while validating the consistent state between the master snapshot and the replica data source; and
resume replicating the application data stored in the master data source to the replica data source in response to validating the consistent state between the master snapshot and the replica data source.
7. The system of claim 1, wherein the one or more processors associated with the replication server are further configured to:
compare the master snapshot to the replica snapshot associated with the replica data source to validate the consistent state between the master snapshot and the replica data source; and
continue replicating the application data stored in the master data source to the replica data source while comparing the master snapshot to the replica snapshot to validate the consistent state between the master snapshot and the replica data source.
8. The system of claim 1, wherein the one or more processors associated with the replication server are further configured to:
replicate information associated with an application and an operating system that interacts with the master data source to the virtual machine disk file, wherein the one or more processors create the replica snapshot associated with the replica data source from the virtual machine disk file; and
boot a virtual machine created from the virtual machine disk file, wherein the one or more processors assign the identity associated with the master data source to the replica data source in response to verifying that the application and the operating system have a healthy state in the virtual machine created from the virtual machine disk file.
9. The system of claim 1, wherein the one or more processors are further configured to generate a report that describes any delays associated with replicating the application data to the replica data source or the virtual machine disk file based on one or more timestamps included in one or more messages associated with replicating the application data.
10. The system of claim 1, wherein the one or more processors are further configured to:
execute one or more operations that apply one or more changes to the application data stored in the master data source; and
generate a report that describes whether the master data source and the replica data source are correctly replicating based on whether the one or more changes applied to the master data source have been applied to the replica data source.
11. A method for providing assured recovery and replication, comprising:
replicating application data stored in a master data source on a replica data source;
invoking a volume snapshot service to create a master snapshot associated with the master data source, wherein the master snapshot copies the application data stored in the master data source;
confirming that the master data source can be recovered from the replica data source in response to a replication server validating that the application data copied in the master snapshot and the application data replicated in the replica data source have a consistent state;
creating a replica snapshot associated with the replica data source in response to a request to recover the master data source from the replica data source, wherein the replica snapshot copies the application data replicated in the replica data source;
assigning an identity associated with the master data source to the replica data source, wherein the replication server assigns the identity associated with the master data source to the replica data source to cause the replica data source to assume control over storing the application data from the master data source; and
replicating the application data on a virtual machine disk file associated with the replica snapshot in response to the replica data source assuming control over storing the application data from the master data source.
12. The method of claim 11, wherein the volume snapshot service records a bookmark associated with the master snapshot to distinguish the master snapshot from one or more additional master snapshots created with the volume snapshot service.
13. The method of claim 11, further comprising:
comparing metadata that describes the master snapshot to metadata that describes the replica data source;
validating the consistent state between the master snapshot and the replica data source in response to confirming that no differences exist between the metadata that describes the master snapshot and the metadata that describes the replica data source; and
establishing the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to determining that one or more differences exist between the metadata that describes the master snapshot and the metadata that describes the replica data source.
14. The method of claim 11, further comprising:
performing a binary difference comparison between the master snapshot and the replica data source;
validating the consistent state between the master snapshot and the replica data source in response to the binary difference comparison confirming that no differences exist between the master snapshot and the replica data source; and
establishing the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to the binary difference comparison identifying one or more differences between the master snapshot and the replica data source.
15. The method of claim 14, further comprising limiting the binary difference comparison to one or more files that have changed in the master snapshot or the replica data source.
16. The method of claim 11, further comprising:
suspending replication between the application data stored in the master data source and the replicated application data stored in the replica data source while validating the consistent state between the master snapshot and the replica data source; and
resuming replication between the application data stored in the master data source and the replicated application data stored in the replica data source in response to validating the consistent state between the master snapshot and the replica data source.
17. The method of claim 11, further comprising:
comparing the master snapshot to the replica snapshot associated with the replica data source to validate the consistent state between the master snapshot and the replica data source; and
continuing to replicate the application data stored in the master data source on the replica data source while validating the consistent state between the master snapshot and the replica data source.
18. The method of claim 11, further comprising:
replicating information associated with an application and an operating system that interacts with the master data source to the virtual machine disk file, wherein the replication server creates the replica snapshot associated with the replica data source from the virtual machine disk file; and
booting a virtual machine created from the virtual machine disk file, wherein the replication server assigns the identity associated with the master data source to the replica data source in response to verifying that the application and the operating system have a healthy state in the virtual machine created from the virtual machine disk file.
19. The method of claim 11, further comprising generating a report that describes any delays associated with replicating the application data to the replica data source or the virtual machine disk file based on one or more timestamps included in one or more messages associated with replicating the application data.
20. The method of claim 11, further comprising:
executing one or more operations that apply one or more changes to the application data stored in the master data source; and
generating a report that describes whether the master data source and the replica data source are correctly replicating based on whether the one or more changes applied to the master data source have been applied to the replica data source.