Quantcast
Channel: VMware Communities : Popular Discussions - Backup & Recovery
Viewing all 64650 articles
Browse latest View live

Veeam backup taking 9 hours on a 2tb backup then disconnecting for 20 minutes at the end

$
0
0

Im using Veeam 8.0 to backup one of my File server VMs    windows server 2008r2   Its about a 2 TB VM and it takes about 9 hours just for an incremental that is only processing about 13 gb of data.    At the end of the backup,  Vsphere tells me its removing snapshot.   it gets to about 99% and then the VM disconnects from the system and it takes about 20 minutes for it to come back online.   I have talked to Veeam and they say its normal for it to do what its doing but not at this length of time and theytold me to go to VMware.    VMware tells me to try the boards for help.

 

anyone have any Idea why its taking this long and disconnecting.

 

thanks

Dave


VDP 6.1 Backup Error & vSphere 5.5

$
0
0

Hi,

 

We received few scheduled backup errors for jobs set up for 'individual disks backup' (x1 hard disk) with the 'fall back to the non-quiesced backup if quiescence fails' option checked.

Error:

"VDP: An unexpected error occurred with the following error code: 10020."

 

Client Log:

server System-serverSystem-1501535800867 Info <0000>: <workorder_finished pid="vmimagew" startUTC="2017-07-10 10:00:00" msgver="1" pidnum="3016" finishUTC="2017-07-10 11:00:00" errorcode="170" wid="server System-server System-1501535800867" errormessage="code 170: completed with errors, client log should be examined" errorrealm="Plugin 3016-vmimagew" />

 

avvcbimage Warning <19733>: vSphere Task failed (quiesce, snapshot error=45): 'An error occurred while saving the snapshot: Failed to quiesce the virtual machine.'.
avvcbimage Error <17775>: Snapshot 'VDP-1500547dfgf4066f0b8d5dfdfd34a5181cf5ffebe' creation for VM '[xxxx] server/server.vmx' task creation encountered a quiesce problem
avvcbimage Warning <0000>: The VM could not be quiesced prior to snapshot creation and this backup will not be used as a base for subsequent CBT backups if successful.
Warning <40711>:     Consider using the pre-freeze and post-thaw scripts to facilitate VM quiescing
avvcbimage Warning <41146>:     This error might caused by the pre-freeze script returning a non-zero error code.

 

Unable to find a fix/or much information RE this, please shed some lights on fix to this issue.

Thank you

VDP backup jobs hung at 92%

$
0
0

stuck jobs.jpg

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?

VDP 6.1.2 appliance can't connect to vCenter after initial configuration

$
0
0

I've deployed VDP 6.1.2 and the configuration went smoothly (test connection to vCenter with proper permissions worked successfully), but after the the appliance rebooted it hung at 70% complete for the VDP:Configure appliance task.  In the /usr/local/avamar/var/vdr/server_logs/vdr-server.log the VDP appliance can't connect to the vCenter server.  Any idea as to how to fix this?  Is there a config file I need to update?

 

2016-08-24 12:30:32,895 INFO  [Thread-7]-vi.ViJavaServiceInstanceProviderImpl: vcenter-ignore-cert ? true

2016-08-24 12:30:33,007 WARN  [Thread-7]-vi.VCenterServiceImpl: No VCenter found in MC root domain

2016-08-24 12:30:33,008 INFO  [Thread-7]-vi.ViJavaServiceInstanceProviderImpl: visdkUrl = https:/sdk

2016-08-24 12:30:33,008 ERROR [Thread-7]-vi.ViJavaServiceInstanceProviderImpl: Failed To Create ViJava ServiceInstance owing to Remote VCenter connection error

