Hello,

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

Anyone already done it ?

Thanks

Guy

I am getting vcb errors all of a sudden when all my vm backsups a failing. nothing was changed and I am seeing this in the vcb event log

this is a hotadd backup with the vcb-helper vm. I recreated the VCB-HELPEr vm but still same error. rebooted vcb also.

[2011-02-20 21:41:07.023 'vcbMounter' 1844 error] Error: Could not locate devic

nodes for new disks.

[2011-02-20 21:41:07.023 'vcbMounter' 1844 error] An error occurred, cleaning u

...

any ideas?

Hi,

we use VMware Data Recovery 2.0 to backup our VM's to NAS via NFS. Taget disk was 500 GB VMDK assigned to VDR. Due to decreasing free place I've tried to extend it this way:

1. reboot VDR

2. extend VMDK in vCenter to 800 GB

3. reboot VDR again 'cause disk size remained the same (fdisk -l):

4. delete old partition a add a new partition using all free space (I've did it successfully several times for some Ubuntu/CentOS VMs):

Disk /dev/sdb: 858.9 GB, 858993459200 bytes

103 heads, 8 sectors/track, 2036069 cylinders

Units = cylinders of 824 * 512 = 421888 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1     2036069   838860424   83  Linux

5. but e2fsck failed (as well as attempts to use alternate superblocks):

e2fsck 1.39 (29-May-2006)

Couldn't find ext2 superblock, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct ext2

filesystem.  If the device is valid and it really contains an ext2

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

    e2fsck -b 8193 <device>

6. I've tried to restore original filesystem but number of blocks is different:

Disk /dev/sdb: 858.9 GB, 858993459200 bytes

103 heads, 8 sectors/track, 2036069 cylinders

Units = cylinders of 824 * 512 = 421888 bytes

   Device Boot      Start         End      Blocks   Id  System

/dev/sdb1               1     1272544   524288124   83  Linux

Does VDR use some special formatting?

My questions:

1. What's a right way to extend VMDK? VDR Administration Guide mentions vCenter part only.

2. Any chance to restore filesystem? I've created new VMDK for next backups immediately but I'd be glad to have access to old backups.

Thanks in advance for tips.

I just noticed that the (4) VDP appliances I am testing all stopped sending the Email Summary Report after the Daylight Savings time change on Sunday. the last report was generated Sunday morning at 12:00am. Now all the appliances are reporting this:

VDP: Send email summary report error. The email summary report timer is set to the incorrect hour. It does not match the vdrdb value.

The time this error is generated is 11:00:00pm which is exactly one hour from when it should be running.

I think this is a Daylight Savings time issue but dont know how to address it.

Any help would be greatly appreciated.

RickH

Hi All

I have been using VDP for a few weeks now and it has been running without too many issues. In the last day or so I have seeing backups fail on 2 of my appliances. I would like to know the reason for the failure so I putty to the appliacne and started to look through the logs in /usr/local/avamarclient/var-proxy-x but I am finding it extremely difficult, none of the logs are labeled with the friendly VM names but insteand the log file names use the vCenter machine ID or some such identifier. I was wondering if somone could give some assistance with

1. Easiest way to find the log for a particular VM

2. What are the best logs to look at to ascertain the actual reason for the backup failure

If anyone has any other tips and tricks for interpreting the logs please let me know.

Thanks a lot guys,

Hi all,

I'm trying to use Backup Exec 2010 to perform full/incremental backups of our VM's with GRT enabled.  However, at the end of every job, I get a warning saying that it failed to mount the virtual disk image.  I went into the debug logs, and found the following:

ENGINE:       Status for: 'xxxxxx' updated

BEREMOTE:      VDDK-Log: TicketResolveHostName: Resolving IP address for hostname xxxxx

BEREMOTE:      VDDK-Log: TicketResolveHostName: Resolved to 10.86.8.47.

BEREMOTE:      VDDK-Log: VixDiskLibVim: TicketLogin

BEREMOTE:      VDDK-Warn: VixDiskLibVim: Not licensed to use this function.

BEREMOTE:      VDDK-Log: VixDiskLibVim: TicketLogout

BEREMOTE:      VMDKRemoteImage::Open()  Could not open the disk '[VMStorage2] xxxxx.vmdk' Error Text: 'Host is not licensed for this feature' Error: '16064'

BEREMOTE:      CDiskLayoutImplementation::DisableAutoMount: Disabling AUTOMOUNT

BEREMOTE:      VMwareVirtualSystem::MountDisksUsingVddk() - Enter

BEREMOTE:      VDDK-Warn: Refusing to set temp directory second time 'C:\WINDOWS\TEMP\vmware-SYSTEM' to 'C:\WINDOWS\TEMP\vmware-SYSTEM'.

BEREMOTE:      VDDK-Log: Mntapi_Init Asked - 1.0 Served - 1.0 was successful,TempDirectory: C:\WINDOWS\TEMP\vmware-SYSTEM.

BEREMOTE:      VDDK-Log: TicketResolveHostName: Resolving IP address for hostname xxxxxx

BEREMOTE:      VDDK-Log: TicketResolveHostName: Resolved to 10.86.8.47.

BEREMOTE:      VDDK-Log: VixDiskLibVim: TicketLogin

BEREMOTE:      VDDK-Warn: VixDiskLibVim: Not licensed to use this function.

BEREMOTE:      VDDK-Log: VixDiskLibVim: TicketLogout

BEREMOTE:      VDDK-Warn: VixDiskLibProvider::NameBasedProvider::Get: Unable to open disk xxxxxxx.vmdk, openflags = 4 - VixError 0x3ec0.

BEREMOTE:      VDDK-Warn: DiskLibProvider_GetDisk: Open failed - index 0.

BEREMOTE:      VDDK-Log: Error 2 opening disk 0.

BEREMOTE:      VDDK-Log: VixMntapi: Operation failed with system error: The system cannot find the file specified.

     (2), translated to 4

BEREMOTE:      VMDKRemoteImage::mountDisks()  Could not open the diskset. Error Text: 'A file was not found' Error: '4'

BEREMOTE:      CDiskLayoutImplementation::SetAutoMount: Enabling AUTOMOUNT

BEREMOTE:      VDiskMounter::MountAllDisks:failed VirtualSystem::Initialize()

BEREMOTE:      Error mounting disks (0xe0009741)

BEREMOTE:      IMG_PDI_FSYS::ImgPdiFsys::AttachToDLE (551):

BEREMOTE:      Error mounting disk(s): E_IMG_FS_FAILED_TO_MOUNT_VIRTUAL_DISK (0xe0009741).

BEREMOTE:      CommonMounter::~CommonMounter called

The relevlant lines to me seem to be the ones that indicate that this host is not licensed for this feature.  The other funny thing is that these logs are produced AFTER the vmdk has been completely copied to the backup server.

We're using vSphere Essentials, which includes the vmstorage API's as I recall, any idea what's going on here?

Thanks

Anyone know how to limit the concurrent backups in VDP 5.8? The registerproxy.sh script no longer does this in VDP 5.8.

Here is all the output that is displayed when the registerproxy.sh script is ran.

Here's the article I was using to try and change the # of proxies.

http://onevirtual.wordpress.com/2013/11/20/re-configure-proxies-for-vdp-to-limit-the-number-of-parallel-backups/

Hello together,

we've got a odd problem, from one day to the next, the VDP quit the file level restore service. When I try to start it with the web client, it just doesn't start.Also, I'm unable to download the log files (I/O-Error) over the web interface.

I tried to search for an solution in the web without any result. Does anyone here knows this kind of error or even better the solution?

Thanks in advance for any help.

There are two ways of changing the IP address of a VDP appliance:

1- via vdp-configure web app

2- via VM console (the blue TUI inteface)

The correct one is the 1- option. If you will do it via 2- (like I did ) you'll end up with broken VDP. This method only changes settings on the network interface while it doesn't change avamar settings ... To fix it you'll have to manually edit IP address in the following files:

/etc/hosts

/etc/sysconfig/network/x-ifcfg-eth0.dpnnetutilbgaux_save

/etc/sysconfig/network/x-ifcfg-eth0.dpnnetutilbgaux_orig

/etc/x-hosts.dpnnetutilbgaux_orig

/space/avamar/var/dpnnetutil.xml

/space/avamar/var/probe.xml

After this reboot the appliance and it should be back to normal.

Anyway, this SHOULD be written in "VDP Administration Guide" and/or noticed in some KB ... or even better ... after VDP is initially configured, changing IP address via VDP console (the blue TUI inteface) should be disabled ... hopefully VMware will fix this someday.

Good day,

We are currently using the vdr appliance 1.2.1.1616 in a vmware 4.1.0 Build 491557 environment. We currently have two separate vdr appliances deployed, each with 2 - 1TB backup destinations.  The backup destinations are on a Drobo 800i.  At this time we cannot upgrade to the latest VDP product as it is not supported in our version of vmware [we will be upgrading in the near future, now that our hardware is supported].  I believe that there is a version 2.0 of the vdr appliance, but I cannot locate the OVF file to deploy, and I am not 100% sure that it is even supported in our version of vmware.

Each vdr appliance reports on occassion, and is becoming almost a weekly occurance, that when executing an Integrity Check it fails for specific restore points, and that the backup set [destination] e.g. SCSI-1:0 will be locked until the restore point with the errors are deleted and integrity check successfully completes.  Errors also sometimes reference error -2241

Have tried to clear the restore points, but none are shown in the Restore tab

Have tried steps in KB#1018060 regarding lock files, there are not .lck files found on the destination datastores.  In all the issues with backup jobs/integrity checks/reclaim operations failing, have never found any lock files on any data destination.

Also have tried steps in KB#1020974.  This has worked once, but other times it reports that the destination is clear and finds no errors.

To rectify the situation, have basically "blown" away the appliance and recreated it.  Most recent was to unmount and format the data destination with the issue - not sure if this will be successful or not, as it was just done prior to submitting this discussion.  Will see if the backup job to this data desitnation runs successfully overnight.

Questions:

1.  Have others experienced these type of issues with the vdr appliance?

2.  Any suggestions on how to make this version of the vdr stable?

3.  Does anyone also use the Drobo 800i successfully with their vdr?

Thank you in advance for any suggestions, etc.

Hi,

i just tried the upgrade from VDP 5.5 to 5.6 and it stopped with this error message:

Installation of the package stalled

The installation stalled due to an error. Please use your snapshot to rollback the appliance.

1.) error message is not really helpful

