I'm going through the Online Backup and Recovery Guide, and trying to grok the ins and outs of SnapMirror and LUNs.
I have a purely procedural question: If I have a source volume full o' LUNs, do I have to define the LUNs on the destination filer, or will the LUNs and their structure "appear" once the mirror is up. They are essentially files, so I would think the latter, but that's a guess.
Once they do appear (or are populated), can I map them to a FC or iSCSI service on the destination filer (albeit read/only)?
I also have a utility question: If the LUNs are used for file systems as opposed to database, then the NetApp isn't going to understand the internal structure of that file system, so any given mirrored file-system-in-a-LUN is essentially not synced, and therefore in a "crash-compatible" state, right? And if backed up via NDMP, it would just be a "data blob", right?
Is there a product or a feature that will get the NetApp to look inside that LUN, and recognize and deal smartly with, say, a NTFS file system inside of the LUN?
Thanks!
/// Rob