Hi Hendrik,      Here you go with the answers, I'm testing it in the lab right now. Really cool feature. I have a few questions though, maybe you could help me with these? 1.) I have a volume that is provisioned and managed by Protection Manager and I can choose to migrate it, However, it then tells me that it can't find any qualified destination aggregates. There is another aggregate on the same filer that is part of the same resource pool. It has more than enough available space. Unfortunately I haven't found a way to figure out why PM assumes that a particular aggeragte is not qualified. The help lists the following requirements: Reside on a storage system that meets the necessary license requirements to support the protection policy. #Reside on a storage system that meets the secondary or tertiary storage provisioning policy requirements. #Reside on the same storage system as the source volume if the source volume is attached to a vFiler unit. #Have enough space to accommodate the migrated volume. 1 and 2 are fullfilled as both aggr are on the same filer, 3 doesn't apply as I haven't configured any vFiler, 4 is fullfilled as well. Are there any other checks that are done but not documented? Can you try for the same volume using the cli ? That will give you the exact reason why the destination aggr is not qualified. dfpm migrate volume -D -d <destination-aggregate-name-or-id> <volume-name-or-id> [volume-name-or-id...] Where -D option specifies to display dry run results of volume migration. Migration will not be started. -d option specifies the aggregate to which the volume(s) needs to be migrated.If not specified, a suitable aggregate will be selected. volume-name-or-id is the volume to be migrated. 2.) Several people have independent dfm installations in the lab environment. I noticed that my installation allows to migrate volumes to a different aggegate, even though these are backup volumes managed by a completely different dfm installation. So it somehow seems to detect that these volumes have been created by a Protection Manager installation, while it does not allow to migrate volumes that have been created outside of dfm. How does the Secondary Space Management find out that these are PM created volumes? There is a flag used internally as to find if the volume is part of the dataset and the relationship is managed by Protection Manager. Below are the ground rules for migration. Volume should not have any clinet facing protocols/exports, like FCP/iSCSI/NFS/CIFS Volume should not be a parent of FlexClone. Volume should not have un-managed data protection       (SV/QSM/VSM) relationships. In other words, the volume      should belong to secondary node of a dataset 3.) I have a customer that runs a large PM setup (managing >1000 snapmirror relationships). As the relationships already existed, we imported them in Protection Manager. Is there any way to use secondary space Management for these relationships? Or are they locked out from these new features forever, just because they used NetApp systems before Protection Manager was invented? As said in the above reply once its part of a dataset even though the relationship was not created by PM its still eligible for SSM Hope I clarifed all your doubts, Do try and let me know your experience. Regards adai ... View more

Starting OSSV 2.6.1 NHA is not bundled with OSSV installer. You will have to download and install it separately. But until OSSV 2.6 NHA was bundled with OSSV installer and you would be asked if you like to install NHA. Below is the snippet from the install. ... View more

Hi Generally, the simulators have same serial no. DFM uses hostname, IPaddress and serial no to identify a Storage system as new. In your case since the serial number is same dfm is cribbing. Do the following. You'll see a file called serialno in the/install/path/node1 edit this to make it unique from the other. DFM will happily discover both a two storage systems. Regards adai ... View more

Snapmirror destination will always be the exact replica of the source, vol options like autogrow, snap auto delete, vol guarantee etc. So even if autosize is turned on in the destination, on snapmirroring it will follow the source(autosize is off on source), only on mirror break the autosize will be turned on. But since fs_size_fixed set to ON in the destination even on mirror break, autosize cant take effect. so you will have to turn fs_size_fixed to off , so autosize can take effect. A better way would be to create a none guaranteed volume with 2x size than your source so the volume doesn't consume any space from the aggr. On snapmirroring the destination volume size will the exact size of the source volume and only that much space would be consumed from the aggr. Even if the source grows since the snapmirror destinatoin volume actual size is 2x the source it will grow till that size, with out snapmirror failing. Even better would be to create aggr sized volume of none guarantee. Regards adai ... View more

Yes 4.0D1 If you are talking about performance advisor, yes you can create a custom view of different volume with the counters you like. Regards adai ... View more

Its dfm 4.0D1 and not 4.1. regards adai ... View more

Can you install the ossv plugin? Also can you check the following in your ossv agent ? go to /usr/snapvault/bin and run ./svinstallcheck.and get the output ? [root@lnxbin]# ./svinstallcheck SnapVault home directory: '/usr/snapvault' SnapVault database directory: '/usr/snapvault/db' SnapVault temporary directory: '/usr/snapvault/tmp' SnapVault Database and Temporary directories have 13% space left (19642Mb) SnapVault service is running SnapVault listener is running NDMP Server, on port 10000, details:     Vendor     Netapp     Product    SnapVault     Version    2_6_1_2009APR08     Host       lnx     Host Id    E1ADC8FCFE184EC8A1D887F33E5782E8     OS Type    Linux     OS Version 2.6.9-55.ELsmp SnapVault QSM Server is responding correctly Validating filesystems:    Mount point / (/dev/sda3) is suitable for backup    Mount point /proc (none) is a special mount, unsuitable for backup    Mount point /sys (none) is a special mount, unsuitable for backup    Mount point /dev/pts (none) is a special mount, unsuitable for backup    Mount point /proc/bus/usb (usbfs) is a special mount, unsuitable for backup    Mount point /dev/vx (tmpfs) is a special mount, unsuitable for backup    Mount point /boot (/dev/sda1) is suitable for backup    Mount point /dev/shm (none) is a special mount, unsuitable for backup    Mount point /proc/sys/fs/binfmt_misc (none) is a special mount, unsuitable for backup    Mount point /var/lib/nfs/rpc_pipefs (sunrpc) is a special mount, unsuitable for backup    Mount point /usr/local (btcinf02.eng.btc.netapp.in:/vol/local/i386-linux2.0) is a remote mount, unsuitable for backup    Mount point /usr/local/share (btcinf02.eng.btc.netapp.in:/vol/local/share) is a remote mount, unsuitable for backup    Mount point /usr/software (btcinf01.eng.btc.netapp.in:/vol/software/arch/x86_64-redhat-rhel4) is a remote mount, unsuitable for backup    Mount point /u (automount(pid4646)) is a special mount, unsuitable for backup    Mount point /x/eng (automount(pid4684)) is a special mount, unsuitable for backup    Mount point /x/sim (automount(pid4689)) is a special mount, unsuitable for backup    Mount point /x/eng/localtest (btcinf02.eng.btc.netapp.in:/vol/localtest) is a remote mount, unsuitable for backup    Mount point /u/adaikkap (nbhome1.eng.btc.netapp.in:/vol/home1/adaikkap) is a remote mount, unsuitable for backup NetApp Host Agent is installed on this system.    Install Location : /opt/NTAPagent    NetApp Host Agent version 2.7 (2.7.0.2203)    Agent Core Library version 2.7 (2.7.0.2203)    Status : Running with PID 4946 Check Succeeded [root@lnx bin]# Regards adai ... View more

What is your DFM OS flavor. Is it linux or windows did you look at the TR mentioned in the other replies to this post ? regards adai ... View more

Hi emanuel,                  Attached is the screen shot with the highlight for the same.  Regards adai ... View more

Hi          I dont think the burt you mentioned is the cause. Because this burt only cause false positive of power supply failed and not filer its self regards adai ... View more

Are you using DR Dataset? Then you can failover. Delete the dataset. Reverse the relationship.(you are free to use the filer cli or dfdrm clis of DFM) Create new dataset and import the reversed relationship in PM. If its not DR dataset, then. Delete the dataset. Reverse the relationship.(you are free to use the filer cli or dfdrm clis of DFM) Discover them in DFM. Create new dataset and import the reversed relationship in PM. Regards adai ... View more

Hi Emanuel, By default lag warning is 1.5days and lag error is 2.0days. Unless you have changed the values there is no chance that 300 seconds was there by default. You can change the same through NMC-> Policy->Edit Nodes and connections and changing the value back. Regards adai ... View more

