insufficient space to process new snapshots, and jobs start to fail. If Upgrading is really the only solution here than i need a good way to ensure my database is preserved and i can upgrade to 6.1. Backup DR policy will land in the in the remote InfoSphere VDP Appliances Dedup. dpnctl stop Select all Open in new window the results after stopping the services. Type the following at the console prompt, to stop the VDP services. Using username - root, and corresponding password. Open the console using the VMware vSphere Client/Web Client, or connect via SSH. I even check the VM configuration log.xml to make sure that i see backup=true for both disks. Login to the VMware Data Protection appliance. I can restore fine other vm's, but this one is giving me problems even though i checked thoroughly and made sure the disks on this VM are not independent. This is not an option this time since i need this particular VM restored to a backup we have from. Is upgrading absolutely necessary? the last time i tried to upgrade from 5.5 to 6.1 the database and all the backups got corrupt and i ended up having to do a fresh install of 6.1 with a new database! VDP can manage backups to replicate specifying the schedule and the target location. This customer is not willing to spend the money on a better solution at the moment so i am stuck with VDP. Additional application backup and restore support for Microsoft SQL. You keep saying that VDP is a can of worms yadda yadda yadda! i cant do anything about it. If you run into the same problem, please share your experience.But i need to make ABSOLUTELY SURE that my DATABASE and backups are preserved if i do decide to upgrade.Ĭause the whole reason for this thread is because i desperately need to restore this particular VM! I suspect the combination of removing the CDROM mapping from the virtual machine and rebooting the VDP appliance resolved the issue. I decided to try “if all else fails, reboot (the VDP appliance)” and sure enough, that did the trick. I tried the backup job a few more times all resulting in failure. in a SharePlay session, connecting your phone to CarPlay might fail. ![]() As expected, I received 40 rows (five datastores x eight proxies). After driving for 10-15 minutes, the screen magically starts responding to touch. This is because VDP has eight internal proxies. DO: Ensure the ESXi host and the Tintri VMstore is accessible on the network for VDP. Running this command should produce approximately eight rows per datastore. I followed that by opening an SSH session to the appliance – ssh – where 192.168.10.51 is the IP address of my VDP appliance and running the command found in the KB article – echo “select * from proxy_datastore_mapping” | psql mcdb -p 5555 -U admin – which produced the output shown in the figure below. Check the garbled characters and fix them in those xml files and start the scheduler. Add/complete the MCS entry and start the scheduler. ![]() ![]() Garbled characters in above xml configuration files. I tried the backup job again – this did not resolve the issue. MCS entry in one or all of the following files is missing or incomplete: 2. The KB article got me started, but I thought it would be worth a blog post to elaborate a bit and share the resolution I found.Īs suggested in the KB article, I disconnected the virtual CDROM drive from the virtual machine that was causing the error (I had only a single virtual machine in the backup job that was failing). Naturally, I search the VMware Knowledge Base (KB) and located this article: VMware vSphere Data Protection 5.1.x fails to start backup jobs (2037003). Probable cause is the datastore for the virtual machine is not accessible. 180 VMware Data Protection 180 Backup VMs from a VSAN Datastore Using VDP. I ran into an interesting vSphere Data Protection (VDP) error: Error Code 30931: Failed to initiate a backup or restore for a virtual machine. Failure Scenarios 155 Magnetic Disk Failure 156 Flash Device Failure 157 Host.
0 Comments
Leave a Reply. |