2.) i rolled back and tried a 2nd time, no luck

Anybody a clue where to look for detailed error messages?

Thanks

VDP installation has been failing me ever since. Today, Techsupport pointed out that Windows NFS shares are not supported for storing the VDP virtual drives. Is there a work around for this? My only bulk storage space is on a NAS running Windows Storage Server 2008R2, with an NFS share. Any help would be appreciated. Thank you!

Mark

Hy,

the appliance DP is rel 5.5.1.356, in the log I can see "error: a backup/restore/validate activity did not start within the allotted time", logged after 9 seconds, and no backup is made.

Is there anyone having the same problem?

thanks in advance

Max

1. Al VDP connect the following message appears:

"The most recent request has-been rejected by the VDP Appliance."

refers to NTP settings.

there is a difference of 17 minutes.

2. While setting NTP for my area can not add chile ntp.shoa.cl

3. I can not change the date and time manually with hwclock

4.When modify Yask time with me the following message:

"Can not update the dynamic configuration policy."

Please need help with this problem.

Hi,

i have freed space removing older backup but vdp not releasing space.

my error log:

root@vdp-00:~/#: mccli event show --unack=true

0,23000,CLI command completed successfully.

ID      Date                     Type    Code  Category Severity Domain Summary

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

1667003 2014-07-28 14:29:48 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1666923 2014-07-28 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

