Attempting to upgrade VDP 6.1 to 6.1.1.  The 6.1.1 ISO is not detected by the appliance in vdp-configure.  I ran the VDP ISO detection patch, which completes successfully, but the upgrade is still not detected.

Is anyone else experiencing this issue?  Where should I be looking to troubleshoot this?  For what it's worth, this VDP is using Data Domain storage.

EDIT: After mounting the upgrade ISO and waiting a few minutes, the output from df -h at the CLI does not show a cdrom/dvd mounted:

Filesystem      Size  Used Avail Use% Mounted on

/dev/sda2       32G      5.8G   25G  20% /

udev               3.9G    148K  3.9G   1% /dev

tmpfs              3.9G    0  3.9G   0% /dev/shm

/dev/sda1       128M   37M   85M  31% /boot

/dev/sda7       1.5G    129M  1.3G  10% /var

/dev/sda9       138G   6.5G  124G   5% /space

/dev/sdb1       256G   4.3G  252G   2% /data01

/dev/sdc1       256G   1.7G  255G   1% /data02

/dev/sdd1       256G   2.4G  254G   1% /data03

Dear all, I have been knocking my VDP about trying to fix it. It had lost data02, and I got that back by running a filecheck discarding the metadata stuff. So, I was then able to gain access to the rollback, but rollback failed.

Now the status looks like this:

root@vdp:~/#: dpnctl status

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: gsan status: up

dpnctl: INFO: MCS status: down.

dpnctl: INFO: Backup scheduler status: down.

dpnctl: INFO: axionfs status: up.

dpnctl: INFO: Maintenance windows scheduler status: enabled.

dpnctl: INFO: Unattended startup status: enabled.

dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

I found this article: Starting the MCS service in VMware vSphere Data Protection 5.1.x fails with the error: gsan rollbacktime does not match … and attempted to run the command specified in there, but it is not successful.

I get this:

root@vdp:~/#: dpnctl start mcs --force_mcs_restore

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: Restoring MCS data...

Permission deniedPermission denied at /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/XML/LibXML.pm line 587.

Could not create file parser context for file "/usr/local/avamar/var/mc/server_data/prefs/mcserver.xml": Permission denied at /usr/local/avamar/lib/MCServer.pm line 128

dpnctl: ERROR: cannot restore MCS data without a password for MCS administrative user id

dpnctl: ERROR: MCS restore did not succeed, so not restarting MCS

dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

So my question is really... How do I specify the password for the MCS administrative user id so that I may force MCS up again?

If I try to start MCS using dpnctl start mcs I get the following:

root@vdp:~/#: dpnctl start mcs

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: Starting MCS...

dpnctl: INFO: To monitor progress, run in another window: tail -f /tmp/dpnctl-mcs-start-output-6153

dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start" - exit status 13

dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

This is what the dpnctl.log looks like:

root@vdp:~/#: tail /usr/local/avamar/var/log/dpnctl.log

2016/06/30-12:50:18 [ "/bin/cat /tmp/dpnctl-get-mcs-status-status-5787 2>&1" exit status = 0 ]

2016/06/30-12:50:18 dpnctl: INFO: "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test" exit status = 13

2016/06/30-12:50:18 rm -f /tmp/dpnctl-get-mcs-status-status-5787 /tmp/dpnctl-get-mcs-status-output-5787

2016/06/30-12:50:18 dpnctl: INFO: "rm -f /tmp/dpnctl-get-mcs-status-status-5787 /tmp/dpnctl-get-mcs-status-output-5787" - exit status 0

2016/06/30-12:50:18 dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

2016/06/30-12:50:18 rm -f /usr/local/avamar/var/dpnctl.lck

2016/06/30-12:50:18 ======= dpnctl 7.1.80-129 (1.139), running as admin, RETURNING at 2016-06-30 14:50:18 CEST =======

2016/06/30-12:50:18 [user "admin"] program (pid 5787) exit status = 1 (error)

2016/06/30-12:50:18 ======= dpnctl 7.1.80-129 (1.139), running as root, ENDING at 2016-06-30 14:50:18 CEST =======

