V-79-57344-38366 Backup Exec 20.6 12TB VMDK
Hey all, I've finally got all my backups working correctly EXCEPT a legacy drive inside a VMware guest server. I had excluded this single VMDK from the nightly backup job and have set up a single one-time backup of this drive as a seperate job. However I cannot get the one-time job to succeed. The job runs for the entirety of the 11.7TB of data inside that 12TB drive but results in the error I included below. The job takes about 2 days to complete unsuccessfully. Currently the job is setup to use the same storage space as the pre-mentioned nightly backup job of this guest VM's other drives. So I know this isn't a permissions issue. I'm assuming as well, since I simply copied the nightly job and then unselected the drives from that job and added the single 12TB drive that the configuration is likely not the issue. Backup- VMVCB::\\<vmguest>.example.com\VCGuestVm\(DC)ha-datacenter(DC)\vm\[110] VMGUSET-79-57344-38366 - VDDK-Warn: VDDK_PhoneHome: HTTP response error in VddkVacCurlHttpsPost with http status 400 at 1058. VDDK-Warn: VDDK_PhoneHome: VddkVacPushData : Failed to post data to VC/PH at line 1022. VDDK-Warn: VDDK_PhoneHome: VddkVacPushVendorProductData : Failed to push vendor product data at line 1326. VDDK-Warn: VDDK_PhoneHome: VddkVacWriteMember : Empty field to serialize for key edition at line 188. VDDK-Warn: VDDK_PhoneHome: VddkVacPushProductInstanceData : Failed to push product instance data at line 1219. VDDK-Warn: VDDK_PhoneHome: VddkVacPushEnvironmentData : Failed to push env data at line 1136. VDDK-Warn: VDDK_PhoneHome: VddkVacPushSessionData : Failed to push session data at line 1709. VDDK-Warn: VixDiskLib: VixDiskLibIsLegacyConnParams: the instance of VixDiskLibConnectParams is NOT allocated by VixDiskLib_AllocateConnectParams. The new features in 6.7 or later are not supported. VDDK-Warn: HostAgent is not a VirtualCenter. Error 20 at 3710. VDDK-Warn: VDDK_PhoneHome: Invaild transport mode used at line 271 VDDK-Warn: VixDiskLibProvider::NameBasedProvider::Get: Unable to open disk \\UNC\PATH\TO\STORAGE\IMG000027\GUESTVM_1-000002.vmdk, openflags = 4 - VixError 0x3e86. VDDK-Warn: DiskLibProvider_GetDisk: Open failed - index 0. VDDK-Warn: ERROR 2 opening disk 0. VDDK-Warn: VixDiskLibProvider::NameBasedProvider::Get: Unable to open disk 1:\IMG000027\GUESTVM_1-000002.vmdk, openflags = 4 - VixError 0x3e86. The line "The new features in 6.7 or later are not supported.", seems of note as the GUESTVM I'm trying to backup is on a ESXi Server 6.7. But again, that same GUESTVM does backup correctly if I exclude that one 12TB vmdk. My backup exec server is on an older ESXi 5.5 host running a Windows Server 2012R2 guest. The GUESTVM I'm backing up is a Windows Server 2016 install. I notice that in the \\UNC\PATH\TO\STORAGE location when the job starts, it creates 8 GUESTVM_1-000002 vmdk that look to split. The first VMDK reaches 1.98TB and then it starts filling the second. This one ends up around 700GB when the job ends. Please help!
How long can you still verify a Backup after it's original finish?
Hello Guys, I've got Problems with the length of Verifies colliding with new Backups on the next Day. I don't want to cancel them, I just want to know how long the so called "Availability Window" accutally exists. I hope you Guys understand my Problem. Some advice would be lovely.how can you take a backup from mysql /postgresql with backup exec 16
I have backup exec 16 as server on windows machine but all my agents are linux servers ( ubuntu ). I can take backup from whatever directory in the server I normaly take backup from ( /etc - /var/www ) and the backup is successful. but I also have some databases on those servers and i want to take backup from them ( mysql - postgresql ) is it possible to take backup from them with backup exec 16 ?How to use hotadd mode with existing physical BE server?
We have an existing physical BE 20.6 server and would like to use the hotadd transport mode for VMware backups. The NBD transport mode takes too long for our environment. We want to avoid the risks of presenting the LUNs to the BE server for SAN transport. I know we would have to add a virtual BE server. However, its unclear how it would integrate to the existing one. Does anyone have a similar setup? Thanks.
