Skip to content

Monitoring

Script location

  1. Create a folder at C:\SyncSafe_Monitoring and make sure the user that will be running the script has permissions to this directory.
  2. Create the script: C:\SyncSafe_Monitoring\Get-DTJob.ps1

Prepare Server Accounts

The monitoring script at this time does not support multiple accounts or domain accounts, so the account used to add and manage servers in the OpenText/DoubleTake console should be the same on source and target. Configure a local administrator account on all systems with identical credentials, e.g. "syncsafe" or "uss-sync" or similar. Use this account when adding servers to the OpenText/DoubleTake Console, and when creating the secret below.

Configure the vault and secrets on the management server

Vault configuration steps:

  1. Install the required modules: Install-Module Microsoft.PowerShell.SecretManagement Install-Module Microsoft.PowerShell.SecretStore
  2. Create the vault: Register-SecretVault -Name SyncSafe -ModuleName Microsoft.PowerShell.SecretStore -DefaultVault
  3. Allow the script to use the vault non-interactively: Set-SecretStoreConfiguration -Authentication None -Interaction None -PasswordTimeout 0

Create the requisite secrets. When prompted enter the username and password for the target replica servers:

set-secret -name "SyncSafe-[Administrator]" -Secret (Get-Credential) Replace [Administrator] with the local admin account created as per the monitoring account preparation.

Create the scheduled task

Currently, the scheduled task is defined as a standard task with the following parameters:

  • Standard task, run whether user is logged in or not, run with highest privileges
  • Probably optional, but configured for the appropriate version of the OS (e.g. server 2025)
  • Triggers > choose a time and run the task every 5 minutes, recurring every 1 day, make sure it's enabled
  • Actions > Start a program -- Program/Script: powershell -- Add arguments "C:\SyncSafe_Monitoring\Get-DTJob.ps1"

You should be prompted to input the credentials for the task, this is very important as this ensures that the script will run even when the user is not logged in.

Worth with the Monitoring team to obtain the necessary prereqs for monitoring with Zabbix.