2016/06/30-12:50:18 [user "root"] program (pid 5729) exit status = 1 (error)

Not a lot to work with here... Logfile has absolutely no info that I can understand...

Message was edited by: Ludvig F Aarstad: added more info

Wow, it was as simple as typing su - admin before running the dpnctl start mcs force_mcs_restore command...

Message was edited by: Ludvig F Aarstad: Added solution...

My VDP version is 6.1(based EMC).

VDP Backup schedule is not running, because that appliance state is "admin" status.

"gsan" service was degraded. From the logs I can see it might caused by disk full, but even I cleared all my restore points, disk space won't be reclaimed because appliance status is "admin".

Here are some of my VDP state, anyone can help? Thank you so much.

root@vdp:~/#: dpnctl status

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: gsan status: degraded

dpnctl: INFO: MCS status: up.

dpnctl: INFO: emt status: up.

dpnctl: INFO: Backup scheduler status: up.

dpnctl: INFO: axionfs status: down.

dpnctl: INFO: Maintenance windows scheduler status: enabled.

dpnctl: INFO: Unattended startup status: enabled.

dpnctl: INFO: avinstaller status: up.

dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

root@vdp:~/#:

root@vdp:~/#: status.dpn
Thu Nov  3 13:01:01 KST 2016  [vdp.kj1.netact.skt.com] Thu Nov  3 04:01:01 2016 UTC (Initialized Mon Feb 15 06:27:42 2016 UTC)
Node   IP Address     Version   State   Runlevel  Srvr+Root+User Dis Suspend Load UsedMB Errlen  %Full   Percent Full and Stripe Status by Disk
0.0     38.123.3.89  7.2.80-98  ONLINE fullaccess mhpu+0hpu+0000   1 false   0.30 14872 16371111  32.9%  32%(onl:1166) 32%(onl:1164) 32%(onl:1167)
Srvr+Root+User Modes = migrate + hfswriteable + persistwriteable + useraccntwriteable

System ID: 1455517662@00:50:56:BA:A1:74

All reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu+0hpu+0000)
System-Status: ok
Access-Status: admin

Checkpoint failed with result MSG_ERR_DISKFULL : cp.20161103033244 started Thu Nov  3 12:33:14 2016 ended Thu Nov  3 12:33:14 2016, completed 0 of 3497 stripes
Last GC: finished Thu Nov  3 12:32:44 2016 after 00m 30s >> recovered 0.00 KB (MSG_ERR_DISKFULL)
No hfscheck yet

Maintenance windows scheduler capacity profile is active.
  The maintenance window is currently running.
  Next backup window start time: Thu Nov  3 20:00:00 2016 KST
  Next maintenance window start time: Fri Nov  4 08:00:00 2016 KST
root@vdp:~/#:

root@vdp:~/#: df -h

Filesystem      Size  Used Avail Use% Mounted on

/dev/sda2        32G  6.0G   24G  20% /

udev            7.8G  180K  7.8G   1% /dev

tmpfs           7.8G     0  7.8G   0% /dev/shm

/dev/sda1       128M   37M   85M  31% /boot

/dev/sda7       1.5G  160M  1.3G  12% /var

/dev/sda9       138G   16G  115G  12% /space

/dev/sdg1       512G  499G   14G  98% /data01

/dev/sdh1       512G  497G   16G  98% /data02

/dev/sdi1       512G  499G   14G  98% /data03

root@vdp:~/#:

I think that issue cause are "/data01", "/data02", "/data03" locations.

But that locations have some checkpoint files.

I don't how delete that checkpoint files.

Please, help me. Thank you so much.

Best Regards,

Neal.Choi

Hey guys,

With a fresh VDP 6.1.3 install on top of vSphere 6.5, most backup jobs hang at 92%.  This is not the issue documented in the release notes, and the backups almost never complete. I DID NOT have this issue with VDP 6.1 under vSphere 6.0.