java.rmi.RemoteException: VI SDK invoke exception:java.lang.IllegalArgumentException: protocol = https host = null; nested exception is:

        java.lang.IllegalArgumentException: protocol = https host = null

        at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:139)

        at com.vmware.vim25.ws.VimStub.retrieveServiceContent(VimStub.java:2114)

        at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:117)

        at com.vmware.vim25.mo.ServiceInstance.<init>(ServiceInstance.java:95)

        at com.emc.vdp2.common.vi.ViJavaServiceInstanceProviderImpl.createViJavaServiceInstance(ViJavaServiceInstanceProviderImpl.java:297)

        at com.emc.vdp2.common.vi.ViJavaServiceInstanceProviderImpl.createViJavaServiceInstance(ViJavaServiceInstanceProviderImpl.java:159)

        at com.emc.vdp2.common.vi.ViJavaServiceInstanceProviderImpl.createViJavaServiceInstance(ViJavaServiceInstanceProviderImpl.java:104)

        at com.emc.vdp2.common.vi.ViJavaServiceInstanceProviderImpl.createViJavaServiceInstance(ViJavaServiceInstanceProviderImpl.java:96)

        at com.emc.vdp2.common.vi.ViJavaServiceInstanceProviderImpl.getViJavaServiceInstance(ViJavaServiceInstanceProviderImpl.java:74)

        at com.emc.vdp2.common.vi.ViJavaServiceInstanceProviderImpl.waitForViJavaServiceInstance(ViJavaServiceInstanceProviderImpl.java:212)

        at com.emc.vdp2.server.VDRServletLifeCycleListener$1.run(VDRServletLifeCycleListener.java:71)

        at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.IllegalArgumentException: protocol = https host = null

        at sun.net.spi.DefaultProxySelector.select(Unknown Source)

        at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(Unknown Source)

        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)

        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(Unknown Source)

        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source)

        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(Unknown Source)

        at com.vmware.vim25.ws.WSClient.post(WSClient.java:216)

        at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:133)

        ... 11 more

2016-08-24 12:30:33,009 INFO  [Thread-7]-vi.ViJavaServiceInstanceProviderImpl: Retry ViJava ServiceInstance Acquisition In 5 Seconds...

VDP License?

VDP integrity check fails

$
0
0

One of my VDP appliances won't run integrity checks.  When I try to run an integrity check manually I get the following error.

 

Capture.PNG

 

My issue is almost identical to the following post:

http://communities.vmware.com/message/2149800#2149800

 

However I've tried rebooting the vdp and I've checked the service status, and they're all running.  Wierd thing is when I try to run a manual integrity check the Maintenace service stops itself then restarts right before I recieve this error message above.  I also have the following errors every morning in the event log.

 

Capture1.PNG

VMDK file not recognized

$
0
0

I have a vmdk file tfrom an SMVI backup that i am trying to mount on a different server adn wehn i try to add it and point top that datastore location no files show up so i can't restore my files.  The file is quite larre so i can't move it around too much but tried different locatoins with the same results. The file is called...server_1-flat.vmdk.  Is there any reason this file cannot be mounted.  Any help is appreciated.  thanks

VDP appliance is nearly full

$
0
0

Hello.

I have alarm:

 

Warning

VDP: [002] The VDP appliance is nearly full

 

What i can do for fix this problem? Please help me.


Should I update the vmware tools on the VDR appliance?

$
0
0

I was a bit suprised to notice the vmware tools on the VDR app were out of date.

 

1) Should I attempt to update them?

 

2) Has anyone succeeded in updating them?

 

Thanks

Iain

Now that VDR is here...any benefits of continuing with vRanger?

$
0
0

 

So we're upgrading to vSphere and I'm just wondering should I even bother renewing all my vRanger Pro licenses?  Anyone else out there ditch their 3rd party backup's or is there another reason to keep them?

 

 

Anyone else having these VDR issues?

$
0
0

I love the fact that VMware is providing VDR as part of the vSphere package. It's definitely a step in the right direction, albeit I'm still inclined to think this software hasn't been put through the ringer in terms of proper QA. I'm just trying to put out a feeler to see how many others have experienced some of the same issues I'm having.

 

To start, I'm backing up my VMs via a network share on a standalone Windows 2003 server that has a NAS attached to it.

 

Some of the issues I've noticed:

 

