How to add a qtree to an existing Snapvault Job (Protection Manager)

[DAMNX6789]

Hello,

we have a primary and a secondary site, on the primary site is a volume called Gruppen, inside are many qtrees. These qtrees are backuped via SnapVault to the secondary site to the backup volume.

We created a new qtree inside the primary volume Gruppen.

We then tried to add the newly created qtree to the existing Dataset in Protection Manager (primary physical ressources), however Protection Manager wants to create a new flexible Volume with only the relationship with the newly created qtree.

1) Is it possible to create a new qtree and add it to the job, without the provisioning of a new volume?

2) If it is possible, what's the way to achieve this?

Thank you!

[adaikkap]

Hi Michael,

     By default you can only have 50 relationship going to a secondary volume. If this is a 51st qtree then it will not create the relationship in the existing  volume rather try to create a new one.

If you want to make it into the same volume you will have to tune a option as follows. This will allow you to use the same secondary volume upto 100 relationships.

dfm option set pmMaxSvRelsPerSecondaryVol=100.

Regards

adai

[DAMNX6789]

Hi Adai,

this was a good guess, but unfortunately is this not the problem, there are about 15 Qtrees inside the volume.

Could this be an issue with the volume size? Because Protection Manager wants to create a new volume of size 9TB!

Primary:

Filesystem                         total                 used                avail capacity                 Mounted on

/vol/Gruppen/                     5068GB          3419GB          1649GB      67%            /vol/Gruppen/

/vol/Gruppen/.snapshot     563GB           347GB               215GB      62%            /vol/Gruppen/.snapshot

Secondary:

Filesystem                         total            used           avail capacity            Mounted on

/vol/Gruppen/                     5734GB     4262GB     1471GB      74%       /vol/Gruppen/

/vol/Gruppen/.snapshot     1433GB      466GB      967GB      33%          /vol/Gruppen/.snapshot

[adaikkap · Accepted solution]

Hi Michael,

     These are the conditions under which PM creates a new secondary volume.

When

• Maxrelspersecondaryvolume
  • You exceed the default(50) # of relationship. This is not your case
• PlatformDedupeLimit
  • Adding the new member may require the secondary be increased, but cant be done due to the max dedupe limit supported for the given platform
• Volume Language.
  • The new members volume language is different from that of the exisitng secondary volume
• Fan-In
  • If the new member exceeds the max-fan in ratio

If the new qtree you are adding is from the same primary  volume  then you should experience case 2.

Regards

adai

[DAMNX6789]

I think you can be right with the volume language because, this is another issue, that we couldn't solve yet:

Secondary> Mon May  6 12:58:27 CEST [Secondary:replication.dst.langMismatch:warning]: Volume language was changed before this transfer or it was changed before some previous update transfer for the relationship of qtree /vol/Gruppen/Q_TK. This might create some problems with further replication transfers of the relationship.

Is there a safe way to change the language without interrupting the Snapvault Relationship?

[adaikkap]

Hi Michael,

     Who changed the volume language ? PM doesn't change it once a secondary volume.

You will have to change the vol lang back to what it was in the secondary volume by using filer cli and discover the same in DFM.

Then re-add the qtree so that it gets created in the same destination volume.

Regards

adai

[DAMNX6789]

I can't tell who has changed it and why, this was before I took over.

However, the primary volume "Gruppen" is language de.UTF-8

and the secondary is now also de.UTF-8

From what i know is, that the volume language on the secondary system was undefined and somebody changed it after the Snapvault Initialize to de.UTF-8