3 Zinc

Re: Image backup---- File level restore.

Lets get a clarification of what you mean by mount point.

So you have a dir, and is something mounted on that dir from outside the system or inside the system

Or is it a link pointing to some other place in the server?

we might be able to figure this out of you can give more info on what you know that "mount point" to be.

0 Kudos
3 Silver

Re: Image backup---- File level restore.

Hello J.H.,

Its folder frm NFS mount. As like we add "--forcefs=nfs" to see the mount points in the file system(from avamar admin GUI) , is there any to see the same from VM image backup. (folders while restore.)

0 Kudos
3 Zinc

Re: Re: Image backup---- File level restore.

No you will never be able to see it in an VM backup.

Let me try to explain.

When you have a NFS you are mounting a FS from another server – but the files are NOT on this system.

So you have MyVm

On it you have /mnt On that you have mounted  SourceDir from SourceServer

A df gives you this

SourceServer:/SourceDir 1509949440 1486490344    2%      135    1% /mymount

All this gives you is a wormhole over the network to SourceServer to see and work on the files in SourceDir

On MyVm you cd to /mymount and do a ls –l

The ls –l goes through the wormhole over to SourceServer and gets the info for SourceDir and brings it back to you on MyVm and displays it.  The Files are NOT on disk on MyVm.

When you backup a server like a client (physical server) it’s like doing an ls –l and backup everything in the list.  By default we do not backup NFS/CIFS mounts because they really are not on this system.

So when you Backup  SourceServer you are backing up SourceDir.  If you backup MyVm like a client and say follow NFS, the backup is going to go through the wormhole to SourceSever and get a data stream of everything in SourceDir, bring back to MyVm via the wormhole and send it to Avamar.

You are now backing up SourceDir twice, once on SourceServer and once on MyVm.  This is extra overhead, time, and metadata.

A VM resides in Vcenter (or Hyper-V or whatever you are using)  as a VMDK  this is like a box with all the data and OS in it.  When you pick up a box you get the contents without ever looking in it.  So when you Backup a VMDK(VM) you get the whole thing without ever looking in it.  So the backup does not know you have a NFS mount, it does not know to go through the wormhole and get a copy of that other data.  It just picks up the box and everything in it. (remember that data is not here it is on SourceServer)

When you did the restore of the VM to a new vm and booted it up, the OS said Hey I am supposed to have a NFS mount I am going to make that mount.  This is  why when you went to the NewVm you could see /mymount and all the info in it from SourceServer:/SourceDir.

Backing up a VM will never backup data from a NFS/CIFS mount.  Only backing up as a client will.

But you don’t have to do that.

Remember I said you get the data when you backup SourceServer.

So in Avamar go to the backup for SourceServer and find SourceDir.

Do a restore of a file and give it a new name.  When the restore is done, go to MyVm and cd to /mymount you will see your restored file – thorough the worm hole – on SourceDir.

So for this restore you are trying to do, just go the backup of SourceServer and find SourceDir and do your restore you will then see it on MyVm.

Any questions?  (Ian can correct me if I got anything wrong)