topic Re: DFM creates qtree with qtreename_00 in Active IQ Unified Manager Discussions https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/DFM-creates-qtree-with-qtreename-00/m-p/23121#M4925 <HTML><HEAD></HEAD><BODY><P>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.</P></BODY></HTML> Fri, 18 Feb 2011 17:44:45 GMT smoot 2011-02-18T17:44:45Z DFM creates qtree with qtreename_00 https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/DFM-creates-qtree-with-qtreename-00/m-p/23118#M4922 <HTML><HEAD></HEAD><BODY><P> 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.</P></BODY></HTML> Thu, 05 Jun 2025 06:59:50 GMT https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/DFM-creates-qtree-with-qtreename-00/m-p/23118#M4922 patrickw 2025-06-05T06:59:50Z Re: DFM creates qtree with qtreename_00 https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/DFM-creates-qtree-with-qtreename-00/m-p/23121#M4925 <HTML><HEAD></HEAD><BODY><P>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.</P></BODY></HTML> Fri, 18 Feb 2011 17:44:45 GMT https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/DFM-creates-qtree-with-qtreename-00/m-p/23121#M4925 smoot 2011-02-18T17:44:45Z