8/16/2019 Granular Recovery Issue and Action Plan - Avamar

1/4

I faced some issue in performing this recovery and identified an action plan as well. Please refer to the

summary below.

The requested server was a VM and we were having Image level backup for that and in this case, we had

to perform granular level recovery. In order to perform the recovery, firstly , we have to choose the

server->requested date->dataset->GLR option(the one that is marked in yellow) in the screenshot.

When I did this first, an error was thrown stating that, Failed to generate session handle. I restarted the

VCenter02 services and tried. Subsequently, it worked but retrieving the backup contents from the

Image level backup was taking much time than usual.

Tried many times but no luck. After some research, as suspected, the reason for much time to retrieve

the contents was due to the FLR limitation i.e. when performing any file-level restore, we cannot restore

8/16/2019 Granular Recovery Issue and Action Plan - Avamar

2/4

more than 5,000 folders or files, nor we, can browse more than 14,498 folders or files in the same file-

level restore operation.

Action Taken:

1. Instead of choosing the option, Automatic, while performing the recovery, I chose one particular

proxy i.e. ausi-avmproxy28 in this scenario

2. It will show retrieving contents and wait for a while 

3. Logged on the proxy (ausi-avmproxy28 in this scenario) using putty, go to /tmp. Then we may see the

folders something like MntPnt3D2P0, MntPnt3D1P1. I found the VMDK is actually mounted on the

proxy under the folder /tmp/MntPnt3D2P0. Navigate to the particular path and find the required file. 

8/16/2019 Granular Recovery Issue and Action Plan - Avamar

3/4

 

4. Use WinSCP to connect to the proxy and locate to this folder and download the file, it is more than

50,000 files, which proves my suspect. If it does not reach the limitation, we can just restore fromAvamar GUI.

8/16/2019 Granular Recovery Issue and Action Plan - Avamar

4/4

 

5. The file downloaded was then copied and pasted on the newly created Restored folder of the server.