Subscribe

Too many snapvault registry entries by DFPM 3.8, may they be deleted?

DFPM is creating a huge amount of snap sched entries in the filers registry. In fact there is one entry for each snapvault relationship (guess that is expected) but there is also one entry for each backup that was done. This is causing major pain and high cpu.

So can these entries be deleted without doing any harm to DFPMs schedules, restores, backups or for whatever it may use these entries?

Re: Too many snapvault registry entries by DFPM 3.8, may they be deleted?

Yes, use the command "snapvault snap unsched"

on the filer  secondary volume to delete the stale entries.


Regards
adai

Re: Too many snapvault registry entries by DFPM 3.8, may they be deleted?

Be aware that deleting a large amount of schedules results in a memory leak issue on ontap 7.3.1.1. So deleting too many schedules 400 Mb memory leak per 1000 delted schedules.

So you may need to reboot the filer where the sched are delted.