1659796 2014-07-28 06:15:37 CEST ERROR   22408 SYSTEM   PROCESS  /      A checkpoint of server data is overdue.

1657176 2014-07-28 03:16:42 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1657174 2014-07-28 03:14:32 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1657077 2014-07-28 03:10:29 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1656836 2014-07-28 02:51:29 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1656152 2014-07-28 02:00:13 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1655727 2014-07-28 01:26:30 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1655507 2014-07-28 00:58:34 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1654226 2014-07-27 23:21:01 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1654224 2014-07-27 23:20:52 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1647646 2014-07-27 14:29:03 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1647573 2014-07-27 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

1635686 2014-07-27 00:47:14 CEST ERROR   22409 SYSTEM   PROCESS  /      A checkpoint validation (hfscheck) of server checkpoint data is overdue.

1633648 2014-07-26 22:27:31 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633647 2014-07-26 22:25:20 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633558 2014-07-26 22:21:28 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633521 2014-07-26 22:19:18 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633342 2014-07-26 22:06:50 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633341 2014-07-26 22:06:42 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632918 2014-07-26 21:38:17 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632774 2014-07-26 21:28:33 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632749 2014-07-26 21:26:23 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632457 2014-07-26 21:07:18 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1629914 2014-07-26 18:15:04 CEST ERROR   22408 SYSTEM   PROCESS  /      A checkpoint of server data is overdue.

