Disable CBT without poweroff VM by Avamar

admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX

======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:18:03 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————————————————-
Jul 30, 2019 4:18:06 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : true
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:18:08 PM CEST

 

 

 
admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –disablecbt –vm XXXXXXXXXXXXXXXXXXXXXX
======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:18:33 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –disablecbt –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————– ———————————–
Jul 30, 2019 4:18:35 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : true
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250
Disabling CBT for : XXXXXXXXXXXXXXXXXXXXXX

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:18:38 PM CEST

 

 

 

 

admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX
======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:18:45 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————————————————-
Jul 30, 2019 4:18:48 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : false
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:18:50 PM CEST

 

 

 
admin@XXXXXXXXXXXXXXXXXXXXXX:~/>: ./proxycp.jar –cbtstatus –enablecbt –vm XXXXXXXXXXXXXXXXXXXXXX
======================= Starting ProxyCP ==========================

Proxycp : v2.79
Date : July 30, 2019 4:22:13 PM CEST

COMMAND : java -jar proxycp.jar –cbtstatus –enablecbt –vm XXXXXXXXXXXXXXXXXXXXXX

VDP/Nemo Detected : false
——————————————————————————————————————-
Jul 30, 2019 4:22:18 PM com.avamar.mc.security.registry.ProviderRegistryBasic register
INFO: Provider “JsafeJCE version 5.0” is registered at position 10
VM Name(Avamar) : XXXXXXXXXXXXXXXXXXXXXX
VM Name(Vmware) : XXXXXXXXXXXXXXXXXXXXXX
CBT Enabled : true
Hardware Version : 8
SCSI Controller : SCSI controller 0 VMware paravirtual SCSI
Disk Type : persistent
File Name : XXXXXXXXXXXXXXXXXXXXXX
File Name : XXXXXXXXXXXXXXXXXXXXXX
Disk Mode : persistent
Type : Thin Provisioned
Total Size (GB) : 250

————————————————————————————————————
——————————————————————————————————————-
Closing Connection Pool : July 30, 2019 4:22:21 PM CEST

Zabbix monitor SC DPM backup status

Monitor System Center Data Protection Manager by Zabbix:

1. Install zabbix agent on Windows (make it reports to server)
2. Create PowerShell script that reports SCDPM status:

import-module DataProtectionManager
$dpmserver = connect-dpmserver (&hostname) -WarningAction:SilentlyContinue
$dpmserver.alertcontroller.refreshalerts()
#Wait-Event -timeout 15
$alerts = @($dpmserver.AlertController.ActiveAlerts.Values)
$warnings = $alerts | where-object {$_.Severity -eq “Warning”} | Measure-Object | select count
$errors = $alerts | where-object {$_.Severity -like “Error”} | Measure-Object | select count
if ($errors.count -ne 0) {
$status = “Error – One or more error conditions exist and backups need to be checked.”
$returnCode = 2
}
elseif ($warnings.count -ne 0) {
$status = “Warning – One or more warning conditions exist. Log onto DPM server to check the status.”
$returnCode = 1
}
else {
$status = “OK”
$returnCode = 0
}
write-host $status
exit $returnCode

source: https://social.technet.microsoft.com/Forums/en-US/02a7e440-7501-4fd7-9052-ee0850995b09/remote-dpm-monitoring-possibilities?forum=dataprotectionmanager

 

3. Create ITEM on Zabbix Server:

TYPE:
Zabbix Agent (Active)

KEY:
system.run[“C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -File C:\zabbix_check.ps1”,]

 

4. On Zabbix Agent config add timeout:

#timeout for powershell script
Timeout=30

DPM cannot continue protection for VMware

Problem:

Type: Consistency check Status: Failed Description: DPM cannot continue protection for VMware <vm_name> on <vCenter_server/ESX host IP>  (ID 30184) More information End time: 2018-03-12 23:48:37 Start time: 2018-03-12 23:48:37 Time elapsed: 00:00:00 Data transferred: 0 MB Cluster node – Source details: <vm_name> Protection group: Protection Group 1 Items scanned: 0 Items fixed: 0

 

Resolution 1:

Problem with VM *.vmx file.

• Delete vmx and recreate VM
  or
• create new VM and bind hdd from old VM.

 

Resolution 2:

• check if there is not snapshot on VM! :)

System Center DPM 2016 Install Error ID: 812

System Center Data Protection 2016

SC-SQL – IP: 10.45.1.200
SC-DPM – IP: 10.45.1.201

Problem:

Installing DPM and connecting it to remote SQL, I’ve got error 812

System Center DPM 2016 Install Error ID: 812

Report configuration failed. Verify that SQL Server Reporting Services is installed properly and that it is running. ID: 812 . When installing Data Protection Manager DPM  common installation error system admins encounter is ID: 812. This is caused by the SQL Server Reporting Services misreading the reporting database.

 

Cause:

Changed account which runs service: Reporting Service

 

Resolution:

Start -> Reporting Services Configuration Manager -> Encryption Keys -> Delete Encrypted Content (click: Delete) -> Change (click: Change) – generates new encryption keys :)

 

Now you may resume installation of DPM :)