![]() Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)ĭpnctl: INFO: Backup scheduler status: up.ĭpnctl: INFO: Maintenance windows scheduler status: enabled.ĭpnctl: INFO: Unattended startup status: enabled. Here are some of my VDP state, anyone can help? Thank you so dpnctl status From the logs I can see it might caused by disk full, but even I cleared all my restore points, disk space won't be reclaimed because appliance status is "admin". VDP Backup schedule is not running, because that appliance state is "admin" status. Has anyone else had this issue with VDP 6.1? If so is there some fix to allow "RECENT TASKS" to actually show the same status in the web client and in the viclient ( They are both talking to the same vCenter so why dont they contain the same information?) The exact builds I am using are the followingĪnd before its suggested the run the VDP 6.1.2 ( latest version) I already tried that and that version had bigger issues freezing up and failing so the version I am using seemed to be more stable :-) It is very concerning when VMware is pushing clients to use the web client more and the viclient less yet seems we keep losing functionality. The only way to view the status was to look at the Tasks Console in the web client and there I could also see the job and failed backup but unless you are already looking for the failure you would never have known. Looking in the Alarms section of the web client also fails to show any indication that there was a failed snapshot on one of the backup jobs. Even after a refresh several times in the webclient there is not indication that the job was ever even run, completed, or FAILED under the Recent Tasks section. The ONLY REASON I know this is because the viclient recent tasks showing the progress of the backup job alerted me to the issue. Now what makes this problem an issue is that one of the VM's I had in the backup job failed to create a shapshot. ![]() Running vCenter 6.0 and VDP 6.1 and after launching a backup job ( through the vSphere web client) I can see the job start but only using the viclient's recent tasks ( it DOES NOT show any status or progress through the web client). Question 2: is there any program that can read/recover data from single vmdk files? (tried already Systools VMware recovery but this does not work with files saved from VM to local disk as the support explained to me)Īny help would be highly appreciated as I'm desperate, not very familiar with VMware and the data is crucial for us. Question 1: Is there any way to incorporate the snapshots, jumping from SERVER-000002 to SERVER.vmdk, seeing that the first one is missing? The content ID of the parent virtual diskĭoes not match the corresponding parent content ID in the child.Ĭannot open the disk '/vmfs/volumes/51312345-e57af280-etc-etc//Server-000002.vmdk' or one of the snapshot disks it depends on. ![]() When I try to add the snapshot files (even renaming the 000002 into 000001 or editing the vmdk file (ParentFileNameHint) it always returns an error.Įrror message from esxi502: Reason: The parent virtual disk has been modified since the child was created. I've rebuild the server on another machine from the -flat file (renaming FILENAME inside SERVER.VMX from SERVER-000015 to SERVER) but this brings me back to the initial server configuration (one year ago). However there was no way to save SERVER-00001.vmdk and the associated delta file and then the server failed completely (data corruption after the failure of one disk in the Raid array, etc.) I've managed to download via Data Storage Browser the big SERVER-flat.vmdk file plus 14 out of 15 other file sets containing snapshots. Ok this is the situation (ESXi 5 /VSphere client):
0 Comments
Leave a Reply. |