1626551 2014-07-26 14:28:52 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1626540 2014-07-26 14:25:24 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1626491 2014-07-26 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

1626183 2014-07-26 14:03:20 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1619232 2014-07-26 06:09:24 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1614592 2014-07-26 00:52:01 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1605944 2014-07-25 14:28:14 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1605913 2014-07-25 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

Can you help please?

Thank You

Hi,

If anyone can help me that would be appreciated. I have setup VDP to backup my VMs individually. Previously my backup used to work but recently, I keep getting the error saying " VDP : A backup/restore/validate activity did not start within the alloted time" in the Tasks. Even trying to perform a "Backup Now" doesn't seem to have any effect. I also did a check on the server logs via ssh in /usr/local/avamar/var/vdr/server_logs/ but nothing seems to show me to the right path.

Hi,

Is there a scripting solution for managing vdp appliance ?

ex : powercli, powershell, avamar ... ?

Hi,

Since i updated to vSphere Data Protection 5.8 the email with the backup report comes completely unformatted, ex:

This is how it was on 5.5 and previous:

Anyone with the same problem? Any fix?

Hi folks.

We have rolled out five VDP appliances to cover around 500VM's over several clusters. I'm not going to lie, VDP has been real pain and I've found it very buggy, but the idea of it working at some point makes me very enthusiastic about getting it to that point. A major issue I am facing at the moment is that while the backups are running relatively OK for most VM's, some of our high IO devices such as Linux Oracle servers, and MSSQL 2008R2 servers are being downed by the backup system.

I had a production MSSQL server freeze for 15 minutes a few days ago while the backups' snapshot was committing itself, this then became responsive again without actually properly going down. This had to be raised as a business affecting incident - so not happy - and yesterday two test Oracle linux boxes freaked out, one rebooted and the other also froze during their backup activities which again wasn't good.

All VMDK's are stored on a NetApp filer accessed through NFS.

I understand these issues are because of either CBT or due to the system using HotAdd which causes the lengthy snapshots. Is this correct? If so - is there a work around to turn off HotAdd for these select VM's, or put them on their own appliance? Or is there another workaround I'm not aware of.

Thanks a lot for any help coming!

Hi,

    I am wondering if anyone can chime in and share some experience how to protect our VMware Infrastructure in the event of Disaster.

The Scenario:

- we have multiple locations ( 2 primary/main sites and 1 aux site) connected to VPLS/VPN between sites w/ 50MBps bandwidth between sites

- in the event of disaster, we'd like to have fail-over capabilities between the primary sites and the aux site will fail over to the primary sites AUTOMATICALLY or MANUALLY.

- when failed over, are there product that can automatically re-IP or re-ROUTE all the host/servers so both client and servers can find each other

- we also would like to have a cloud backup for long term archiving so we can backup/restore our exchange mailbox(es), sql database server, and our VMs

I know I may miss some other important question/scenario, but let's start with that for now.

- Does anyone use or have experience on such solution?

- Does VMware have native support(without using 3rd party) for business continuity and backup/recovery solution?

- I also have done some comparison and soul searching and come up with the following choices: Actifio, Veeam 8.x, Unitrends, Zerto(for the automation), Cisco/Simplivity. Does anyone have any experience on these products?

I'd prefer the least resistance and least cost solution in which I am hoping that VMware have most of the features I am looking for.

Thank you.