Netapp SnapManager for Exchange 6.0.4 new-backup error

I came across this error the other day after upgrading from Netapp SnapManager for Exchange 6.0.3 to 6.0.4. When I tried to run a backup it would produce this error in the Windows Eventviewer:

Job : new-backup -Server ‘EXCHANGE’ -ManagementGroup ‘Weekly’ -BackupTruncatedLogs $False -RetainBackups 4 -RetainUtmBackups 0 -StorageGroup ‘DB1′,’DB2′,’PF’ -Verify -VerificationServer ‘Exchange’ -UseMountPoint -RemoteAdditionalCopyBackup $False
The operation executed with the following results.
Details: An Unexpected Error occurred while executing new-backup.
Details: Cannot invoke this function because the current host does not implement it.
Stack Trace : at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.ThrowNotInteractive()
at System.Management.Automation.Internal.Host.InternalHostUserInterface.PromptForChoice(String caption, String message, Collection`1 choices, Int32 defaultChoice)
at System.Management.Automation.MshCommandRuntime.InquireHelper(String inquireMessage, String inquireCaption, Boolean allowYesToAll, Boolean allowNoToAll, Boolean replaceNoWithHalt)
at System.Management.Automation.MshCommandRuntime.DoShouldContinue(String query, String caption, Boolean supportsToAllOptions, Boolean& yesToAll, Boolean& noToAll)
at System.Management.Automation.MshCommandRuntime.ShouldContinue(String query, String caption)
at System.Management.Automation.Cmdlet.ShouldContinue(String query, String caption)
at SMEPSSnapin.SMEBackup.ProcessRecord()
Stack Trace: at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
at System.Management.Automation.PipelineNode.Execute(Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)
at System.Management.Automation.StatementListNode.ExecuteStatement(ParseTreeNode statement, Array input, Pipe outputPipe, ArrayList& resultList, ExecutionContext context)

I had to work with Netapp support in order to resolve this which actually got escalated to Level 2. The issue is simply with the -RetainUtmBackups option. This option is incorrect if you specify a value of 0, meaning you don’t want to retain up to the minute restore capabilities. To resolve this you must do 1 of 2 things:
1. Use -RetainUtmBackups -1 OR
2. Use -NoUtmRestore

The option RetainUtmBackups accepts values above and including 1 if you would like to retain up to the minute Exchange restores.