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
At Present, when we use -disablenetwork:$false in Restore-CohesityVMwareVM cmdlet, still it doesn't connect any network while restoring to alternate vcenter. If we specificy -networkId then only it will attach that particular network ID to restored vm, not all. This is big gap in DR scenarios where we need to attached all networks by default while restoring to alternate vcenters. So ideally -disablenetwork:$false should be sufficient, and should attached all networks present at backup. However that's not happening.
in Rubrik PowerShell, this feature works fine and attaches all networks by default with -disablenetwork:$false
The text was updated successfully, but these errors were encountered:
馃殌 Feature Request
At Present, when we use -disablenetwork:$false in Restore-CohesityVMwareVM cmdlet, still it doesn't connect any network while restoring to alternate vcenter. If we specificy -networkId then only it will attach that particular network ID to restored vm, not all. This is big gap in DR scenarios where we need to attached all networks by default while restoring to alternate vcenters. So ideally -disablenetwork:$false should be sufficient, and should attached all networks present at backup. However that's not happening.
in Rubrik PowerShell, this feature works fine and attaches all networks by default with -disablenetwork:$false
The text was updated successfully, but these errors were encountered: