I have vSphere Data Protection 6.1.2.19 backing up a set of VMs on a Image job. This job appears to be attempting SQL Database backups, as I get a cascade of errors in the event log:

Event 12362, VSS- A shadow Copy LUN was not detected in the system and did not arrive.

Event 1, SQLVDI - SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0)

Event 3041, MSSQLSERVER- BACKUP failed to complete the command BACKUP DATABASE model.

Event 18210, MSSQLSERVER- BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device '{D4F45946-222F-4984-B8DC-7943DE4D38E2}1', Operating system error 995(the I/O operation has been aborted because of either a thread exit or an application request.

How can I disable the SQL Backups in a VDP Image backup? I'm handling the SQL backups entirely outside of VDP.

HI,

I am really struggling to get my VDP plugin running in webclient 6.5 after the upgrade.

I Can se the VDP plugin 6.1 under Administration--> plugins, but not on the start page of the web client.

all the services on the VDP are running, I have tried to remove the extensions com.vmware.vdp and tried to re-register the VDp on vCenter bit it does not work. Anybody that can help me with this issue.? I am out of ideas... I am using Winows based vcnter.

HI ,

I am trying to configure Netbackup master server  7.0 to take backup of all virtual machine. I am using EMC Fibrechannel  and vmware 4.0 for VMware

Environemnt.  Now i want to take VM backup by Netbackup.   Please answer below mention.

1.  Do i need to present all the luns to Netbackup master server also to take san free backup of Vmware .

2. How it is possible to do the same thing without presenting all the luns to Master/Backup server.

3. i have 100 VM's and How can i take the agent free full vmbackup.

Whwn I was using VMWare Data Recovery, I used a NAS datastore to store my backups while still having the backup appliance running on my main datastore that contains all my VMs.  Is it possible to do this with VDP?  I see that the appliance already comes with the backup virtual disks already created.  I thought about removing them from the VM, moving them to a different datastore and then re-adding them to the VM.  The 2 TB VDP appiance has about 12 virtual disks (not counting the OS disk).  It would be tedious to move each of the backup virtual disks to an alternative datastore.  Is there a better procddure for doing this?  Should I even do it at all?  Am I stepping outside the bounds of how this appliance was meant to work?

I would appreciate some advice in this manner.

Hello

Since upgrading our environment from 5.0 to 5.1 we are having problems backing up several VM's

We use the Netvault Backup, with the VMware Plugin, to backup our VM's

When a backup job is run overnight, one VM fails, with the following message:

Task to create VM snapshot failed with reason 'An error occurred while quiescing the virtual machine. See the virtual machine's event log for details.'

I check the VM's event log and the following is displayed

The guest OS has reported an error during quiescing. The error code was: 4 The error message was: Quiesce aborted.

The following is what I have tried to fix the problem, all failed:

• Remove and reinstall VMware Tools on the VM approx 5 times in a row
• Remove VMware Tools and reinstall without the VSS option
• Disable VSS backup from within Netvault
• Manual snapshot of the VM will sometimes work and sometimes fail

We have a backup job that runs every night Monday - THursday, which backs up approx 10 VM's, with 1 failing with the error message.

On a Friday night we have 2 backups jobs that run, which backup a total of approx 30 VM's, with 7 VM's failing with the error message

Any ideas how I can fix this problem?  It's been suggested its something to do with Datastore storms but everything was working before the upgrade to 5.1

Thanks in advance

Andrew

Hi,

I'm using the last version of VDP (6.1.1)

I succesfully backup VM but I have problem with other VM under Windows 2008R2

The backup start and stuck at 92%.

I've see on the other discussion but the bug concern older version.... I have no error messages and I don't know where to search.....

Have you an idea to adress this problem ?

Thanks

Hello,

I am trying to upgrade my VDP 6.1 appliance to 6.1.1. The iso is not being detected when mounted so I was going to run the hotfix. However, I cannot upload the hotfix files to my appliance via ssh. I am able to log in to the vdp-configure web portal and the vmware console using the root account. When I try to log in using putty or winscp it is saying access denied.

Also, all the potential solutions I'm finding via google appear to be broken. I get this error when trying to access the vmware kb articles:  1$deletedMessageForViewDocumentPage

Any advice would be appreciated. Thanks in advance.

Hello.

Anyone using replication here ? I'm thinking about replication to to other location, we have VDP 6.1 (not advanced), and, according to docs, there is still a product called  RTI (Replication Target), available only in version 5.8, that does not need an additional license. Could I install free ESXi on remote location, install that RTI and use replication ?

Running VDP evaluation and it works fine when backing up small machines. Larger machines, more then 400 GB takes forever, canceled after a few days. Something to do with the virtual machine itself or something other that might cause this?

On what network should I place the VDP servers, same as VMotion, Mgmt network or Production VLANs?

In my home lab I am attempting to manage proxy throughput by reducing the number of simultaneous backup are restore clients via the vSphere Data Protection Configuration Utility web interface.  The web interface will show that the number has been reduced from 8 to the selected amount, but when I monitor the activity via the mccli utility on the VDP appliance it shows that eight VM backups are running as part of the backup job.  I have not been able to test or replicate this with a clients cluster since we do not currently have any clients running VDP 6.1, and thus I am also unable to open a case on this issue.  Has anyone else seen this type of behavior, or know where in the VDP appliance CLI I might be able to force this setting?

Hi,

I tried to upgrade from 6.1.2.19 to 6.1.3, in order to upgrade vmware to 6.5

It failed, because after upgrade I'm still in 6.1.2 and MCS service is down.

Itried to retart or force retore it, without success.

Here is what I found in log :

2017/01/19-19:47:50 dpnctl: INFO: subsystems to act upon: mcs

2017/01/19-19:47:50 dpnctl: INFO: subsystems not to act upon: maint, cron, firewall, axionfs, sched, avi, emt, gsan

2017/01/19-19:47:50 /bin/touch /var/lock/subsys/zzdpn

2017/01/19-19:47:50 INFO: environment variable USERNAME is undefined or empty

2017/01/19-19:47:50 /usr/bin/ssh-agent /bin/bash -c '/usr/bin/ssh-add /home/dpn/.ssh/dpnid && /tmp/dpnctl-run-self.5310'

2017/01/19-19:47:51 dpnctl: INFO: ======= dpnctl 7.2.80-118 (1.139) RESTARTING at 2017/01/19-20:47:51 CET (UTC +0100), running as admin =======

2017/01/19-19:47:51 dpnctl: INFO: log file time stamps are in UTC; local time is 2017/01/19-20:47:51 CET (UTC +0100)

2017/01/19-19:47:51 dpnctl: INFO: PATH=/opt/emc-tools/bin:/usr/local/avamar/bin:/sbin:/usr/sbin:/usr/local/avamar/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/local/apache/bin:/usr/local/ssl/bin:/opt/vmware/bin

2017/01/19-19:47:51 dpnctl: INFO: Argument list: "--mcs_user=root" "start" "mcs"

2017/01/19-19:47:51 dpnctl: INFO: subsystems to act upon: mcs

2017/01/19-19:47:51 dpnctl: INFO: subsystems not to act upon: maint, cron, firewall, axionfs, sched, avi, emt, gsan

2017/01/19-19:47:51 INFO: environment variable USERNAME is undefined or empty

2017/01/19-19:47:51 [ pid = 5371 ]

2017/01/19-19:47:51 /usr/bin/ssh-add -l

2017/01/19-19:47:51 The agent has no identities.

2017/01/19-19:47:51 INFO: environment variable USERNAME is undefined or empty

2017/01/19-19:47:51 [ pid = 5371 ]

2017/01/19-19:47:51 /usr/bin/ssh-add -l

2017/01/19-19:47:51 The agent has no identities.

2017/01/19-19:47:51 /usr/bin/ssh-add /home/admin/.ssh/dpnid

2017/01/19-19:47:51 Identity added: /home/admin/.ssh/dpnid (/home/admin/.ssh/dpnid)

2017/01/19-19:47:51 [ pid = 5371 ]

2017/01/19-19:47:51 /usr/bin/ssh-add -l

2017/01/19-19:47:51 3072 dc:c8:3e:84:f5:99:88:b7:49:07:3f:b8:8b:ee:be:34 [MD5] /home/admin/.ssh/dpnid (RSA)

2017/01/19-19:47:51 dpnctl: INFO: no update context, so not checking for MCS and EMS restore indication

2017/01/19-19:47:51 gsan status check:

2017/01/19-19:47:51 - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:47:51 server up: idle

2017/01/19-19:47:51 - - - - - - - - - - - - - - - END

2017/01/19-19:47:51 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1

2017/01/19-19:47:53 dpnctl: INFO: "([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1" - exit status 0

2017/01/19-19:47:53 /bin/cat /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:47:53 [ "/bin/cat /tmp/dpnctl-get-mcs-status-output-5371" exit status = 0 ]

2017/01/19-19:47:53 dpnctl: INFO: - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:47:53 INFO: Administrator Server status: down

2017/01/19-19:47:53 dpnctl: INFO: - - - - - - - - - - - - - - - END

2017/01/19-19:47:53 /bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1

2017/01/19-19:47:53 [ "/bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1" exit status = 0 ]

2017/01/19-19:47:53 dpnctl: INFO: "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test" exit status = 2

2017/01/19-19:47:53 rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:47:53 dpnctl: INFO: "rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371" - exit status 0

2017/01/19-19:47:53 rpm -q --quiet connectemc

2017/01/19-19:47:53 dpnctl: INFO: "rpm -q --quiet connectemc" - exit status 1

2017/01/19-19:47:53 gsan status check:

2017/01/19-19:47:53 - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:47:54 server up: idle

2017/01/19-19:47:54 - - - - - - - - - - - - - - - END

2017/01/19-19:47:54 dpnctl: INFO: Starting MCS...

2017/01/19-19:47:54 dpnctl: INFO: [no passthrough options found for program "mcserver.sh" in context "start"]

2017/01/19-19:47:54 dpnctl: INFO: To monitor progress, run in another window: tail -f /tmp/dpnctl-mcs-start-output-5371

2017/01/19-19:47:54 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start ; echo $? >/tmp/dpnctl-mcs-start-status-5371) >/tmp/dpnctl-mcs-start-output-5371 2>&1

