You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is no dedicated cmdlet to remove a Rubrik backup. Invoke-RubrikRESTCall can support this task, but having a cmdlet that can take a pipeline input from cmdlets such as Get-RubrikVM or Get-RubrikFileset and remove a backup(s) would simplify a workflow.
For example, if I want to be able to remove backup of relics that are 30 days or older, I want to be able to do something like this:
Currently, we have to produce a snapshot ID and then feed it into Invoke-RubrikRESTCall. It's not impossible, but it's not as intuitive as it would be if a cmdlet to remove a backup that can take a pipeline input were available. For example, my line to invoke the forementioned REST call looked like this:
We have started developing the requested feature, our apologies for the delay in picking this up. This functionality will be available within a couple of days.
Expected Behavior
Currently there is no dedicated cmdlet to remove a Rubrik backup. Invoke-RubrikRESTCall can support this task, but having a cmdlet that can take a pipeline input from cmdlets such as Get-RubrikVM or Get-RubrikFileset and remove a backup(s) would simplify a workflow.
For example, if I want to be able to remove backup of relics that are 30 days or older, I want to be able to do something like this:
Get-RubrikVM TestVM1 | ?{$_.isRelic -eq $true} | Get-RubrikSnapshot | {$_.date -lt (Get-date).adddays(-30).tostring("yyyy-MM-ddTHH:mm:ssZ")} | Remove-RubrikSnapshot
Current Behavior
Currently, we have to produce a snapshot ID and then feed it into Invoke-RubrikRESTCall. It's not impossible, but it's not as intuitive as it would be if a cmdlet to remove a backup that can take a pipeline input were available. For example, my line to invoke the forementioned REST call looked like this:
Invoke-RubrikRESTCall -Endpoint 'vmware/vm/snapshot/d7d8dd59-3e5c-4f23-88aa-b6b5cadb0f4d' -Method DELETE -Query (new-object -typename psobject -property @{'location'='all'})
This is specific to VM backups. I suspect the endpoint path would look different for databases and filesets.
The text was updated successfully, but these errors were encountered: