Hi, I do have the need to perform some "powered off" backups using Veeam (or any other software for the matter).

The "Powered off" backups would be performed like once a Qtr and I was looking if I can find a way to schedule the entire process but I have met a problem and need some kind advise.

Software:

- ESXi 5.1.0 1743533 with vCenter 5.1 (I do not know exact version)

- Veeam 7.0.0.871

Proposed task

1. Shutting down VMs (Running Windows 2008 & Windows 2012)

- To run 30 min before scheduled backup job

- Rather straightforward as shutdown can be scheduled via Windows or even viClient

2. Backup VMs

- run scheduled VM backup

- run scheduled Backup copy to tape (optional, can run almost anytime later)

- Run script to boot up VM

The problem

The problem now is that most backup software have the function to run scripts or batch files after the backup completes.

Can someone kindly guide me how to write a "DOS" batch file to boot up a Virtual Machine

Alternative

The only alternative that I have tried is to use vCenter to schedule a VM "power up" time. But if the backup exceeds the timing, I may not have a "powered down" VM backup copy.

Please kindly advise

Hi,

I use VDP 6 to back up 30+ VMs. I have a full vCloud Suite deployed that includes vRops. What I would like to accomplish is to get the info about failed backups in vRops. I wasn't able to find a way to do that. Is email the only option of alerting about failed backups?

Thanks

KH

Hello,

I am attempting to set up a Hortonworks sandbox on our VSphere 5.5 lab environment.  We have deployed many times before and have had various problems, but this is a new one to me.

After selecting the OVA file from my local disk within the File/Deploy OVF Template wizard, and selecting where to store the VM (we use SAN), it errors out after I click "Finish" with the error "Failed to Deploy OVF package: A general system error occurred: Failed to write to C:\ProgramData\VMware\VMware VirtualCenter\journal\1433426209.11: Error writing file.  There is not enough space on the disk."

I don't know why it is trying to write a journal file to my local workstation, but at any rate the path referenced in the error did not exist.  I tried creating those folders but the same error was returned.

Note that this is a 5.41 GB OVA file and the local disk on my workstation has 244 GB free.

I then tried adding additional permissions (Users did not have Write) but it still threw the error.  I noticed that the file properties page for the OVA showed it as blocked since it came from a different computer so I unblocked it, but again had no luck with the deploy...same error.

I assume that the path is written during the conversion of a VM at Hortonworks to an OVA (Export?) but I have no idea how, or even if I could change it.  Or even if changing the path would help.

Has anyone else run into this issue and is there a work-around that you can provide?

Thanks is advance for any help,

Rick

I replaced old VDP 6.0.2 instances with the new VDP 6.1.

The actual backups seem to be working correctly, but I had 2 VDP instances replicating to an offsite VDP instance.

I am trying to re-set up the replication (all instances are now on 6.1), but when I try authenticating with the remote instance, I keep getting an error message saying "Authentication failed. Modify destination network settings, username, password, or path and then click "Verify Authentication" to verify authentication again."

I tried both the repluser and root users, where I got the same error.

Any ideas?

Hello,

After a Storage VMotion of the VDP appliance, it became unresponsive. I'm not able to manage it through vCenter nor its web interface. I guess it's something related to its internal proxy.

When I try to enable it, it fails. I've already rebooted the VDP appliance and the VCSA. Also, I've checked via CLI the health of the VDP services and the backup data. Seems fine.

I've also tried to unregister VDP VM and register again. I need help

My environment:

ESXi 6.0 U2

VCSA 6.0 build 3634794

VDP 6.1

Here it comes some screenshots and logs of the issue:

/usr/local/avamar/var/vdr/server_logs/vdr-server.log

2016-06-15 11:48:12,020 ERROR [Timer_CustomValue]-vi.ViJavaAccess: doGetAveVirtualMachine(): Unable to obtain local AVE virtual machine from its IP address [10.12.73.253]
2016-06-15 11:48:12,021 ERROR [Timer_CustomValue]-vi.ViJavaAccess: getAveVirtualMachine(): Unable to obtain local AVE virtual machine. Might be an Avamar physical machine.
2016-06-15 11:48:12,021 ERROR [Timer_CustomValue]-vi.ViJavaAccess: Failure to determine local AVE instance-uuid
2016-06-15 11:48:12,061 ERROR [Timer_CustomValue]-schedule.CustomValueUpdateTimerTask: Could not update the custom values.
java.lang.NullPointerException        at java.lang.String.contains(Unknown Source)        at com.emc.vdp2.schedule.CustomValueUpdateTimerTask.checkAndUpdateAnnotation(CustomValueUpdateTimerTask.java:97)        at com.emc.vdp2.schedule.CustomValueUpdateTimerTask.run(CustomValueUpdateTimerTask.java:72)        at java.util.TimerThread.mainLoop(Unknown Source)        at java.util.TimerThread.run(Unknown Source)
2016-06-15 11:48:16,869 ERROR [Timer_ServiceHealthValidator]-vi.ViJavaAccess: doGetAveVirtualMachine(): Unable to obtain local AVE virtual machine from its IP address [10.12.73.253]
2016-06-15 11:48:16,869 ERROR [Timer_ServiceHealthValidator]-vi.ViJavaAccess: getAveVirtualMachine(): Unable to obtain local AVE virtual machine. Might be an Avamar physical machine.
2016-06-15 11:48:16,869 ERROR [Timer_ServiceHealthValidator]-schedule.AlarmCheckTimerTask: Failed to get aveVM. aveVM is null
2016-06-15 11:48:16,869 INFO  [Timer_ServiceHealthValidator]-schedule.ServiceHealthValidatorTimerTask: Starting Service Health Check on Wed Jun 15 11:48:16 BRT 2016
2016-06-15 11:48:16,878 INFO  [Timer_retireVM]-schedule.RetireVirtualMachineTask: Searching for virtual machine registrations to retire...
2016-06-15 11:48:16,879 ERROR [Timer_HFSValidator]-vi.ViJavaAccess: doGetAveVirtualMachine(): Unable to obtain local AVE virtual machine from its IP address [10.12.73.253]
2016-06-15 11:48:16,879 ERROR [Timer_HFSValidator]-vi.ViJavaAccess: getAveVirtualMachine(): Unable to obtain local AVE virtual machine. Might be an Avamar physical machine.
2016-06-15 11:48:16,880 ERROR [Timer_HFSValidator]-schedule.AlarmCheckTimerTask: Failed to get aveVM. aveVM is null
2016-06-15 11:48:17,136 INFO  [Timer_retireVM]-connection.Mcsdk10StubManager: ServiceInstanceMoref desc=Service Id: urn:uuid:08FCE6D79ECB43283E1466002109508 name=urn:uuid:08FCE6D79ECB43283E1466002109508 value=SERVICE
2016-06-15 11:48:17,186 INFO  [Timer_retireVM]-connection.McAccessManager: Creating new mcsdk stub handler for connection key: [1151234205, Service Id: urn:uuid:08FCE6D79ECB43283E1466002109508] on Thread: [Timer_retireVM]
2016-06-15 11:48:17,240 INFO  [Timer_HFSValidator]-schedule.HFSValidatorTimerTask: HFS ValidRangeHours 48
2016-06-15 11:48:17,240 INFO  [Timer_HFSValidator]-schedule.HFSValidatorTimerTask: Last validated checkpoint happended on Tue Jun 14 15:06:25 BRT 2016
2016-06-15 11:48:17,360 INFO  [Timer_ServiceHealthValidator]-schedule.ServiceHealthValidatorTimerTask: Internal proxy configured?true
2016-06-15 11:48:17,360 INFO  [Timer_ServiceHealthValidator]-services.BaseCLI: GsanCLI: Updating service state.
2016-06-15 11:48:18,421 INFO  [GsanCLI-update]-services.BaseCLI$4: GsanCLI-update: State update complete. New state: running
2016-06-15 11:48:18,421 INFO  [Timer_ServiceHealthValidator]-services.BaseCLI: McsCLI: Updating service state.
2016-06-15 11:48:18,441 INFO  [McsCLI-update]-service.AdapterUtils: MCS Web Services URL: https://vdp6.epl.gov.br:9443/services/mcService  MCUserId="MCUser"
2016-06-15 11:48:18,632 INFO  [McsCLI-update]-connection.Mcsdk10StubManager: ServiceInstanceMoref desc=Service Id: urn:uuid:08FCE6D79ECB43283E1466002111165 name=urn:uuid:08FCE6D79ECB43283E1466002111165 value=SERVICE
2016-06-15 11:48:18,650 INFO  [McsCLI-update]-connection.McAccessManager: Creating new mcsdk stub handler for connection key: [1151234205, Service Id: urn:uuid:08FCE6D79ECB43283E1466002111165] on Thread: [McsCLI-update]
2016-06-15 11:48:18,699 INFO  [McsCLI-update]-services.McsCLI: MC Connection with Key: [McConnectionKey URI: https://vdp6.epl.gov.br:9443/services/mcsdk10 Username: MCUser Locale: en_US mcDomain: / trustAllSSLCerts: true productName: VDP] isConnected: [true]

I'm having a constant problem with backup solutions firing snapshots and sometimes not deleting them.  From what I've read, this is a problem for a lot of people.  I first noticed this when testing VDR; however, I've had the same problem with vRanger and Veeam.  I was curious if there was a way that I could setup an automatic or scheduled task to delete all snapshots?  I can alway putty in to the volume and removesnapshots, but is there a simple way to do this across all volumes?  I don't see a problem with this as long as my backups have completed.  Let me know otherwise and thanks again!

We get the following error when trying to recover a VADP image level backup for a virtual machine which has been protected using SRM:

Invalid or unsupported virtual machine configuration.

vSphere Replication does not support changing the length of a replicated disk.

We have SRM protection configured between two sites, but also have an isolated third site used for DR testing in which I need to restore the SRM protected machines. This site is a vanilla install of vCenter and 3 vSphere hosts only. I can recover VADP backups for non SRM protected VM's fine, however, when trying to recover a VM that was being protected using SRM in the production site I get the error.

We are running vSphere 5.0.1 and using EMC Networker 7.6 SP4 for backup and recovery.

I've raised a call with VMware but they seem unsure. Has anyone seen this issue before?

Thanks.

Pete.

Hi

I had some backups fail last night and on 4 VMs I can see a snapshot that the VDP appliance made during the backup but was unable to remove automatically. (I assume)

Since these are some pretty critical servers I want to make sure that I can simply delete them using the snapshot manager without it impacting the running VMs in some way.

One of the reasons I want to be absolutely sure is that the view in the snapshot manager seems a bit odd. (See Attached images)

Shouldn't the snapshot be above the "You are here"? This it what it looks like on 3 of the VMs.

On the fourth it looks like this:

Any advice will be greatly appreciated.

Hi,

I've been struggling with VDP for a couple of days now.

Here's the setup:

• vCenter appliance 5.5 U2
• 1 VDP 5.5.6
• 1 VDP 5.8

The VDP 5.5.6 is there since a long time ago, it's running fine and I can manage it no problem in the vCenter Web Client.

But, cannot see the "vSphere Data Protection 5.8" option. Therefor I cannot manage the VDP 5.8.

The VDP 5.8 is a fresh install. I've tried registering it using three different users and it doesn't seems to do the trick.

vsphere.local\Administrator

vsphere.local\VDPAdmin (This is a user that I created for the purpose)

MyDomain\VDPAdmin (This is an AD account in my domain. Of course MyDomain is not the real domain name )

All three accounts had permissions defined at the root level of the vCenter as administrators.

Each time it registered successfully. I've rebooted both vCenter and VDP appliance numerous times.

Any help would be appreciated.

Thanks.

I have deployed a second VDP appliance v6.1 in a DR site and want to use it as a replication target. I have noticed that the appliance is not pushing hard and is not sending a lot of data through the link. The replication is happening on the weekend when no one is using the link between the sites and we have 1Gb connection between the two sites. I reached out to our network guy and i asked him to monitor the traffic between the two appliances, He told me that we have enough bandwidth, but looks like the appliance is not pushing hard enough or the appliance is not sending a lot of data through the link. He mentioned something like 1Mb/s as a transfer rate. The replication job starts then stuck on 92% in the source site and 98% in the distention site and the replication task fails if it took it more than 24 hours.

Any one had the same issue? Is there a limitation set on the appliance or a configuration file that we can modify to make it send more data than 1Mb/s ?

Symptoms:

in vmware VDP 5.5/6.0/6.1, every scheduled backup job fails with error 10014

Cause:

the scheduled job does not match with retention policies

!

Solution:

the retention policies have to match with the frequency set in the scheduled job.

for example, if you want to set a job with daily schedule, you must set at least one day in retention policy panel (Item "this Schedule:", field "Daily for:")

I need to remove some damaged restore points, but what do i need to do after i mark them for delete,  i.e. how do i delete them or run a manual reclaim job?

also.

what is the ramification to restore points that exist after the damaged restore point, since backups are incrementals, how can i restore from anything post the dmg'd restore point since it would be missing some information?

Dear Team,

We want to transfer one Virtual Machine image from one site to second site, without effecting Source VM. want to know following 2 methods will work ....

Method 1

1) Take clone of Source VM

2) Copy new cloned vm from vmfs datastore to external HDD

3) ship the external hdd to second site

4) Connect external hdd on vcenter converter server

5) restored on any ESX host

or

Method 2

1) Take image backup of Source VM

2) manually copy image backup folder from VCB server to external HDD

3) ship the external hdd to second site

4) Connect external hdd on vcenter converter server

5) restored on any ESX host

want to know which option will be the best or any other options are available to do the needful.

regards

Mr VMware

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

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...

Ive got the basic version of VDP running at three sites (Vsphere 5.5, VMware vCenter Server 5.5.0b, VCB 5.5). Without fail, after a moth or two, its quits running. Vsphere then gives four or more warnings like this:

• The ESX Host License does not permit usage of VDP and the 60 day evaluation period has ended.
• Start Core services using the vSphere Data Protection Configuration Utility.
• Start Backup Scheduler using the vSphere Data Protection Configuration Utility.
• From the Configuration tab of the vSphere Data Protection user interface, click the All Actions icon and select 'Run integrity check'.

If I open the vdp-configure window, I have to manually start: core services, maintenance services, backup scheduler. Once I restart those services, it runs for a while. Then I reboot and nothing restarts unless I manually restart (the errors above pop up). In frustration, each time, I've just removed the install of VCB and made a new one.

