when I run the backup vmware virtual machine data protection application fails and the job is in execution.

manually cancel the task but still appears in recent work.

as I can cancel and delete the task?

Starting in VDP 6.1 there is a nice new feature where if quiescence fails it will fall back to a non-quiesced backup.  But I believe the check box does opposite of what you would think.  Maybe this could be fixed in the next release.

When its unchecked VDP will do a non-quiesced snapshot if quiescence fails.  If its checked it does not fall back to non-quiesced snapshot.

I confirmed looking at the details of the dataset:

When its checked - type=boolean:name=fail_on_quiesce_error:value=true

When its unchecked - type=boolean:name=fail_on_quiesce_error:value=false

Symptoms:

in vmware VDP 5.5/6.0/6.1, every scheduled backup job fails with error 10014

Cause:

the scheduled job does not match with retention policies

!

Solution:

the retention policies have to match with the frequency set in the scheduled job.

for example, if you want to set a job with daily schedule, you must set at least one day in retention policy panel (Item "this Schedule:", field "Daily for:")

I need to make a backup copy of seven VM for one night. If I just make the job with these VM, they will be processed at the same time that strongly loads a host. Whether it is possible to specify that creation of backup copies shall be made sequentially?

What will do VDP if several tasks are assigned to the same time?

What will do VDP if one task isn't finished, and time to launch another came?

I would clarify it experimentally, but it is terrible to experiment with working system.

Can any one in this group help me in this Task.

Backup a VM without turning it  off.

due to some reason , I have a abc-00002-delta.vmdk and no other files ( no VMX . no abc-0002-flat.vmdk)

is there any way to mount this vmdk in windows to recover files ？

or any way to mount this vmdk in vsphere ？

I tried to create a new VM and attach the vmdk , there is a error messages

"cannot open the disk '*.vmdk' or one of the snapshot disk is depends on"

Long story short - a folder was deleted from the datastore which contained the flat and descriptor file for one drive on a server containing very important data. This was also the time when we found out the backups were corrupt. We have the *000001-ctk.vmdk, *000001-delta.vmdk, and 000001.vmdk file for this drive. Is it possible to recover the main descriptor and flat file (or the entire deleted directory) from this?

Any help is greatly appreciated

I have successfully set up my environment to use backups with ghettoVCB.

Now I would like to email the log file. The problem is however that my mail provider needs authorization so I cannot just enter server, port etc in the script.

Is there a way to enter user name/password for the SMTP-server somewhere?

Best Regards,

Anders

Hello,

I looking for any method for removing old backup on one shot.

Anyone already done it ?

Thanks

Guy

VDP Version: vdp 6.1.3.70

vCenter Version: 6.0.0.20000

We have several VM backups that are stopping during a scheduled job.
The errors we have is:

Error Code: 10014

Type: Scheduled Backup

Error backup:

2017-03-04T06:00:39.486Z avtar Error <7922>: Invalid expires input value (expires=1488607200)

2017-03-04T06:00:39.486Z avtar Error <8939>: Errors occurred preparing for backup (exitcode=152). No backup will be created.

2017-03-04 06:01:39 ASP-ACR-AD-4W-sat7u-ASP-ACR-AD-4W-sat7u-1488607200010 Warning <0000>: Workorder "ASP-ACR-AD-4W-sat7u-ASP-ACR-AD-4W-sat7u-1488607200010" non-zero exit status 'code 164: internal failure'

2017-03-04 06:01:39 ASP-ACR-AD-4W-sat7u-ASP-ACR-AD-4W-sat7u-1488607200010 Info <0000>: <workorder_finished pid="vmimagew" startUTC="2017-03-04 06:00:17" msgver="1" pidnum="3016" finishUTC="2017-03-04 06:01:39" errorcode="164" wid="ASP-ACR-AD-4W-sat7u-ASP-ACR-AD-4W-sat7u-1488607200010" errormessage="*code 164: internal failure*" errorrealm="Plugin 3016-vmimagew" />

When running a manual back-up everything is running fine.

Anybody a solution for this?

Thanks.

I have successfully signed the OVF package with ovftool 4.2. The certificate was signed by a Root CA.

Now the problem is that vSphere Web Client runs into the following error during Deploy OVF Template.

Any help is greatly appreciated.

My environment is a mixture of ESXI 5.1 and 5.5.  Recently added two VDP 6.01 appliances running single backup jobs each with a third VDP 6.01 as a replicate appliance.  I'm using six proxies on one backup appliance and four on the other all deployed to seperate host/datastores - no clusters, HA etc.  Performance is great, but I'm seeing vCenter log spew from the replicate appliance.

Task Name:  VDP:Scheduled Replication Job Destination Task

Task Description:  [Backup Appliance Replication Job] - xxxxxxxxxxxxxxxxx#xx where it looks like the #xx is the id of the VM image in the replicate appliance.  It looks like it's cycling through the VM Image id every couple of seconds with an entry for each VM in the environment.  The net effect is continuous sub-second log entries.

I'm open to ideas on the root cause.  It's not causing any problems except chewing up log space and future log queires.

Thanks

DAMo

VDP configuration and installation are normal, but backup error, backup can not continue, although you see            Fail to download VM metadata, try later, but I don't know what the problem is.            The error log is as follows. Ask for help:

--------------------------------------------------------------------------------------------------------

-----  START avvcbimage log 2019-03-07 11:38:09 CST  [7.2.180-167 Linux-x86_64]

--------------------------------------------------------------------------------------------------------

2019-03-07T11:38:09.033-08:00 avvcbimage Info <5008>: Logging to /usr/local/avamarclient/var/test2-1551929879509-3306f8eb7116f7c3e2b9e9e59a4c3a0c591e4e98-1016-vmimagel.log

2019-03-07T11:38:09.033-08:00 avvcbimage Info <5174>: - Reading /root/.avamar

2019-03-07T11:38:09.033-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamar/etc/usersettings.cfg

2019-03-07T11:38:09.034-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimage.cmd

2019-03-07T11:38:09.034-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd

2019-03-07T11:38:09.038-08:00 avvcbimage Info <6673>: CTL listening on port 52565

2019-03-07T11:38:09.040-08:00 avvcbimage Info <10684>: Setting ctl message version to 3 (from 1)

2019-03-07T11:38:09.040-08:00 avvcbimage Info <16136>: Setting ctl max message size to 268435456

2019-03-07T11:38:09.043-08:00 avvcbimage Info <40636>: SSL Certificate Thumbprint: 58:92:C8:7E:11:CE:AB:36:92:8A:60:40:30:CE:D8:CC:53:F1:40:1C

2019-03-07T11:38:09.043-08:00 avvcbimage Info <0000>: job type = 4

2019-03-07T11:38:09.064-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:09.064-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:09.130-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:09.236-08:00 avvcbimage Info <40726>: VM Config Info: VMX version 4(F), ctk enabled(T), fault tolerant (F), Guest OS Red Hat Enterprise Linux 6 (64-bit), Cloud UUID = NoUUID. version=13

2019-03-07T11:38:09.255-08:00 avvcbimage Info <40727>: VM Guest Info: GuestOS Family = linuxGuest, Guest Full Name = CentOS 4/5 or later (64-bit), Guest OS State = running, Tools Running = guestToolsRunning,  Tools Version Status = guestToolsUnmanaged

2019-03-07T11:38:09.324-08:00 avvcbimage Info <14625>: WorkOrder Disk Info:

   Prior Disk '2000': file(base):'[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk', backItUp=1

                snapshot file:'[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk'

                prior size(KB):0, current size(KB):367001600, match=0

                prior change block ID:''

                Datastore:'Macrosan_AutoTier_Lun03' Directly Accessible=1

2019-03-07T11:38:09.424-08:00 avvcbimage Info <40637>: Proxy Host Name=esxi29.lntmh.com(6.7.1 build-10302608)

2019-03-07T11:38:09.507-08:00 avvcbimage Info <40638>: VM Host Name=esxi30.lntmh.com(6.7.1 build-10302608)

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19547>: Using Simultaneous Workorders method

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19652>: Updated cache lookup

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19587>: Create cache lock file succeeded

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19588>: usLockFile: /usr/local/avamarclient/bin/var1.lck

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11979>: proxy VM DNS name is: 127.0.0.2,vdp01.lntmh.com,vdp01,192.168.101.126

2019-03-07T11:38:09.508-08:00 avvcbimage Info <18672>: proxy VM Instance name is: vdp01.lntmh.com-proxy-1

2019-03-07T11:38:09.508-08:00 avvcbimage Info <17793>: proxy VM Moref is: vm-5063

2019-03-07T11:38:09.508-08:00 avvcbimage Info <16010>: vCenter 'New Core Business' is vcsa01.lntmh.com

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11981>: VM's host is esxi30.lntmh.com

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11982>: VM's primary storage location is [Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmx

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11983>: VM's vCenter ID is vm-3973

2019-03-07T11:38:09.508-08:00 avvcbimage Info <19658>: change block file: VmImage1_changefilemap.tmp

2019-03-07T11:38:09.541-08:00 avvcbimage Info <11984>: VM's backup account on vdp01.lntmh.com is /vcsa01.lntmh.com/VirtualMachines/ZYLWEB01_UBfzB1oMmAggk1yC18TNtA

2019-03-07T11:38:09.541-08:00 avvcbimage Info <11986>: Changed block tracking is engaged for this VM

2019-03-07T11:38:09.541-08:00 avvcbimage Info <11988>: A reference to a valid prior backup is not available so this will be a full level zero backup.

2019-03-07T11:38:09.610-08:00 avvcbimage Info <19549>: metadata tmp dir: /usr/local/avamarclient/var/vmware/1/temp

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware/1, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware/1/temp, failed (-1)

2019-03-07T11:38:09.611-08:00 avvcbimage Info <40654>: isExitOK()=0

2019-03-07T11:38:09.611-08:00 avvcbimage Info <17823>: Body- abortrecommended(f)

2019-03-07T11:38:09.613-08:00 avvcbimage Info <19660>: targetlist contains <path backup="true" name="[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk" diskCapacity="375809638400" />

2019-03-07T11:38:09.613-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimage.cmd

2019-03-07T11:38:09.613-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd

2019-03-07T11:38:09.613-08:00 avvcbimage Info <7084>: target[0]=[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk

2019-03-07T11:38:09.613-08:00 avvcbimage Info <40658>: vmparams (vcsa01.lntmh.com)

2019-03-07T11:38:09.613-08:00 avvcbimage Info <40654>: isExitOK()=0

2019-03-07T11:38:09.628-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:09.628-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:09.657-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:09.746-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:09.746-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:09.772-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:09.773-08:00 avvcbimage Info <16041>: VDDK:OBJLIB-LIB: Objlib initialized.

2019-03-07T11:38:09.773-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Attempting to locate advanced transport module in "/usr/lib/vmware-vix-disklib".

2019-03-07T11:38:09.966-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Advanced transport plugin /usr/lib/vmware-vix-disklib/lib64/libdiskLibPlugin.so was successfully loaded into vixDiskLib.

2019-03-07T11:38:09.966-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Enabling advanced transport modes.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Initialize transport modes.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:2019-03-07T11:38:09.967+08:00 info -[7F239E879700] [Originator@6876 sub=vm:DictionaryLoad: Cannot open file "/etc/vmware/vsphereFeatures/vsphereFeatures.cfg] : No such file or directory.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:2019-03-07T11:38:09.967+08:00 info -[7F239E879700] [Originator@6876 sub=vm:[msg.dictionary.load.openFailed] Cannot open file "/etc/vmware/vsphereFeatures/vsphereFeatures.cfg] : No such file or directory.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:2019-03-07T11:38:09.967+08:00 info -[7F239E879700] [Originator@6876 sub=vm:FeatureStateLib: Error while loading feature config file: /etc/vmware/vsphereFeatures/vsphereFeatures.cfg]  using default feature state values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Available transport modes: file:san:hotadd:nbdssl:nbd.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:VMware VixDiskLib (6.5) Release build-5993564

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/preferences. Using default values.

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: OpenSSL using FIPS_drbg for RAND

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_Init: Initialization is completed.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <9666>: Available transport modes are file:san:hotadd:nbdssl:nbd

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_PrepareForAccess: Prepare to access disk.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Resolve host.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_AllowVMotion: Disable VMotion.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/preferences. Using default values.

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: OpenSSL using FIPS_drbg for RAND

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2019-03-07T11:38:10.549-08:00 avvcbimage Info <17818>: VixDiskLib vMotion reservation successfully enabled by 'vSphere Data Protection'

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16011>: Running cleanup of old backups.

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Cleanup: Remove previous mount points and clean up .

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Resolve host.

2019-03-07T11:38:10.550-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Disconnect: Disconnect.

2019-03-07T11:38:10.550-08:00 avvcbimage Info <16048>: VixDiskLib_Cleanup() found no prior mounts to cleanup.

2019-03-07T11:38:10.562-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:10.562-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:10.587-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:10.620-08:00 avvcbimage Info <0000>: SnapshotManager: initializing at 127.0.0.1:8543, vCenter vcsa01.lntmh.com(administrator@vsphere.local), datacenter(/New Core Business), httpsTimeout_ms(60000), maxDeleteRetries(-1)

2019-03-07T11:38:10.696-08:00 avvcbimage Info <0000>: GET: curl_easy_getinfo succeeded with httpcode(200)

2019-03-07T11:38:10.701-08:00 avvcbimage Info <0000>: AvSnapMgr::getData Succeeded httpCode: 200

2019-03-07T11:38:10.701-08:00 avvcbimage Info <0000>: SnapshotManager version:7.2.80.167

2019-03-07T11:38:10.701-08:00 avvcbimage Info <40642>: Using SnapShot Manager - with fallback to proxy calling vSphere API functions.

2019-03-07T11:38:10.768-08:00 avvcbimage Info <18648>: The snapshot '' could not be removed.

2019-03-07T11:38:10.811-08:00 avvcbimage Info <40751>:  Datastore Macrosan_AutoTier_Lun03

2019-03-07T11:38:10.828-08:00 avvcbimage Info <14664>: no snapshots are present on this VM.

2019-03-07T11:38:10.862-08:00 avvcbimage Info <0000>: (CURL) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:38:10.862-08:00 avvcbimage Info <0000>: (Legacy) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:38:10.862-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:38:10.862-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:38:20.872-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:38:20.872-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:38:30.882-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:38:30.882-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:38:40.894-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:38:40.904-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:38:50.912-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:38:50.932-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:39:00.932-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:39:00.942-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:39:10.942-08:00 avvcbimage Warning <40648>: DataStore/VM Info download failed.

2019-03-07T11:39:10.942-08:00 avvcbimage Warning <0000>: [IMG0016] The datastore from VMX '[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmx' could not be fully inspected.

2019-03-07T11:39:10.964-08:00 avvcbimage Info <0000>: (CURL) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:39:10.964-08:00 avvcbimage Info <0000>: (Legacy) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:39:10.964-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:39:10.964-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:21.007-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:39:21.007-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:31.018-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:39:31.018-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:41.033-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:39:41.033-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:41.078-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:39:51.084-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:39:51.084-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:51.192-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:40:01.193-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:40:01.193-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:40:01.228-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:40:11.229-08:00 avvcbimage Info <0000>: initial attempt at downloading VM file failed, now trying by re-creating the HREF, (CURL) /folder/ZYLWEB01%2fZYLWEB01.vmx?dcPath=%252fNew%2520Core%2520Business&dsName=Macrosan_AutoTier_Lun03, (LEGACY) /folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03.

2019-03-07T11:40:11.229-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:40:11.229-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:40:21.239-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:40:21.239-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:40:31.252-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:40:31.252-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:40:41.263-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:40:41.263-08:00 avvcbimage Info <40756>: Attempting to Download file:/folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03

2019-03-07T11:40:41.278-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:40:51.280-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:40:51.280-08:00 avvcbimage Info <40756>: Attempting to Download file:/folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03

2019-03-07T11:40:51.298-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:41:01.299-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:41:01.299-08:00 avvcbimage Info <40756>: Attempting to Download file:/folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03

2019-03-07T11:41:01.317-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:41:11.317-08:00 avvcbimage Warning <40650>: Download VM .vmx file failed.

2019-03-07T11:41:11.317-08:00 avvcbimage Error <17821>: failed to download vm metadata, try later

2019-03-07T11:41:11.317-08:00 avvcbimage Info <9772>: Starting graceful (staged) termination, failed to download vm metadata (wrap-up stage)

2019-03-07T11:41:11.318-08:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation  or pre/post snapshot script failed

2019-03-07T11:41:11.318-08:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation/pre-script/post-script failed

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40654>: isExitOK()=157

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40659>: snapshot created:false NOMC:false ChangeBlTrackingAvail:true UsingChBl:true, ExitOK:false, cancelled:false, fatal: true

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40654>: isExitOK()=157

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40660>: vcbimage_progress::terminate

2019-03-07T11:41:11.319-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_EndAccess: Disk access completed.

2019-03-07T11:41:11.319-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2019-03-07T11:41:11.319-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Resolve host.

2019-03-07T11:41:11.320-08:00 avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 0, exitcode 157: miscellaneous error

2019-03-07T11:41:11.320-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_AllowVMotion: Enable VMotion.

2019-03-07T11:41:11.704-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2019-03-07T11:41:11.704-08:00 avvcbimage Info <17819>: VixDiskLib vMotion reservation successfully released

--------------------------------------------------------------------------------------------------------

----- END avvcbimage log 2019-03-07 11:41:16 CST  (12 warnings, 3 errors, 0 fatal errors)

--------------------------------------------------------------------------------------------------------      

Hi,

Recently I upgraded to version 6.1.4 and seems to be I began to get all sort of errors. This one I see more often:

09/22/2017 01:12:30: Backup job named "job3" completed.

09/22/2017 01:02:39: Appliance has changed from "Full Access" to "Admin".  Backup functionality is no longer available.

09/22/2017 01:00:30: Backup job named "job3" started.

Checking #dpnctl status:

dpnctl: INFO: gsan status: degraded
all other services are up.

How to get instance to normal state ?

I'm currently using VMWare Infrastructure Client to manage couple of VMs sitting on VMWare ESX server. I don't have access to service console. Can anybody suggest a way to schedule snapshot delete though the infrastructure client? As mentioned ago, I don't have access to service console.

If I mount some virtual mashines in file mode to the backup server the Windows VSS service shuts off:

vcbmounter -h VCENTER -u vcbuser -p xyz -a name:"Win2k3-Server" -r D:\VCBmount\Win2k3-Server-file -t file -m san

So while some virtual mashines are mounted to D:\ I can not create VSS because there is some kind of problem with the service. If I unmount the virtual mashines the VSS service is working again.

--

Windows Event Log:

VSS 12293

Volumeschattenkopie-Dienstfehler: Beim Aufrufen einer Routine auf einem Volumeschattenkopieanbieter "{b5946137-7b9f-4925-af80-51abd60b20d5}" ist ein Fehler aufgetreten. Routinedetails IVssSnapshotProvider::QueryVolumesSupportedForSnapshots(ProviderId,29,...) .

Vorgang:

Von diesem Anbieter unterstützte Volumes abfragen

Kontext:

Anbieter-ID: {b5946137-7b9f-4925-af80-51abd60b20d5}

Snapshotkontext: 29

---

We are using Backup Exec 12.5 (lastet Updates installed) with VMware Consolidated Backup 1.5 Update 2 and the Integration Module for Symantec Backup Exec for Windows Servers.

In Backup Exec the pre command is configured as followed:

"C:\Program Files (x86)\VMware\VMware Consolidated Backup Framework\backupexec\pre-backup.bat" backup_job01 "Win2k3-Server"

The Snapshot will be mounted to d:\VCBmount\

Until here everything is working fine.

Backup Exec now has to backup up the following:

d:\VCBmount\Win2k3-Server\letters\D\*.* /SUBDIR

After backing up those files I always get the following error:

     Sichern- Win2k3-Server - AOFO: Initialisierung fehlgeschlagen: "D:". Advanced Open File Option verwendet: Microsoft Volume Shadow Copy Service (VSS).
                V-79-10000-11226 - VSS Snapshot-Fehler. Der ausgewählte Snapshot-Provider von Microsoft Volume Shadow Copy Service (VSS) hat Folgendes zurückgegeben: "Unerwarteter Anbieterfehler". Stellen Sie sicher, dass alle Anbieterdienste aktiviert sind und gestartet werden können. Ausführliche Angaben finden Sie in der Windows-Ereignisanzeige.

In Backup Exec there is no AOFO Option activated.

I have been trying to export an OVF template using the vSphere Client Version 4.1.0 Build 258902 of a VM from an ESXi server running 4.1.0 Build 260247 using a licensed version of vSphere 4 Standard.  On some of my VMs, I can export them fine.  However, I have a couple that timeout.  For the ones that fail, I get the popup progress dialog that provides esitmates of time, etc., and it proceeds for a time and them just times out.  It gets about 35% done before I get the error "Failed to export Virtual Machine:  The operation timed out".  The time of duration of my last try was about 16.5 minutes.

The image I am having problems with as provisioned storage of 204 GB, and used storage of 10.63 GB.  Guest OS is Ubuntu 10.04.2 64 bit, but I doubt that is the issue.  VM version is 7.  CPU 3 and memory is 4 GB.  I stopped the VM before exporting it, and it does not have any snapshots yet taken of it.

I have noticed a couple other threads asking for help on this topic with no answers, so I have started another thread to hopefully get somebody's notice.  There seem to be a few others out there with this issue.

I would download the files directly via browsing the datastore, but that seems to take a crazy amount of time to do ... literally hours and hours.

Here is a section of the system logs:

<version>657</version>
[        :QuickInf:P:16] 2011-04-15 13:18:52.610  Current Memory Usage (gc/virtual/physical/paged): 21.271016/566.923264/189.149184/161.140736
[viclient:SoapTran:W:21] 2011-04-15 13:18:57.363  Invoke 1339 Finish WaitForUpdates on PropertyCollector:session[5212368b-16bc-8738-4b84-7fb725fe7fef]52855471-0a5a-fa3f-e500-ba80952e0ade [192.168.30.6] - Serial:0.000, Server:899.974
Suppressed: VirtualInfrastructure.Soap.MethodInvocationSoapImpl: The request failed because the remote server '192.168.30.6' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
[viclient:Error   :W:21] 2011-04-15 13:18:57.363  ConnectionError occurred while executing WFU
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server '192.168.30.6' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
   at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
   at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
   at Vmomi.Core.PropertyCollector.WaitForUpdates(String version)
   at VirtualInfrastructure.Updates.PollerDispatcherImpl.ExecuteSingleWFU()
   at VirtualInfrastructure.Updates.PollerDispatcherImpl.PollWaitForUpdates()
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.

   --- End of inner exception stack trace ---

Hello guys,

I'm trying to make arcserv V15 backuping my ESX 4.1 hosts. What I would like is to make backup of VM, not at the operating system level. My environnement is quite simple : 3 Hosts ESX 4.1 (essential licence pack), No SAN, only local datastore + Arcserv 15.

I try to find  some documentation, but I failed to find something really clear. As far as I know, my Arcserv server is "vstorage api" and "vcb" enabled. I cant find out how to link all this together.

If someone has some feedback to provide me on this.

regards,

Raphael.

Hi,

We're currently doing an implementation of a LAN-free backup solution with ESXi 4.1. It's using the IBM TSM storage agents on the physical proxy nodes and the backup/restores are working but we're getting very slow transfer speeds.

We have been trying various options in the client preferences (see below for items from the dsm.opt file) from the client side but it's made no difference. When using the 'sharedmem' option the backup just hangs and does nothing with no entry in the dsmerror logs to point us in the right direction.

Storage agent version - 6.2.1

TSM client version - 6.2.3.1

If anyone has encountered similar problems from an IBM TSM implementation please post any suggestions.

Hi All,

VM console becomes blank after restoring from VDR backup, but I'm able to ping the particular system IP address. Kindly help us resolve this.

Thanks in Advance