Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

GRT enabled backup of a 1.6TB vmdk completes successfully, but silently fails during GRT processing in Backup Exec 2010 R3 when targeting a Deduplication Storage Folder

Created: 01 Aug 2012 • Updated: 24 Oct 2012 | 4 comments
dedupe-works's picture
1
Vote
Login to vote
Me Too!I have the same issue
Product(s): Backup Exec, Backup Exec - 2010
Severity: Data threat/Security vulnerability
Status: Public fix available
Tech Note: More Information

GRT fails to locate the VMDK in the deduplication storage folder after successful backup of the large VMDK.

This prevents GRT restores from completing successfully if tested at a later time.

*UPDATE*

This issue is resolved in Backup Exec 2012 Hotfix 194470. (TECH194470).

This issue is resolved in Backup Exec 2010 Hotfix 194471. (TECH194471).

Comments 4 CommentsJump to latest comment

_grimm's picture

I have the same issue but with BUE 2012 (fully patched as of 06/09/12).

This only happens with one server and only one .vmdk of that server, which is 1TB is size.

Restores from the C:\ drive of that server work fine.

This sucks as it is the main file server :-(

0
Login to vote
dedupe-works's picture

_grimm - switch the server to a remote agent based backup until this is addressed.

Regards.

Randey

0
Login to vote
_grimm's picture

I have thanks.

Have you had other reports of this affecting BUE2012 too? I've also noticed that when duplicating this server to tape I receive a success status, but the amount of data processed only equates to the C:\ drive which is 50GB, not the whole VM which would be 1050GB, which confirms that the 1TB .vmdk is not being stored correctly by Puredisk.

Any indication on if/when this may be fixed? I kind of amazed no-one has tried backing up a 1TB+ .vmdk to dedupe before now...

0
Login to vote
dedupe-works's picture

I do have other cases currently with this issue already.

When the fix is released, this post will be updated in conjunction with the tech note describing the issue.

Regards.

Randey

0
Login to vote