If the volume was recovered from a Replay and continues to technically run from that particular Replay then the Replay itself will look like in the GUI that it is still there and will never "expire" unless you unmapped and then deleted the "view" of that Replay, but since it is considered your active volume it will stay looking like that always. It's not keeping any extra data around since the data that is a part of that Replay is the active data on the server. The only way I know that you can clean up the look of the volume would be to create a new volume of the exact size and do a CMM (copy mirror migrate) of the old view volume into the new volume, then delete the view volume, and then it would look "clean" in the GUI.  Either option will net you the same amount of used disk space in the end though so it may not be worth the effort and you would need 2x the original disk space while it's doing the CMM process.  If you don't know how to do the CMM process Copilot can walk you through it. It's a pretty straight forward process.
Hello, I'm new to Compellent Storage and with my new position was asked to "figure out" our replay situation.  We have quite a few volumes set up and about half of them have old, expired replays from 3 or 4 years ago. In System Manager most just say: State: Frozen Source: Created by user Create volume: {deleted volume} Some say source as "created by schedule" and actually have a volume listed under Create Volume. My understanding is that several years ago there was some kind of issue and they went thru and created new volumes from these replays and then attached those volumes to servers and they're now being used as new volumes. That's what someone told me anyway. So I have several questions: 1) Is there a way to tell where these replays are now being used as active volumes? 2) Is there a way to get rid of the expired replays so we can reclaim the storage, without effecting anything - specifically the new volumes that were created off them? 3) We replicate most of our LUNs to a different data center and most of the time the replays get stuck and we get way behind on the replication. Looks like replication is only using about 50megs of our 100meg pipe, even tho there's not much else using the replication link. Is there some other way we should be configuring things? Right now we have our replay schedule to go once per hour. Thanks for any and all help. I plan on calling support, but would like to be more armed with knowledge and have stuff to look at on my side before calling them
Frozen Replays