Unsolved
This post is more than 5 years old
1 Rookie
•
55 Posts
0
1625
May 31st, 2016 09:00
Slow vm image FLR restore. Disable vm image FLR encryption?
Is there a way to disable encryption while restoring data coming from a Data Domain when using the VM Image FLR restore option? The only option available is "Restore Access Control List (ACL)". Is there an attribute I can specify instead?
I am trying to restore a 22GB folder using the FLR option, and so far after 15 minutes about 800MB has been restored. I am wondering if encryption is causing the slowness and was hoping to disable encryption to see.
No Events found!
ionthegeek
2 Intern
•
2K Posts
1
May 31st, 2016 09:00
FLR is slow, especially for large or numerous files. The problem is unlikely to be related to encryption.
Since this is DD, I'd recommend using instant access as a workaround.
Anonymous User
1 Rookie
•
55 Posts
0
June 1st, 2016 06:00
yea we ended up starting an image restore of the whole vm but for some reason the image restore is extremely slow as well. the restore has been running over 16 hours and only has 111GB out of 165GB completed. Looking at the cpu of the image proxy, at first the usage was high and the restore was running good. Then cpu just drops off and here we are.
I have looked at everything that I could think of and researched, I guess I am going to let it finish and collect the logs and open a case.
I forgot about the ability to mount the vmdk since version 7.1, I am going to look at that for sure.
Anonymous User
1 Rookie
•
55 Posts
0
June 1st, 2016 10:00
I have found out why the image restore is taking so long. It looks like after installing: vsphere update 5.5 update 3b disables sslv3: http://pubs.vmware.com/Release_Notes/en/vsphere/55/vsphere-vcenter-server-55u3b-release-notes.html
On one of our vm clusters we had this patch installed, we had not had a chance to install on the other. On the cluster we did not have the patch installed, restores were running great. We installed the patch, now the restores are running slow.
The restore is unable to take advantage of the advanced transport modes because the session is unable to connect to vcenter to determine the transport mode to use.
2016-06-01 09:46:44 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.
2016-06-01 09:46:44 avvcbimage Info <16041>: VDDK:2016-06-01T09:46:44.628-05:00 [7FD150E7A700 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to ; cnx: (null), error: N7Vmacore3Ssl12SSLExceptionE(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)
2016-06-01 09:46:44 avvcbimage Info <16041>: VDDK:2016-06-01T09:46:44.631-05:00 [7FD150EBB700 error 'HttpConnectionPool-000000'] [ConnectComplete] Connect failed to ; cnx: (null), error: N7Vmacore3Ssl12SSLExceptionE(SSL Exception: error:140000DB:SSL routines:SSL routines:short read)
2016-06-01 09:46:44 avvcbimage Info <16041>: VDDK:2016-06-01T09:46:44.631-05:00 [7FD15BFE2700 error 'Default'] Cannot use advanced transport modes for vcenterhostname/moref=vm-92501/snapshot-92502: Other error encountered: SSL Exception: error:140000DB:SSL routines:SSL routines:short read.
2016-06-01 09:46:44 avvcbimage Info <16041>: VDDK:VixDiskLib: Advanced transport modes not available for opening moref=vm-92501.
Not all vcenter communication is broke, only the transport mode function is broke. Removing ssl v3 breaks avamar from being able to determine the transport mode to use.