Each storage vendor (and NAS device) has its own, unique geometry and metadata for its filesystem. These filesystem dependencies carry over into the format of the backup on tape. These dependencies are also inherited by their NDMP backups and are independent of the NDMP protocol itself.
For example, NetBackup supports Isilon, VNX and Netapp,among others. However, it does not support restoring VNX data to Isilon or Netapp. Similarly, EMC Avamar supports those same NDMP platforms, but does not support restoring one NDMP backup to a different architecture. This is because each vendor implements elements of the NDMP specification differently, to suit their individual filesystems.
Even though many vendors support NDMP backups (and even three-way backups between different vendors, as an example), their unique implementations add a layer of complexity.
Let us know if that helps!
If you want to be able to backup and restore independent of the underlying storage architecture, you can configure the backup application to backup using File Protocols, such as SMB and/or NFS.
Otherwise, as others have mentioned NDMP is a command and control protocol. It can make a series of calls against a variety of different storage platform to initiate a backup/restore using the native backup format of the underlying storage platform.
While every said before is totally correct, there are (limited) ways to extract data Isilon NDMP backups. If you are interested, and you can omit Windows permissions (ACLs), and need it for a one time job or a "plan C", let me know.
Pete I did not get that ? If we have a NDMP full from isilon , if we need to restore it to any Linux file system and keep the same shares ? how could we do that or can we ? This is for low cost DR situation ..
Ok, here it is, BUT do not make this part of a paid solution, it's unsupported
and more a "last resort" kind of thing:
Install a virtual Isilon node in your favorite VMware hypervisor.
Mount the target Linux file system on the virtual node via NFS.
Perform a network-based (three-way) NDMP restore to the virtual node,
redirected to the NFS mount.
Strangely, the NFS mount must be under /ifs, e.g. /ifs/restore
But the actual /ifs file system, which is pretty slow on virtual nodes,
is never touched by the restore.
The performance will depend on the whole pipeline:
NDMP/tape source --> network paths to and from the virtual node
--> ingest performance of the Linux system. Writing tons of small files
over NFS would be inherently slow.
For a supported, transferable backup solution you will need to
rely on NFS/SMB-based backups in the first place, as stated by the others!
Guys if I am reading "EMC avamar NDMP accelerator for EMC NAS Systems" version 7.2 User Guide Rev 01 - PAGE 41 , it talks about "Restoring to a Linux or Windows Client from NDMP backups" ?
Can some one validate that for me please ..
Seems that Avamar, being an EMC product like Isilon, is able to correctly decode the Isilon backup streams sent over NDMP.
Which isn't too hard as Isilon uses an augmented tar format... which only theoretically gives you another way to extract stuff by yourself (I have tried and like the virtual node method more ).