Something to do with esg127567? We noticed that each time upu try to restore a big file, each time the size of the file which is restored is different. Best regards
Yes, there is a need. It's not handy to make a guest level backup and an image level backup. Incidently we need to restore a large file, because a image level backup is stored at least a Year, it's very handy to restore a file from the image level backup instead of a second (and same) guest level backup. Best regards
Maybe as workaround. Restore image as a new VM-server, add disk to an existing VM and copy file to the correct place. It looks to work for us. Good luck
The workaround sounds good, but if we need to restore a file for example with ~30GB and we have a VMDK Image file with 500GB, it´s hard to restore the whole VMDK file just to get the needed 30GB file. There is also the need for the necessary disk space, which could cause issues for a few customers.
schallean
1 Rookie
•
43 Posts
0
April 9th, 2013 04:00
This issue has been fixed in Avamar Version 6.1.x and the timeout values have been increased.
Sameer_Khan
121 Posts
0
March 13th, 2012 13:00
There is a hidden flag available to increase timeout. I would recommend contacting support for the same.
schallean
1 Rookie
•
43 Posts
0
March 13th, 2012 14:00
Thanks for that information. Case has already been opened.
But my Question is. Why does it take nearly 60 Minutes for 30GB File and after 60 Minutes were only ~7GB restored???
This is also interessting.
Thanks for support.
Andreas
jpsmeele
4 Posts
0
March 15th, 2012 03:00
Same issues here. Did you already solved this? And how?
Best regards
jpsmeele
4 Posts
0
March 16th, 2012 01:00
Something to do with esg127567? We noticed that each time upu try to restore a big file, each time the size of the file which is restored is different. Best regards
Sameer_Khan
121 Posts
0
March 16th, 2012 05:00
If there is a need to restore large sized individual files, guest level backup is the best option to go for.
jpsmeele
4 Posts
0
March 19th, 2012 06:00
Yes, there is a need. It's not handy to make a guest level backup and an image level backup. Incidently we need to restore a large file, because a image level backup is stored at least a Year, it's very handy to restore a file from the image level backup instead of a second (and same) guest level backup. Best regards
jpsmeele
4 Posts
0
March 20th, 2012 00:00
Maybe as workaround. Restore image as a new VM-server, add disk to an existing VM and copy file to the correct place. It looks to work for us. Good luck
schallean
1 Rookie
•
43 Posts
0
March 22nd, 2012 03:00
The workaround sounds good, but if we need to restore a file for example with ~30GB and we have a VMDK Image file with 500GB, it´s hard to restore the whole VMDK file just to get the needed 30GB file. There is also the need for the necessary disk space, which could cause issues for a few customers.
J_H_
2 Intern
•
498 Posts
0
April 15th, 2013 12:00
schallean - can you give more info on that. I am on 6.1.x and I cannot restore anything large froma vm backup.
I have to restore to a restore vm and cross mount the drive on the original server so we can copy/paste.