If the replay is mounted as a volume it will never expire on the original volume. We ran into this every thing when we had to restore a complete volume from a replay. The real issue is that replay volume on the original will continue to grow and will never actually be combined (expired). Two fixes that i'm aware of: 1. Use storage vmotion (you stated you were in a vmware environment) and vmotion anything on that new view volume to a new volume. Once the view volume is empty unmount it in vsphere, remove mappings in compellent and deleted the volume. At that point the replay will expire on the originating volume. 2. This one is coming from Compellent support so i'm not 100% sure on the steps involved (we are a vmware shop so we just did a storage vmotion) - you can run a copy and move command which will in turn copy the data as new to the new volume. This will then allow that replay to be released from the original volume. Save yourself the time and headaches - just storage vmotion off of that view volume what you need and delete it. That's was we did.
 So I have created a volume from a reply, mapped it into vsphere and its showing up fine as a new datastore, all is good! But my query is, the original replay that I have used to create a datastore, is set to expire in 2 days? What will happen to the new volume I have mapped as a result of this expiring? The new volume has its own replays, which seem to mirror the old volume? Also you will see I have created a manual replay on the original one at he request of the Devs, so that can be ignored [IMAGE][IMAGE][IMAGE]  Cheers
I have created a volume from a replay..............