Hi it seems despite NTAP_PM_RUN_BACKUP=N is set a snapvault is triggered every time SC is run.
Could Ctrl+M make this being handled as NTAP_PM_RUN_BACKUP=Y on a Redhat Linux server?
It seems odd though.
This is on a 3.4p2 install on a Redhat 5.7 server.
Or any other explanation?
We schedule the backups via PM and the scedule is none on primary and 23:00 daily on secondary.
Also we want Protection Manager to handle all retention times.
It workes just fine.
Bu if the PM dataset is in a non-conformant state then SC just wanrs about it and do not update PM with the snapshot.
This creates a primary snapshot that PM is unaware of.
Any way to secure that SC is not allowed to take any snapshots that PM is unaware of?
Or to clean up and remove all snapshots unknown by PM?
Regards Magnus Nyvall
