Re: Why should we disable dedupe when using Protection Manager?

community@netapp.com — Thu, 02 Jul 2009 15:41:20 GMT

I think the only rationale behind that recommendation (I'd treat that as a recommendation) is explained on that page:

if snapshots exist, de-dupe will 'release' duplicate blocks & the youngest (if my memory servers OK) snapshot will be grown by exactly the same size as de-dupe 'saving'.

But this issue is not specific by any means to just Protection Manager.

Regards,

Radek

Why should we disable dedupe when using Protection Manager?

community@netapp.com — Thu, 02 Jul 2009 14:47:27 GMT

Hi,

I have a question regarding the documents on NOW:

Backup und Debup

http://now.netapp.com/NOW/knowledge/docs/ontap/rel7311/html/ontap/rnote/rel_notes/concept/c_oc_rn_lim-dp-sv-protmgr-dedupe.html

Do not use Protection Manager 3.7 on volumes that have deduplication enabled.

Okay, I know OM 3.7 is not aware of Dedupe. But it is still possible to do backups with dedupe enabled on the primary side.

My Customer found this and is asking if this also applies for the PM in 3.8 Version.

Additional question is...

Do we need Provisioning Manager license for future Protection Manager installs, if we want to use dedupe on primary and secondary snapvault relationship? (got something in my mind from talking with PMs)

NetApp Technology Network: Message List - Why should we disable dedupe when using Protection Manager?

Re: Why should we disable dedupe when using Protection Manager?

Why should we disable dedupe when using Protection Manager?