A couple of things, first an LVM snapshot is discrete with the aperture or gap between the snaps set by the customer where in our CDP implementation we capture every write and give the user the ability to unwind to any point in time. I also think with LVM you have a limit on the number of concurrent shapshots, where with our CDP you are only limited to the amount of storage you've reserved for the journal.
Second, our CDP solution is heterogeneous and operates across any open system platform and is not reliant on any host-based component (e.g. A volume manager such as LVM) -- also CDP images can span SERVERS/OS platforms and ARRAY platforms — for example you can have CDP operating on LUNs that are accessed by two or more differing operating systems giving you a true "federated" CDP — with LVM you are restricted to the single host (or clustered host environment)
'failed to grasp how this differs from good old LVM snapshots.
natmaka 3 years ago
A couple of things, first an LVM snapshot is discrete with the aperture or gap between the snaps set by the customer where in our CDP implementation we capture every write and give the user the ability to unwind to any point in time. I also think with LVM you have a limit on the number of concurrent shapshots, where with our CDP you are only limited to the amount of storage you've reserved for the journal.
PointBB 3 years ago
Second, our CDP solution is heterogeneous and operates across any open system platform and is not reliant on any host-based component (e.g. A volume manager such as LVM) -- also CDP images can span SERVERS/OS platforms and ARRAY platforms — for example you can have CDP operating on LUNs that are accessed by two or more differing operating systems giving you a true "federated" CDP — with LVM you are restricted to the single host (or clustered host environment)
PointBB 3 years ago