I have noticed a few pecularities when it comes to OnCommand Core and management of SnapVault relationships, and was seeing if this is just me or a more wide spread problem:
1) If I have an external relationship established and import it into a policy in OnCommand Core, it will NOT remove the existing relationship. It simply creates a second one allowing 2 jobs to be running at the same time. This seems inefficient as the whole thought behind importing would be to manage the relationship through OnCommand and not somewhere else. This creates an additional cleanup process that I was not aware of and was keeping data that should have aged out per our retention policies.
2) If you modify the dataset (ie schedule, throttle, etc), it does not appear to update the relationships, even if it has to run a new conformance. This potentially leaves scheduling conflicts, throttles, etc in place.
OnCommand is presented as a central management for relationships (including backups- SnapVault/Mirror), but this seemingly simple function is missing. Any good backup software will update schedules, retentions, etc when the policy is changed. I realize OnCommand Core is not marketed as backup software (reference SnapProtect), but the Protection Policy functionality does imply this as a "poor man's" backup management software. I only found the above issues after working with PowerGUI and the ONTAP Powershell functions or via the CLI. There was no visible indicators in the GUI that the above issues were present. For a new admin these could present a serious issue.