Generall: =========== Be aware of multiple limits which are not written in the fat client code of dfpm. All limits like different aggr- types, netapp OS types etc. are not checked and no exception handling. Your case source Ontap 8.0x 64bit aggr > 32 bit ist not supported (see DPG/Admin Guide). You did chose DR Mirror in dfpm. This will produce a volume snap mirror async mirror on command line therefore the mirroring between 64/32 bit is not supported. Qtree SM would be supported as logical replication. In your case you need to select a DR Backup Policy where is creating on command-line Netapp a qtree snap-mirror replication async. The difference to a DR Mirror (Volume Snap Mirror) the Backup DR Mirror Policy is creating Qtree Snap- Mirror like sourcefiler:> /vol/source/- in case of whole volume SM. I know this is absolutely not clear if you are going to select different policies. Be aware if you are using
Policies in dfpm and effective creating Snap's on Filer ======================================================= DR Mirror = Volume Snap Mirror like sourcefiler:vol1 > targetfiler:vol1 DR Backup = Qtree Snap Mirror like sourcefiler:/vol/vol1/- (whole volume) or source filer:/vol/vol1/q1 > targetfiler:/vol/vol1/q1 Backup = Qtree Snapvault basically same as DR Backup but Snap Mirror can be writable this would never possible with snapvault therfore there is no "DR Capable" flag in dfpm but if you change in dfm option set pmQSMBackupPreferred=No then QSM is used everytime.
Your Case ========= You need to configure a empty dataset (no source, no target included) You add then a protection policy Policy = DR Mirror & DR Backup or just Backup (but you need to be secure that both aggr types source/dest are same bit 32/32 64/64
Only after you added to the emptyDataset desired backup Policy DR Mirror/Backup you can import external relationship. (But again need same bit #nr)
Be aware all existing snapshots are not imported and even there still exist on vol’s there are not shown in dfpm. Only dfpm backups are shown. dfpm creates as well own additional snapshots (at least 2 x ) and you need to purge/delete older snapshots manually.
Re: Importing Existing SnapMirror Relationship into Protection Manager