You should better know whether you clone at all. Only you know your configuration. But of course you might verify whether you have any active clone pool and if there are volumes labeled and used for that pool. Last not least your could also use mminfo and also report "copies". It will tell you the number of instances for the save set.   Each save set has a cloneid (it is basically the nsavetime timestamp, as it is unique). So if you do not see a cloneid, it might be due to the fact that you copied my command ... incl. my typo (cloneceid instead of cloneid). Sorry.   If you want to query the save sets of a specific volume, just use    mminfo -q "volume=vol_name" -r ....   The mminfo command is one of the best described commands in NW. You will find the full set of parameters in the Command Line Reference manual. You must not necessarily have the whole content in your mind but you should understand the basics how to use the command. And do not forget - mminfo just queries the media index, it does not change the content. So please familiarize with the command to learn it ... it does not harm.  
EMC Networker 9.1 - Problem with our weekly backups. We have set FULL weekly backups with 2 weeks retention. Recently I noticed the weekly disk volume (where the backups are saved) is getting almost out of space. Checking the Volume Save Sets I see old Weekly backups with Save Times from 7 months ago still present with a Browsable status, even though their Clone Retention Time is correct (it is 2 weeks after the Save Time). I tried to change the retention time manually with Change Expiration and selecting Expire the selected save sets NOW, then I ran the following commands to scan the volumes and clean space: mminfo -q "type=data domain,type=adv_file" -r volume -xcl > volume.lstfor /f %A in (volume.lst) do [NAME] -X -V %Afor /f %A in (volume.lst) do [NAME] -C -V %A That didn't do anything, no space was freed and the Savesets were still present. Next I tried the scanner command:  scanner -m W:\Weeklybackups It didn't free any space, in addition, I noticed that the scanner commands changed the Close Retention Time for ALL the savesets to 2 weeks in the future! How do I resolve this, how do I expire and delete old savesets?
Stubborn Clone Retention Time - Savesets won't delete