HP Storage Mirroring Software - Manual (Page 181)

179 of 195
recommendation can be confusing. You want to enable the account,
which means this option should not have a checkmark. If the option
does have a checkmark, meaning the account would be disabled, file
recalls will not function.
f. Finish the account creation wizard.
3. Add the new service account to the local Administrators group on the source and
repository server.
4. Add the new service account to the local Double-Take Recall group on the source
and repository server.
5. Modify the Storage Mirroring Recall service on the source and repository server to
use the new service account.
a. From the services applet (Administrative Tools, Services) right-click the
Storage Mirroring Recall service and select Properties.
b. On the Log On tab, select This account and specify the new user and the
password.
c. On the General tab, select Startup type, and select Automatic.
d. Click OK to save the changes.
6. Start the Storage Mirroring Recall service on the source and repository server. If
the service is already running, you must stop and restart it so that it uses the user
account and group modifications you just made.
Note
If you have an active Storage Mirroring Replicate job, you can validate
your security configuration using the Replication Console.
1. Open the Replication Console by selecting Start, Programs,
Storage Mirroring, Storage Mirroring Replication Console.
2. Double-click your source machine in the left pane of the Replication
Console to log on to it.
3. With the source highlighted in the left pane, locate in the right pane
the Storage Mirroring protection job in the Replication Set column.
The name will be created from the source and repository server
names and the keyword Protection or Data Protection.
4. Right-click the protection job in the right pane of the Replication
Console and select Connection Manager.
5. Select the Archive Options tab.
6. Click Validate.
The validation checks to see if the correct service is running and if it has
an account in the correct security group. It also confirms if the repository
server has shared the archive bin correctly and if network communications