2017/01/19-19:48:02 dpnctl: INFO: "([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start ; echo $? >/tmp/dpnctl-mcs-start-status-5371) >/tmp/dpnctl-mcs-start-output-5371 2>&1" - exit status 0

2017/01/19-19:48:02 /bin/cat /tmp/dpnctl-mcs-start-output-5371

2017/01/19-19:48:02 [ "/bin/cat /tmp/dpnctl-mcs-start-output-5371" exit status = 0 ]

2017/01/19-19:48:02 /bin/cat /tmp/dpnctl-mcs-start-status-5371 2>&1

2017/01/19-19:48:02 [ "/bin/cat /tmp/dpnctl-mcs-start-status-5371 2>&1" exit status = 0 ]

2017/01/19-19:48:02 output of "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start":

2017/01/19-19:48:02 - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:48:02 Database server is running...

2017/01/19-19:48:02 INFO: Starting messaging service.

2017/01/19-19:48:02 INFO: Started messaging service.

2017/01/19-19:48:02 === BEGIN === check.mcs (prestart)

2017/01/19-19:48:02 check.mcs                        passed

2017/01/19-19:48:02 === PASS === check.mcs PASSED OVERALL (prestart)

2017/01/19-19:48:02 Starting Administrator Server at: Thu Jan 19 20:47:59 CET 2017