emanuel wrote: Is the 253 a controller wide limitation here? C:\Users\emanuel>dfpm policy node get NTFS_backups Node Id:                    1 Node Name:                  NTFS volume data filers only Hourly Retention Count:     2 Hourly Retention Duration:  0 Daily Retention Count:      2 Daily Retention Duration:   0 Weekly Retention Count:     1 Weekly Retention Duration:  0 Monthly Retention Count:    0 Monthly Retention Duration: 0 Backup Script Path: Backup Script Run As: Failover Script Path: Failover Script Run As: Snapshot Schedule Id:       0 Snapshot Schedule Name: Warning Lag Enabled:        Yes Warning Lag Threshold:      259200 Error Lag Enabled:          Yes Error Lag Threshold:        300<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<Here is the answer for your lag error/ Node Id:                    2 Node Name:                  NTFS Backup Systems Hourly Retention Count:     0 Hourly Retention Duration:  0 Daily Retention Count:      2 Daily Retention Duration:   2592000 Weekly Retention Count:     2 Weekly Retention Duration:  0 Monthly Retention Count:    1 Monthly Retention Duration: 0 253 is not controller wide its the 255 snapshot limit per volume. Your lag error is 300s or in other words 5mins as per the policy. Its so evident from the pop up window and the policy lag error settings. Regards adai ... View more

Hi Emanuel,      Can you get the screen shot of the pop window that is show when the ellipsis button against the protection status is pressed in the Dataset page for the dataset in question. That will give all possible reasons why PM thinks its a Lag Error.Also can you get the output of the following command. dfpm policy node get for the policy attached to the dataset ? Regards adai ... View more

Hi Phil, You cannot save the columns or in other words the columns selected or disabled are not persistent across log-in/log-outs in NMC. Regards adai ... View more

The reason behind your aggr copy is current aggr running out of space? If the answer is yes to the above, then pls go head and start using the secondary space management feature of 4.0 Regards adai ... View more

Hi Scott, Can you try installing them in separate Machines? Is launching SMO gui crashing? What about launching NMC? Regards adai ... View more

Hi Scott, To which GUI are you referring NMC ? or SMO ? If its smo can you try to see in dfm if that is listing all available policies by typing the following command. dfpm policy list ? Regards adai ... View more

Hi Scott, Are you installing the ESX version of OSSV? As I see error like Failed to execute 'configure_esx' What is the OS platform on which you are installing OSSV and what it the OSSV installer flavor you are using. Regards adai ... View more

If you want to take advantage of policy based provisioning for primary and secondary you will need provisioning manger license as these are features of provisioning manger. But  as pete said, as of 4.0  provisioning manger is autoenabled when protection manger license is installed.So you dont need separate license. Regards adai ... View more

With Protection Manger 3.8 or latter we do allow fan-in of secondary volumes for SV and QSM relationships. Where we allow qtrees form different primary be backed up to a single secondary volumes. The options is call " dpMaxFanInRatio" which you will have to set it to more than 1 to enable fan-in. Also starting 3.8 we do allow flexible naming conventions in the snapshot naming which is again controlled by the following options. pmCustomNameUseHostName pmCustomNameUseQtreeList pmCustomNameUseRetentionType pmCustomNameUseVolumeName Regards adai ... View more

Then it only means those snapshots are not registered as backup or they are taken with the propagation disabled. Regards adai ... View more

Hi Richard,      Can you elaborate me on what prevents you from using Protection Manager. Just trying to understand what is preventing your adoptions of the same. regards adai ... View more

Hi Emanuel,      AFAIK the default email messages cant be changed.But you can have your alarm script to generate a email with the messages of your choice, using the environment variables of the alarm. http://now.netapp.com/NOW/knowledge/docs/DFM_win/rel38/html/faq/index.shtml#_13.2 The example in the link is for userquota but it is very much same for any space management events of volume, qtree,aggr and userquota which have environment variables associated with them. Regards adai ... View more