From a single IBM Spectrum Protect™ Snapshot
installation, you can manage all of the IBM Spectrum
Protect Snapshot installations in your
organization and mount VSS snapshots to remote servers.
Before you begin
To use the remote management and remote mount features, you must install and enable Windows PowerShell 3.0, or later, on all
IBM Spectrum
Protect Snapshot installations that you want to
manage. To download, install, and enable the software, follow the instructions in:
Microsoft
Windows Management Framework 3.0 Downloads
Procedure
- Enable remote management for IBM Spectrum
Protect Snapshot installations or the Remote Mounting feature by entering the following Windows PowerShell command.
Enable-PSRemoting -force
- Add the IBM Spectrum
Protect Snapshot servers to
the trusted hosts list by entering the following command on each remote system:
Set-Item WSMan:\locahost\Client\TrustedHosts -Value
remote_server_name,local_host_name -Force
where remote_server_name specifies the remote server.
- Restart the winrm service by entering the following command:
Restart-Service winrm
- Optional: If you use the IBM Spectrum Protect
Snapshot for Microsoft Exchange Server software,
enable the Windows PowerShell Remoting feature with
Credential Security Support Provider (CredSSP) authentication. Complete the following steps:
- On the primary system, enter the following command to enable the Windows PowerShell Remoting feature with CredSSP:
enable-wsmancredssp -role client -delegatecomputer remote_computer_name
where remote_computer_name specifies the remote computer.
- On each remote system that runs the IBM Spectrum Protect
Snapshot for Microsoft Exchange Server software, enter the following command to enable the Windows PowerShell Remoting feature with CredSSP:
enable-wsmancredssp -role server
- Verify that the Windows PowerShell Remoting feature is
configured by using one of the following methods:
- Use the "Test-WSMan" cmdlet to test whether the WinRM service is running on the remote
computer.
A. On Server A, enter the following cmdlet to verify that the Windows PowerShell Remoting feature is configured correctly:
Test-WSMan remote_server_name
where
remote_server_name specifies the remote server.
B. On Server B, enter the
following cmdlet to verify that the Windows PowerShell
Remoting feature is configured correctly:
Test-WSMan remote_server_name
where
remote_server_name specifies the remote server.
Restriction: For the remote mount feature, you must use the same computer name that you
use with the /RemoteComputer CLI option.
- To verify that the Windows PowerShell Remoting
feature is configured, enter the following cmdlets:
A. On Server A and Server B when Credential
Security Support Provider (CredSSP) authentication is not enabled, enter the following cmdlet:
invoke-command -computername remote_server_name
-scriptblock {pwd} -Credential $creds
where
-computername specifies the remote computer name and
remote_server_name specifies the remote server.
B. On Server A and Server B
when Credential Security Support Provider (CredSSP) authentication is enabled, enter the following
cmdlet:
invoke-command -computername remote_server_name
-scriptblock {pwd} -Credential $creds -Authentication Credssp
where
-computername specifies the remote computer name and
remote_server_name specifies the remote server.
Restriction: For the remote mount feature, you must use the same computer name that you
use with the /RemoteComputer CLI option. In addition, when you use the CLI command
for the remote mount feature, use the same user name and password that you use with the
/RemoteComputerUser and /RemoteComputerPassword CLI
options.
- Click . To verify a test connection to a remote computer, in the
Actions pane, click Manage Computers. Click
Test Connection.
- Add a remote system. Click . To add a computer to the selected Tree Nodes, in the
Actions pane, click Manage Computers. Click the
plus-sign icon.