1) Backups take an inordinate amount of time. I can understand the first backup, but my VMs don't change very much from day to day. Most of the data being manipulated is located on RDMs are these are backed up using Tivoli, not VDR (I use VDR solely for the OS partitions). Each partition is approximately 25GB, there are 15 VMs and my backup window (10pm - 6pm) isn't sufficient to complete the process.

 

2) Integrity checks for the backups are taking a crazy amount of time and will usually stop due to my window being closed (see point #1)

 

3) I'm getting inconsistent "failures" for certain VMs (the report will simply state that a VM failed to backup, not much else). It also varies per night and not always the same VMs (not exactly sure if this is related to #1 where the window is closing while VDR is executing)

 

4) I had the most difficult time setting up the remote share from the VDR appliance in vSphere. The username and password would never be accepted (even though if I tried the same share with the same user/pass on a Windows machine, it would work fine). I finally narrowed down the problem to the simple fact that the VDR appliance can't handle passwords that have special characters in them (this password had an "@" and a ","). Looking at the console while attempting to mount the share would spit out a CIFS error -22. Changing the password to include only numbers and letters was sufficient to work around this issue.

 

5) Snapshots not being created for no apparent reason and thus failing the VDR process. I'm fully able to do a manual snapshot with or without the memory state, so I'm not sure why VDR can't do it. This issue is very intermittent. I had it often when I first setup VDR, but now it only happens every so often (without any type of consistency).

 

I think that's all I can think about for now..

Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

$
0
0

 

Then i try to backup VM using VDR the following error occured:

 

 

Create virtual machine snapshot

Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

 

 

How can i fix this issue ?

 

 

Please help...thanks.

 

 

VDR backup disk space never decreasing?

$
0
0

I've been testing VDR 1.0.1 for a while now, it works fine for me so far, but there is one possible serious issue I'm pondering about now:

Old restore points are being deleted according to my configured retention policy:

8/6/2009 1:16:37 PM: Executing Reclaiming

8/6/2009 1:16:37 PM: Reclaiming Destination /SCSI-0:1/...

8/6/2009 1:16:54 PM: Deleted restore point 7/30/2009 10:09:35 AM for virtual machine MY_VM1

http://...

8/6/2009 1:19:59 PM: Task completed successfully

8/6/2009 1:19:59 PM: Duration: 00:03:22

 

Seems like everything goes according to plan here, no issue.

However the actual disk space used by VDR never decreases on my VDR box, even though it delted a few dozen restore points already.

Thinking about the way VDR backups work, this actually seems quite natural and logical to me:

VDR creates an initial full backup on the first backup, and then only incremental ones for all subsequent backups. So if you want to restore from a restore point from yesterday, you need to have the data of the initial + all other incremental backups ever made for that VM, regardless of whether you still have the actual restore points of all those incremental backups. That way (by that design), it is impossible for VDR to ever decrease the used disk space, unless you delete the most recent restore point or the whole VM from VDR of course.

This means it should make no difference to the disk space whether your retention policy keeps one or one hundred restore points. If you restore the most recent restore point from any of those policies, VDR still has to process all the data of all previous backups, applying changes one after another as those backups happened.  "Merging" such a block-level disk backup seems impossible to me, or does it really do something like that?

 

Someone please clarify if this theory is applicable, or if am I horribly mistaken here?! if I am in fact mistaken, why is my used disk space not only rising steadily?

VDR problems / anyone actually USING VDR successfully?

$
0
0

I have been trying since vSphere and VDR came out to get some successful backups and rehearsal restores. I am just trying to get backups to be stable for more than a week at least..

 

I have reinstalled the appliance and plugin to the latest version (build 4.0.0-176771-R1.0G68) and appliance version reporting 1.0.1.362.

 

The errors I am receiving in the tasks view after letting VDR run overnight are:

 

-  (vm name) incomplete"

- Trouble writing to destination volume, error -102 ( I/O error)

 