2017/01/19-19:48:02 Starting Administrator Server...

2017/01/19-19:48:02 java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)

2017/01/19-19:48:02 - - - - - - - - - - - - - - - END

2017/01/19-19:48:03 dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start" - exit status 1

2017/01/19-19:48:03 rm -f /tmp/dpnctl-mcs-start-status-5371 /tmp/dpnctl-mcs-start-output-5371

2017/01/19-19:48:03 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1

2017/01/19-19:48:04 dpnctl: INFO: "([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1" - exit status 0

2017/01/19-19:48:04 /bin/cat /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:48:04 [ "/bin/cat /tmp/dpnctl-get-mcs-status-output-5371" exit status = 0 ]

2017/01/19-19:48:04 dpnctl: INFO: - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:48:04 INFO: Administrator Server status: down

2017/01/19-19:48:04 dpnctl: INFO: - - - - - - - - - - - - - - - END

2017/01/19-19:48:04 /bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1

2017/01/19-19:48:04 [ "/bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1" exit status = 0 ]

2017/01/19-19:48:04 dpnctl: INFO: "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test" exit status = 2

2017/01/19-19:48:04 rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:48:04 dpnctl: INFO: "rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371" - exit status 0

2017/01/19-19:48:04 dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

2017/01/19-19:48:04 rm -f /usr/local/avamar/var/dpnctl.lck

