DFM creates qtree with qtreename_00

IHAC who has created a SnapVault relation and the name of the qtree to backup, was used to create a qtree with this name on the SnapVault secondary. But when we checked the destination we also saw a qtreename_00. Can somebody explain why this new qtree has been created.

Re: DFM creates qtree with qtreename_00

My guess is there already was a qtree named "qtreename" on the secondary volume. When creating a SV relationship, the destination qtree must not exist before you start initializing. To avoid the conflict, we add the _00 suffix.