Active IQ Unified Manager Discussions
Active IQ Unified Manager Discussions
We want to upgrade our Protection Mgr to 3.8 but then can across this bug:
Bug 354933:
The issue occurs when using the SnapVault and Open System SnapVault protocol with Protection Manager with DataFabric Manager server 3.8 and Data ONTAP 7.3.1. Data ONTAP storage systems run out of resources (NDMP threads) when used for SnapVault activities because Protection Manager with DataFabric Manager server 3.8 uses a new API for data transfer. Normal data protection activities are possible until the NDMP thread count in Data ONTAP is exceeded. The number of threads available is platform dependent and the threads cannot be recovered after they have been consumed. Normal activity continues in Data ONTAP, but additional NDMP transfers are blocked after the maximum thread count is reached. Note: After Data ONTAP reaches the NDMP thread limit, additional NDMP requests are not serviced, whether they are for SnapVault, SnapMirror, or other activities. This issue does not affect DataFabric Backup Manager or DataFabric Disaster Recovery Manager. Workaround: None. The only recovery solution is to reboot the storage system or upgrade to a version of Data ONTAP that contains a fix for Bug 354933.
Currently this is not fixed in ANY version of ONTAP.
In our environment we run a 3070 cluster that then backs up to an R200 which then mirrors to an offsite 3020. Trying to figure out the effect upgrading to 3.8 would have. Sounds like the above bug is a show stopper but may be reading it wrong.
Thoughts???
Fixes??
Hi Kevin,
If your filers are not running 7.3.1 then this is not an issue for you.
If your filers are running 7.3.1 then there is a patch release of 7.3.1 ONTAP available.
-Marlon
So if we DONT run OSSV but all of the rest we are OK? thats how I read this. It would be good to have a confirmation.
Cheers,
Eric
AFAIK OSSV also uses ndmp threads.
Yes, OSSV is NDMP too. thats good then because we dont use OSSV so I should be good to upgrade.
Eric
The question here is if your storage systems are running ontap 7.3.1 and if you are using or planning to upgrade to 3.8 then you must upgrade your
Data Ontap Version on your storage systems to the mentioned patch releases to fix this issue.
Regards
adai
Currently this is not fixed in ANY version of ONTAP.
This is fixed in ontap versions 7.3.1.1P4D2 and 7.3.1.1P6D6
If you are planning to upgrade to 3.8 pls upgrade to 3.8D3 or above.
Regards
adai
So where does one go about getting all this patches and non regular versions?