2017/01/19-19:48:04 ======= dpnctl 7.2.80-118 (1.139), running as admin, RETURNING at 2017-01-19 20:48:04 CET =======

2017/01/19-19:48:04 [user "admin"] program (pid 5371) exit status = 1 (error)

2017/01/19-19:48:04 ======= dpnctl 7.2.80-118 (1.139), running as root, ENDING at 2017-01-19 20:48:04 CET =======

2017/01/19-19:48:04 [user "root"] program (pid 5310) exit status = 1 (error)

I always see this : INFO: environment variable USERNAME is undefined or empty

I'm able to connect via the web client, but can't even call a rollback.

I also destroyed my snapshot, because at the end of the update process everything seemed to be good.

If someone can help me ! Otherwise I think I will have to delete and reinstall it, loosing my backups...

Hi,

Our VM froze because our ESXi datastore is full. I deleted -.vmsn  for the 1st snapshot file via CLI (using the 'rm' command).

VM is on thick disk and have 2 snapshots. so I still have -flat.vmdk, -delta.vmdk. ( for both snapshots ) and -.vmsn ( only for the 2nd snapshot ).

would it be ok if I delete all the snapshots from snapshot manager? atm we only have 8 GB on datastore and the snapshots file size is around 67GB

Thanks,

Dan

Hi,

I am trying to query the changed blocks of a disk as described in the "designing Backup solutions for for VMware vSphere".

For whatever deviceKey I try I get an "invalid argument" error indicating that the deviceKey is wrong

Steps I do:

+create snapshot

+ wait till snapshot is done

+ try the queryChangedDiskAreas()

How can I get the deviceKey?

Thanks,

Nico

All,

VMware Data Recovery version 1.0.1 was released today and is available from

http://www.vmware.com/download/vsphere/

Note that updates are happening, so the listing on the page may still say version 1.0.0 .  Go ahead and select Download and after accepting the EULA, you will see the new ISO with Build 17677. 

The v1.0.1 release addresses the following

Large Temporary Files Removed as Expected

Data Recovery modifies virtual machines' vmdk files' settings so a snapshot can be created for backup purposes. In the past, after the backup has been created, the vmdk file's settings was sometimes left configured for snapshots even after the backup was complete. This led to these virtual machines being left in snapshot mode while accumulating snapshots that were undetected by vSphere Client. This process has been redesigned so that these temporary files are no longer be left behind. In previous versions of Data Recovery, this issue can be resolved by following the process described in the knowledge base article titled "Delete ddb.delete entries and snapshots left behind by Vmware Data Recovery".

Backups Can Be Completed While Integrity Checks Are Running

Data Recovery can complete backup operations at the same time that an integrity check is running. In the past, when an integrity check was running, backups could not be completed.

Improved Integrity Check Backup Speed

Integrity check has been optimized for faster performance. In the past, comparable integrity checks took longer to complete.

Improved VMotion Licensing Support

Virtual machines can be moved between hosts using VMotion without producing licensing issues. In the past, if a virtual machine was moved between hosts using VMotion, licensing checks sometimes produced errors.

Reduced Data Recovery Backup Appliance Shutdown Time

The Data Recovery Backup appliance now shuts down more quickly than it did before. In the past, the appliance often took 15 minutes to shutdown.

Improved Support for Different Time Zones

In the past, Data Recovery did not consistently handle time zones with positive offsets relative to GMT. For example, Data Recovery could encounter issues with data associated with the Paris time zone, which has an offset of +1, whereas data associated with the New York time zone, which has an offset of -5 was handled as expected. These issues no longer occur.

Data Recovery Supported with Essentials Plus Licenses

Data Recovery is included in Essentials Plus licenses. In the past, using Data Recovery with Essentials Plus licenses failed. Backup jobs created with Essentials Plus licenses failed with the error "License not available to perform operation. Feature hotplug not licensed..."

Integrity Check Optimized to Run During Idle Times

Before running regularly scheduled integrity checks, the Backup Appliance determines if the current time is during a backup window. If the current time is not during a backup window, the integrity check runs. If the current time is during a backup window, the backup appliance checks the backup schedule to determine if there will be a time in the next 24 hours that will not be during a backup window. If there is a time in the next 24 hours that is not during a backup window, the Backup Appliance waits for that time. If there is no time that is not during a backup window in the next 24 hours, the Backup Appliance completes the integrity check.

Hej,