My backup storage is on CIFS. I cannot attach a VMDK, mainly for the reason that I don't want to use my SAN as backup storage! I setup a separate server with over 4TB space specifically designed as storage. If it WILL make a difference I guess I can mount the CIFS on the ESX host which VDR resides and create a VMDK on it. I don't see how this is any different than VDR using the CIFS share directly though...

 

Things I have checked:

 

- The CIFS share is working fine. I have an OS level backup software on some physical machines using it fine for over a month without disconnections

- There is plenty of space on the share (2 shares, 1 has over 600GB free space, the other over 3TB free space...)

- I can manually snapshot the VMs in question just fine and the LUNs over iSCSI have plenty of free space to accommodate the duplicated VM + some more...

- I have tried using the VDR appliance as-is and also upgraded the VDR appliance CentOS to latest 5.3 and kernel using instructions found on the boards here. No difference.

- The VDR appliance can ping the VC server and all the ESX hosts just fine and resolves the hostname of each fine.

 

Any ideas? Is anyone actually successfully using VDR for over a month without issue?

Can use the server configured MSCS as a VCB Proxy Server??

$
0
0

 

Hello all

 

 

Does anyone know if it is ok to use the server,configured as one of MSCS cluster, for VCB proxy server????

 

 

I'd be appreciated for any information!

 

 

Thanks in advance!

 

 


Backup VM with VMwate Data Recovery and snaphot

$
0
0

 

hi all,

 

 

I tried to backup a VM with  VMwate Data Recovery and when I bring to compliance

 

 

first,  data recovery  try to take a snapshot of the VM before backup the VM.  but failed for a VM. (Create virtual machine snapshot

Ms-Main Cannot create a quiesced snapshot because the create snapshot  operation exceeded the time limit for holding off I/O in the frozen

virtual machine.)

 

 

 

 

 

The problem, is that when I take a manual snapshot of this VM with the GUI,it works ! (with the 2 options checked it works: snaphot memory and quiesce file system but without option snaphot memory it don't work in manual)

 

 

  but Data Recovery cannot !  (so I think it doesn't take memory snapshot ) so it failed

 

 

thanks to help me.

 

 

benoit

 

 

ESXi Config Backup

$
0
0

 

While we were waiting for our offical HP SD cards to turn up for our Blades we used some spare SD cards we had knokcing about, now the HP cards have arrived, however I can not see how to backup the current ESXi install to maintain all the network settings, vds etc

 

 

Thanks

 

 

Dave

 

 

vDR (1.1) and backing up to a Network Share

$
0
0

HI

I want to setup vDR to backup to a network share, but wanted to understand what the best practices are for the network share and if it is OK for it to be presented on the Virtual Center Server.

 

Also, if I wanted to copy this network share to tape (for off site storage) is this OK. Anything to be aware off?

 

I have been reading a previous  post and it implied that I need to power of the vDR appliance, to ensure that the dedupe store is not in use ( no integrity checks / backups taking place). Is this the case ?

 

Many Thanks,

vmware data recovery e-mail notification

$
0
0

 

Is there a possibility to send an e-mail after a successful job? I cannot found a configuration about that in data recovery.

 

 

Regards

 

 

Reducing disk space usage of Deduplication Store in VMWare Data Recovery

$
0
0

Hello,

 

Using VDR, we occasionally need to increase the disk size of the Deduplication Store. Before version 1.2 there was no way to find out how disk space was actually used and therefore we could only presume backups took more space. As this is now possible (is shown by selecting the destination on the configuration tab under Home/Solution and Applications/VMware Data Recovery), we’ve discovered the capacity of the disk was much larger than the deduplicated size (347GB dedup of 450GB capacity).

 

 

Last weekend we run again out of disk space on the deduplication store, as there's over 20% of unused capacity this raises the following questions:

1.    Why does VDR run out of disk space?

2.    Is there a way to reclame / shrink /  make smaller /reduce / consolidate … the size of the deduplication store to stop the need of increasing the disk?

3.    Any way to decrease the disk size once point 2 was done?

 

 

 

 

Will someone please enlighten me as to what is happening?

Viewing all 64650 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>