Help!

Thanks!

Arch

new vdp 5.5 appliance 1TB connected to a vcenter 5.5 appliance

configured a dozen or so backups that are working.

have 3 vm's that get

"An unexpected error occurred with the following error code: 10058"

the three vm's are windows 2008 servers.

running job manually or scheduled get the same error

google does not come up with any matches nor does this community have mention of the error code.

any ideas?

Hi, It seems that Storage DRS isn't detecting the vR replicas on the target site. I have an alarm of datastore usage that is above 85% and SDRS does nothing. I'm using vR 6.1 and replications are working as normal. In the docs is said to "register the Sphere Replication appliance with the SSO service to enable the communication between Storage DRS and the Sphere Replication Management server" but I've already done that. Any help appreciated..

I'm getting the failed to remove for one VM in the reports section.  Happened last night on the scheduled BU, and this morning when I did an "on demand" BU.

This particular job has three servers - the failed one is VCenter.

However -

I watched it in VCenter take and remove the snapshot this morning - it's definitely not there.  Not snapshot file in datastore browser or snapshot manager.

I have an image to restore from last night and this morning.

Shows as a failure in the backup tab.

Shows as out of date in the details.

Hi,

We have a problem since we upgrade to ESXI 6.0

Many Backups have these error in Veeam : invalid CBT data

After search i find a kb in vmware : VMware KB: Backing up a virtual machine with Changed Block Tracking (CBT) enabled fails after upgrading to or instal…

And i install the good patch yesterday.

But this night we have the same problem and my question is :

Do that backup need to turn one time after patch with error forautomatically reset the CBT?

thank you for your help.