for a client project we are looking for a good backup solution and had a look at VMware Data Recovery. The customer does not have a central storage so we wonder if it makes any sense to use this new product?

Some background you might use: In our setting we have two ESX servers (with local storage) serving five virtual hosts each as well as one physical management / backup server. The hosts run Windows Server 2008, one server has a Lotus Domino database.

We would really appreciate if you could give us some advice on this.

Best, cpb-

Hi,

    I met a problem when I used vcb to backup. The log shows "  Snapshot creation failed: Operation failed since another task is in progress."

   Are there anyone what the problem is and how to fix it?

  The below is the log :

Error: Other error encountered: Snapshot creation failed: Operation failed since another task is in progress.

An error occurred, cleaning up...

Deleted directory E:\VCBBackupRoot\CSGSGPKEXT04

Error VM :'CSGSGPKEXT04' snapshot failed

From: BSM@omckbak1.omcapj.adapps.hp.com "VM-csgsgpkext04-FS-Daily"  Time: 18/08/2009 9:56:17 PM

      Session remote exec script vmwarepreexec.cmd

      on host tkimxcvomc01.omcapj.adapps.hp.com failed. Exit code = 1

From: BSM@omckbak1.omcapj.adapps.hp.com "VM-csgsgpkext04-FS-Daily"  Time: 18/08/2009 9:56:17 PM

      None of the Disk Agents completed successfully.

      Session has failed.

Thanks in advance!

Lan Lan

hi guys

Reading some documentation for vDR

I see this:

The recommended is at most 2 destinations up to 1TB.

so if I want more destinations sice for instance I already have 2 destinations 1TB each.... in that case Do I have to use a 3 party backup software or install another vDR appliance?

is there a limit of 500GB for a deduplicated VMDK.

So if my VM has a VMDK of 800GB and deduplicated is 600GB it won't be backup

my company works with IBM products so they are telling me that after I install vDR they will use Tivoli Storage Manager (TSM)... this means I have to use Share Network as destination since it's the only way to take my VMs out the SAN to tapes

or I am wrong? I mean I can use VMDK o RDM? I am confused because of this

Destination stores can be stored in RDM with either virtual or physical compatibility. If you plan to save the

destination store to tape by taking snapshots, you will want to use RDM with virtual compatibility. Snapshots

cannot be taken with RDM with physical compatibility.

maybe it is especifying that using RDM and planning to backup to tapes you have to use vRDMs but using VMDK there is no problems for tapes

thanks a lot

Is there some easy method to enable/disable a specific backup job within vDR without having to edit each backup job and modifying the "Backup Window"???  Are there any powerscript commands or vDR console commands to assist with setup, maintenance and management of the vDR environment.  The vDR plugin UI is really lacking many management features.

Thanks!

We have 3 vSphere ESXi servers currently running approximately 40 VMs. They are currently being backed up using VDR which is doing a good job for us in all but 1 respect - it's not providing application consistent SQL backups on our 3 SQL servers.

To get around the problem our SD/DBA guys are running SQL backups to an additional vmdk attached to the SQL servers and VDR is backing up this vmdk only on the SQL servers. They are running a full SQL backup every night and transaction log backups every 15 minutes and say they can restore to any point in time using the log backups.

Although we're confident we can restore from any db corruption or DR situation, it would involve 2 separate teams and 2 separate restore procedures. Ideally we'd like to implement a single backup and recovery solution that will back up all our VMs, including transactionally consistent SQL backups so that we could relieve the SD/DBA guys of all backup and restore responsibilities.

We would need restore points on our SQL servers every 15 minutes to replicate the point in time restores we can achieve at the moment but without having to restore all the transaction logs.

I have just downloaded Veeam and am about to start a trial but I was wondering if people had experienced the same problem and addressed it with a VM image level backup solution such as Veeam or vRanger. Is it possible to achieve our requirements?

I am using a fully patched Backup Exec server to test the VMware agent for backing up VM's. Here is what is happening:

1. Backup Exec requests a snapshot

2. I can see the snapshot getting created in vCenter

3. Then vCenter mounts the original vmdk file as another disk to the backup server( I have no idea why it does this )

4. Backup exec backs up the vmdk file

5. The backup completes normally in backup exec but in vCenter I see this error:

Remove snapshot

Unable to access file

<unspecified filename> since it

is locked

I have the backup exec RAWS installed on the VM. Anyone else run into this? Its pretty maddening and Symantec says they will not give support on trialware.