The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
VM Explorer Practitioner Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with HPE VM Explorer

SOLVED
Go to solution
Highlighted
DFranke
Acclaimed Contributor

Problems with HPE VM Explorer

Hello,

I have problems with the HPE VM Explorer.

I want to backup a 200gb vm to a usb-disk.
The size of the USB Drive is 1000 GB, and its free.

So, everytime I want to back the backup
Its transfering data to the usb drive.
But after 1 hour the backup fails with disk full.
But there is 846 GB of data free on the usb-drive.

How can I get my backup working?

7 REPLIES
Sandeep Kumar S
HPE Expert

Re: Problems with HPE VM Explorer

Hello,

Share us the debugs from the VMX server. In the Web Interface, go to "admin" -> "Settings" -> "Support" and click to "Generate New Debug Report". Download the zip file and provide it to us along with the task report.

simultaneously you can log a case with HPE for quick resolution. 

https://softwaresupport.hpe.com/ 

Regards,

Sandeep

DFranke1
Acclaimed Contributor

Re: Problems with HPE VM Explorer

Good morning,

thank you for your respone.

I attached the Debug Report File

DFranke1
Acclaimed Contributor

Re: Problems with HPE VM Explorer

Hello,

what i forget to say is that i opened a case and hp told me that I should post at this forum.

And one of the first test backup was a server 4 with 707 gb of data.

Sandeep Kumar S
HPE Expert
Solution

Re: Problems with HPE VM Explorer

Hello,

Please find the answer below:

1) External HDD:

E:\ - USB-HDD , format: FAT32, type: Fixed, root: , space: 907323277312/999958085632

The disk is formatted with FAT32. This format has limittation of 4 GB. I would recommend to format the disk with NTFS partition. This can be done from command line or from GUI.

2) On 23rd we can see that multiple schedules of same VM "SambaServer" was run in span of 30-60 minutes. This might cause issue if creating snapshots which is still in process and can cause error. You can schedule it to run once the backup of same VM completes.

[6708] 23.06.2016 10:35:14 [1949846] Backup Task () started for VM:'SambaServer' (VMX: 6.1.005.0)

[6780] 23.06.2016 10:56:05 [8965277] Backup Task () started for VM:'SambaServer' (VMX: 6.1.005.0)

[1400] 23.06.2016 11:06:24 [3651301] Backup Task () started for VM:'SambaServer' (VMX: 6.1.005.0)

[2788] 23.06.2016 12:32:38 [9523647] Backup Task () started for VM:'SambaServer' (VMX: 6.1.005.0)

[8760] 23.06.2016 14:24:36 [6616848] Backup Task () started for VM:'SambaServer' (VMX: 6.1.005.0)

[1356] 24.06.2016 08:06:01 [5874000] Backup Task () started for VM:'SambaServer' (VMX: 6.1.005.0)

3) With the below error, we can test this outside VMX and check. During snapshot process with memory option included, we can see timeout issues. This can be due to connectivity issue between ESXi and VMX. 


[1356] 24.06.2016 08:06:09 [5874000] Creating memory snapshot "Memory Snapshot 2016-06-24-080601" on 10.4.2.8(memory=True, quiesce=True)
[1356] 24.06.2016 08:14:48 [ERROR] Exception in the ESX SDK (RetrieveProperties [Task:haTask-6-vim.VirtualMachine.createSnapshot-512268390] properties count 1 (info)): The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
[1356] 24.06.2016 08:14:48 [ERROR] Exception in the ESX SDK (RetrieveProperties 55), retrying in 1sec: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
:
:
[1356] 24.06.2016 08:53:49 [5874000] Memory Snapshot created on VM: 10.4.2.8/SambaServer
[1356] 24.06.2016 08:53:51 [5874000] Checking backup size
[1356] 24.06.2016 08:53:51 [5874000] Backup space needed: 249.153.863.075 bytes
[1356] 24.06.2016 08:53:51 [5874000] Available space: 907.323.277.312 bytes
:
:
[1356] 24.06.2016 08:54:16 [5874000] Copying [Datastore2] SambaServer/SambaServer-Snapshot21.vmsn
[1356] 24.06.2016 09:02:57 [ERROR] : Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

-> Check the backup by unchecking "Include memory dump of the virtual machine (needs additional snapshot)" in the schdule. 

-> If you have VC, perform the same task manually and check if the issue is faced. Take snapshot of VM with memory option and download the VM to the external disk. 

-> Check NW issue between ESX and VMX.

Hope this helps.

Regards,

Sandeep

DFranke1
Acclaimed Contributor

Re: Problems with HPE VM Explorer

Thank you very much.

I am trying to make a backup on another usb dic with NTFs formattedd.

And I hope that this will work.

DFranke1
Acclaimed Contributor

Re: Problems with HPE VM Explorer

Hello eyeryone,

the backup is finished.

It works.

Thank you very much.

Sandeep Kumar S
HPE Expert

Re: Problems with HPE VM Explorer

Hello,

Good to know the issue is resolved now.

Regards,

Sandeep

--------------------------

Please assign Kudos

--------------------------

//Add this to "OnDomLoad" event