I have tried backing up photon OS machines, centos 6.5 machines, centos 6.6+ machines, and centos 7 machines.  So far the only ones to successfully complete are some of those old centos 6.5 ones.  I'm not sure if the O/S version is a red herring here, or if it's related to some other pattern I just can't identify at the time.

I have tried backing up images with the quiesce option both on and off, and it doesn't seem to make a difference in the result.  The backups hang regardless and are unsuccessful.

I should mention the storage was created along with the appliance and is on VSAN, if that makes any difference, but - this absolutely all worked with VDP 6.1 and vSphere 6.0.

I looked in a failed job's vmimage log in /usr/local/avamarclient/var/ and noticed this at the end:

2017-01-17T04:02:15.693+04:00 avvcbimage Info <9679>: Virtual disk connection to '[vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1.vmdk' has been closed
2017-01-17T04:02:15.693+04:00 avvcbimage Info <19718>: Found Disk from Device Key: '2001'.
2017-01-17T04:02:15.693+04:00 avvcbimage Info <9674>: virtual disk [vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1_1.vmdk will be connected readonly
2017-01-17T04:02:15.693+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_OpenEx: Open a disk.

2017-01-17T04:02:15.693+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1_1.vmdk.

2017-01-17T04:02:16.008+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: Request RandomAccessRO diskKey = 2001, readOnly = 1, openSnapshot = 0.

2017-01-17T04:02:16.094+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2017-01-17T04:02:16.101+04:00 avvcbimage FATAL <5889>: Fatal signal 11 in pid 15065
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  FATAL ERROR: <0001> uapp::handlefatal: Fatal signal 11
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006b93b1
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba127
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba44b
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba53e
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 0000000000628810
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56c90850
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5050193f
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5051c277
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5051c75e
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5052b142
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5052b678
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56ecab73
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56ecb123
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004284bc
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004291f9
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004993c4
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 000000000070ac4c
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56c88806
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e558cd9bd
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  ERROR: <0001> uapp::handlefatal: aborting program pid=15065, sig=11
2017-01-17T04:02:16.103+04:00 avvcbimage FATAL <5890>: handlefatal: Aborting program with code 176, pid=15065, sig=11
2017-01-17T04:02:16.103+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Exit: Unmatched Init calls so far: 1.

2017-01-17T12:00:07.999+04:00 avvcbimage Info <40660>: vcbimage_progress::terminate

the log ends there.

This looks serious to me, but it's hard to figure out where to go from here.

Does anyone have any advice as to how to proceed?

Thanks for any assistan

I am trying to patch my ESXi 6.0.0, 3029758 to patch ESXi600-20171101 but it is producing the error [Errno 28] No space left on device. on which drive does the Update get installed and can I delete the swap file on one of the datastores, called 'OS Store'. I presume the patch gets deployed here but there is a large swap file in here that I am cautious of deleting. Please see attached images.

I am struggling to path this host that another engineer before me left in a mess. Any help will be greatly appreciated.

Hi

I've a few questions about VDP. I have to save more than 150 VMs with VDP, so it's important to backup the vms in less time.

Can someone describe the tasks taken in the backup process? (detailed)

Take a Backup of a VM that was backed up on the 30th October and today is backed up again, the backup takes over 1h 30 minutes. Why so long?

Disk Size: 42 GB

Datastore: 6x Lefthand P4300

Backup Datastore: Synology RS810 (4x WD 2TB 24x7)

Disk Speed Test: 100 MB/s read, 80 MB/s write

should also not be the problem..

the load on the syno isn't very high (look the screenshot).

Does anyone have an Idea why its so slow..?

All Network is Gbit...

Most backup jobs are hanging at 92% completion.  I see some posts about recovery jobs hanging, but nothing about backups.  Logs on this beast are not user frendly so I've got no direction yet.  Any ideas what might be hanging these?

Hi, Please help me here

The VM is running Veeam application it got hung. I was rebooted the VM some time back

It consists of NFS and vSAN. The VM is running on top of stretched cluster on top of CISCO H/W. After rebooting it seems failed to load and throwing error "Unable to enumerate all disks. The file specified is not a virtual disk"

Uploading log file and screenshot something strange I found. Appreciate effort

I was attempting to increase disk size on the primary disk of a VM. I followed instructions to delete all snapshots. After I noticed that the disk type went from Thin provisioned to Thick provisioned. After increasing the disk size in the VM properties I powered on the machine and received multiple errors:

An error was received from the ESX host while powering on VM <NAME>.

Failed to start the virtual machine.

Cannot open the disk '/vmfs/volumes/NUMBER/NAME.vmdk' or one of the snapshot disks it depends on.

The system cannot find the file specified

VMware ESX cannot find the virtual disk "/vmfs/volumes/NUMBER/NAME-000003.vmdk". Verify the path is valid and try again.

Module DiskEarly power on failed.

Cannot open the disk '/vmfs/volumes/NUMBER/NAME_4-000004.vmdk' or one of the snapshot disks it depends on.

The system cannot find the file specified

VMware ESX cannot find the virtual disk "/vmfs/volumes/NUMBER/NAME.vmdk". Verify the path is valid and try again.

I have attempted to follow the instructions to recreate the vmdk file, but have had no success. Is there any other option to get this machine back?

I have recently setup a small new virtual environment.  One of the key features is a vDP backup appliance running on a host at physically separate location, with backups being performed over the network.  This allows for backups that are protected from disasters like fire.

I am trying to backup 3 VMs from one host to this backup appliance, using a single backup job.  Two of them are able to backup fine, but one VM is always erroring out with this error:

VDP: Backup job (Main Backup) failed to backup client Main Server.  Execution error: E10007:Miscellaneous Error.

I haven't been able to find much more of value, except poking around some text logs in the vDP appliance I saw some SSL communications errors in the nfcssl protocol.

I should also add that the VM in question is a Windows Server 2008 R2 standard guest OS.  I have set disk.EnableUUID to false, and I'm using vshadow.exe in a script file to prep the VSS for backup during the snapshot process.  However, one of the other VMs that is successfully backing up is the exact same server OS and configuration, and it is working fine.

Both hosts are Dell servers running ESXi 5.1.

Also, this VM is also the largest of the 3 VMs, with a 1 TB partition with about 100GB utilized.  At one point it had an RDM disk attached, but after reading that can cause problems I have detached it and still get the error.

Thanks in advance for any help!

Brant

Hi,

I have tried VM restore into an ESX(i) Server using vStorage API. But, it fails with "Access to resource settings on the host is restricted to the server(vCenter Server) that is managing it" error. Can  anyone please give me steps to restore VM eventhough the particular ESX(i) Server was connected with vCenter Server or restoring virtual machine via vCenter Server?

Thanks for you help.

Udhaya kumar K.

I have small  environment in which i configured Openfiler as a iSCSI Storage. I configured Vmnic load balancing on vmkernel  ports (Vstroage1 , vstroage2)  attached to on of ESXi.

Please verify is it correct Vmnic load balancing for iSCSI storage ? 

i am receiving  50MB/S backup speed. Can i optimize this backup speed ??? Further i am using Veam 7 which is running inside windows 7 on same esxi Server where my backup machines are located. please guide me.

I accidentally changed permission to DCUI and VPXUSER and now I can't log in to the vSphere .. how can I go back in and switch it to administrator ..

Please help

franq80@gmail.com

Can I attach an external SCSI tape drive to one of my hosts and then add it as a device on a virtual machine.

I want to use backup exec on a virtual machine rather than having to have a separate physical server to attach the tape drive. I realise that I wouln't be able to vmotion the guest but as its only going to be a backup machine I'm happy with that.

Thanks in advance,

Hello,

I try to understand how VDR works.

I configured VDR to backup VMs from Friday at 7pm to Monday at 6am (see attached file 1) (During this time, there are no modifications on these VMs)

And, I customed my number of retention (see attached file 2)

• Number of recent backups to retain : 2
  
• Older backups to retain : 4
  

What mean "Number of recent backups to retain"? (I read the VDR documentation and it's write that VDR do a daily backup, but I don't want to do a daily backup but a weekly one, how can I do that?)

What mean "Older backups to retain" ? (it's the number of backups to keep?)

I would like to backup each VMs once during the week end. But with my configuration, I have a backup each monday, friday, saturday and Sunday.

And, I want to keep 4 backups (1 each week end during 1 month => 4 weeks retention)

Also,

How can I know if VDR do incremental or Full backups?

JF

Attempting to upgrade VDP 6.1 to 6.1.1.  The 6.1.1 ISO is not detected by the appliance in vdp-configure.  I ran the VDP ISO detection patch, which completes successfully, but the upgrade is still not detected.

Is anyone else experiencing this issue?  Where should I be looking to troubleshoot this?  For what it's worth, this VDP is using Data Domain storage.

EDIT: After mounting the upgrade ISO and waiting a few minutes, the output from df -h at the CLI does not show a cdrom/dvd mounted:

Filesystem      Size  Used Avail Use% Mounted on

/dev/sda2       32G      5.8G   25G  20% /

udev               3.9G    148K  3.9G   1% /dev

tmpfs              3.9G    0  3.9G   0% /dev/shm

/dev/sda1       128M   37M   85M  31% /boot

/dev/sda7       1.5G    129M  1.3G  10% /var

/dev/sda9       138G   6.5G  124G   5% /space

/dev/sdb1       256G   4.3G  252G   2% /data01

/dev/sdc1       256G   1.7G  255G   1% /data02

/dev/sdd1       256G   2.4G  254G   1% /data03

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"

Hello all

We are having a lengthy discussion in my company about backups of vPostgres.

We are currently on vSphere 5.5 ion Windows with SQl backend and plan to move to vSphere 6.5 appliance (vCHA) 6.5U1c. We currently rely on SQL to perform our backups which also has transaction logs so vCenter DB is backed up regularly every 15 minutes.

I'd like to have something similar in place for when we move across to vPostgres but my colleague feels a once a day backup of the VM is sufficient and I realise it all boils down to how risk savy you are and also how you see things. I personally feel taking a backup of your database for vCenter (as well as SRM and vROPS when we move to vPostgres for that) is not enough. After all, we can potentially lose a great deal of information in a day including perf stats, permissions changes, VM changes etc. and we would not be in a position to even work out what change took place because I work in a very large organisation with 10 vCenter servers, 3,500 virtual machines, more than 190 hosts and more than 7,000 staff.

I would like to know the opinion out there so I can accept defeat and agree or put a strong argument for more regular backups. One of my remaining tasks is to also ensure Commvault can actually provide what we need as we are currently on v10 with the plan to upgrade to v11 soon. For starters, CommVault v10  is not particularly good at restoring files for system state although I realise this is another topic altogether.

Also, what systems are people actually to back things up? There is a KB that VMWare provides but having spoken to them they told me sysAdmin is the way to go. A general level ticket was logged but the support was not too good.

Also, what about scheduled backups for the external PSCs? We will have two at each site and I realize this is can also be backed up manually but scheduling backups is not so easy if you were previously on Windows and not familiar with Cron etc.I realize we have resiliency and with a load balancer this can be be automated but backups are still important.

Any feedback appreciated.

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)

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

Hello everyone!

I am looking for backup solutions for my company.

Right now i'm using a small Synology NAS with 4TB - that we already have - to test the Active Backup for Business from them.

The problem is: I can only create tasks and backup VMs that are not running, and we have many VMs running that we cannot turn off.

Does anyone know if it's possible to backup VM while they are running? Sorry for the "newbie" question, i am new at this, i am looking for this solution as it's a must to have backups and we have none and they don't want to expend money with solutions like Nakivo, Veeam, etc...

Right now we have the vSphere 6.0 Enterprise PLUS Edition.

4 Hosts

4 Storages

200+ VMs* - Around 70 Active VMs

Obs: I've noted that i can only backup using Active Backup for Business if the Datastore which this VM use has no other VM running that use this same Datastore too.

So i get this error:

Thank you very much for your attention,

Hugo Alves