Archive for the ‘backup’ Category

Avamar granular restore failed / continuous process

Posted: 09/21/2021 in Avamar, backup
0

At proxy:
service vmwareflr restart
service axionfs restart

check in /usr/local/avamar/var (at proxy):
axionfs_xxxxxxx_xxxx_xxxx_xxxxxxxxxxxx.log

VMware VDP stuck at 70%

Posted: 08/19/2021 in Avamar, backup, Vsphere Data Protection
0
  1. vi /usr/local/avamar/lib/mcsutils.pm
  2. Add line under $prefs variable:

    . "-Dsecurity.provider.rsa.JsafeJCE.position=last"
  3. reboot appliance

Disable CBT without poweroff VM by Avamar

Posted: 07/30/2019 in backup, DPM, Uncategorized, VMware
0

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

DPM cannot continue protection for VMware

Posted: 03/13/2018 in backup, Data Protection Manager, DPM, Hyper-V, System Center, virtualization, VMware, Windows
Tags: , ,
0

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! :)