But I would like to understand the applicability of a particular technology on something indicative example. Please, If you are not hard... I think this will be very useful information for all of us...
Tnks
In short, you will be able to keep your data highly avaialble, you`ll get ability to recover in any point-in-time, even on the disaster recovery site, during your SSD will keep live longer while your RAID 5 will suddenly start showing you good read AND WRITE rates. I think this should give you the general idea of the concepts of next version. If this is not enough, maybe it is good idea to contact our sales dep and they`ll provide you with the required information specific to any potential project.
Will background CDP consolation be making an appearance?
As it is now, as snapshots expire, the underlining storage container remains in place as long as some of the data in the container remains valid data. This has an impact of rapidly filling disk space as remnants of old container files seem to stick around for very long times, instead of consolidating very old files. As it is now the only way to clean up the CDP files, is every few months copy the data out into another CDP volume. I moved to DD containers with delete enabled but this has its own limits as well, but does seem the closest thing to a build it and forget about it there is.
Actually this is how it should work starting from next version. Right now the deletion support is only experimental feature, which menas that it is highly not reommended to use it in the production environment.
I would like to see a background service that works in a round robin fashion, and moves from one CDP to the next, until it cycles through all the CDP’s and then take a break for a week or a month and then starts again. As Starwind manages all the IO it could run it in the background, letting other IO activity have priority. Either by having the base CDP file purge expired data fragments and then merges in the valid fragments from expired CDP files. Or copy out valid data from the old base CDP file into a new base file and then merge in valid fragments form expired CDP files. Whichever makes the most Defrag sense inside of the base file should be used I would think (to many holes to plug, copy, only a few holes to plug, merge).
Otherwise for me CDP doesn’t have a valid reason to be used; it is just too much maintenance.
We should have it in the next release as well.
Thank you for a great product,
It is my hope the feedback is taken as constructive feedback and not a complaint in any way
Thank you for your feedback - it was constructive and really fluent. Only by knowing what people require we can determine where to move exactly! Thank you!
