Highlighted
dantoch
1 Nickel

FLR Failing on new RDM's

Jump to solution

Hi,

Avamar is  7.0  and vCenter is 5.5.    Backups of one particular server (Win )   have been great  forever with a mix of regular drive letter mounted filesystems and RDM (virtual type)  SAN LUNs.    Image backups and FLR.. no problem.   Recently, two new SAN LUNs  Virtual RDM's (setup exactly the same as the others, I am told)  were added  (1.5 TB and 3.0 TB)  and the backup seems to be capturing them.  The restore GUI initially shows them,  however  if I attempt  FLR  via the Browse for Granular Restore button,  those two drives are no longer shown.  In the Activity log, I do  see  "avvcbimage Warning <6780>, Found unknown Section 'browse-from-catalog' in workorder,  ignoring".   Not sure  if that is pertinent, as it successfully can FLR the older RDMs.  I also see in the log  "avvcbimage Warning <0000> VixDiskLib_PrepareForAccess  returned fault(1) unknown error".    We also did an image backup of just those two vmdk's  from an operator's GUI session... again the bkp succeeded (4.5 TB),  but then, attempting to FLR browse.. it actually showed a Dialog window (Don't have the exact text) something to the affect that it couldn't mount the vmdk..  (Note we did not  see that dialog when the backup contained the entire machine, good RDMs and all..it just never showed the disks/data for the 2 new LUNS after attempting FLR)

Haven't opened a tkt with EMC  yet.. .and  may not be able to as this is AVAMAR 7.0...  It's on a dark site  network that's  disconnected from the world.

Any help is appreciated.

Thx,

0 Kudos
1 Solution

Accepted Solutions
dantoch
1 Nickel

Re: FLR Failing on new RDM's

Jump to solution

Hi,

I am replying to my own post...  as  I just figured it out.   After  revisiting the FLR attempt on the 2nd backup of ONLY the new RDMs,  I noted  the  dialog error message... it  said  "Failed to mount disks.  Verify that the disks on the VM have valid/supported partitions".      That got me asking the right questions to the  Wintel Admins.   That rang a bell.  As it turned out, they DID NOT create the new RDM's exactly the same as the older ones.   Since these new ones were rather large  1.5 and 3 TB's, the used GPT partition types and not the MBR types that all the other existing partitions  were.  Bingo.  So with this version 7.0 of Avamar, it doesn't support that partition type.  They could have rebuilt the RDMs with the MBR partition type (no prod data on there yet) , however they said Microsoft recommends using GPT for anything of decent size.  So  we decided to setup agent based backups,I configured the MCS to allow duplicate client names and setup a backup group and dataset to backup those 2 new mount points.   I cant recall offhand if or at what version Avamar will support those GPT's.. but there is a plan to upgrade the version soon in that environment.

Thx.

0 Kudos
1 Reply
dantoch
1 Nickel

Re: FLR Failing on new RDM's

Jump to solution

Hi,

I am replying to my own post...  as  I just figured it out.   After  revisiting the FLR attempt on the 2nd backup of ONLY the new RDMs,  I noted  the  dialog error message... it  said  "Failed to mount disks.  Verify that the disks on the VM have valid/supported partitions".      That got me asking the right questions to the  Wintel Admins.   That rang a bell.  As it turned out, they DID NOT create the new RDM's exactly the same as the older ones.   Since these new ones were rather large  1.5 and 3 TB's, the used GPT partition types and not the MBR types that all the other existing partitions  were.  Bingo.  So with this version 7.0 of Avamar, it doesn't support that partition type.  They could have rebuilt the RDMs with the MBR partition type (no prod data on there yet) , however they said Microsoft recommends using GPT for anything of decent size.  So  we decided to setup agent based backups,I configured the MCS to allow duplicate client names and setup a backup group and dataset to backup those 2 new mount points.   I cant recall offhand if or at what version Avamar will support those GPT's.. but there is a plan to upgrade the version soon in that environment.

Thx.

0 Kudos