Copy a Repository

[dsalter]

Hi,

I am using Vault 10 Standard and need to create a new Repository. I want to copy an existing repository completely intact and create this new one from the copy. Basically a copy of the repository to a new repository name. Is this possible?

Thanks,
Don

[Tonya]

Hi Don,

Quick question before I provide you with some guidance. Will the new repository be in the same Vault database in SQL Server? Or do you plan to install a new Vault Server and SQL Server instance to support the new repository?

Thanks,

Tonya

[dsalter]

Hi,

I would like the new repository to be in the same database (same version), just named differently. Thanks.

[Tonya]

Hello again,

The Vault Folder Export Tool will allow you to export folders from one Vault repository to another. If you want an entire repository, you can export from root and then import into an entirely different Vault database. Vault Folder Export / Vault Folder Import will include the history of the objects directly exported.

The tool is in the Vault Client directory and it's called VaultFolderExportImport.exe. Documentation is in ExportImport.chm in the same directory.

Thanks,

Tonya

[dsalter]

Am I able to import a repository into the same Vault database but change the name of the repository?

[Tonya]

Yes, that is correct. It will be a new repository within the same Vault database. Simply provide the new repository with a different name and import the the export file into the new repository.

Tonya

[dsalter]

Hi,

OK, so everything mostly goes well, except for one folder which will not import. It fails with an error. I've attached the error file. I've tried exporting and re-importing with same error. I cannot get around it and it causes the import to fail.

[Tonya]

Run a history query on $, and in the Actions tab uncheck all actions except for obliterate. Are there any obliterates listed? If so, this could be the cause of the problem.

Can you also look in you Export/Import log, typically found at C:\Program Files\SourceGear\Vault Client\VaultExportImport.txt, and in your Vault server log at %windir%\temp\sgvault\sgvault.log to see if any errors are recorded at the time the Import fails? Can you please send the logs, or the errors to support at sourcegear.com with a link to this forum thread?

Thanks,

Tonya

[dsalter]

I ran a history and there are no obliterations.

I also do not have a VaultExportImport.txt file in the location you mention.
I've searched my PC and there is no file of that name on it.

[dsalter]

I did discover that the issue (right now), seems to be 9 objects:

txid txitem itempath txtype itemobjverid otherobjverid
5466 1 $/Reports/Consolidated View/RDLs/ICCS_WB.rdl 3 44074 NULL
5466 2 $/Reports/Consolidated View/RDLs/E6ME_WB.rdl 3 44075 NULL
5466 3 $/Reports/Consolidated View/RDLs/E5ME_WB.rdl 3 44076 NULL
5466 4 $/Reports/Consolidated View/RDLs/CR4C_WB.rdl 3 44077 NULL
5466 5 $/Reports/Consolidated View/RDLs/CCUO_WB.rdl 3 44078 NULL
5466 6 $/Reports/Consolidated View/RDLs/B5ME_WB.rdl 3 44079 NULL
5466 7 $/Reports/Consolidated View/RDLs/A5CM_WB3.rdl 3 44080 NULL
5466 8 $/Reports/Consolidated View/RDLs/A5CM_WB2.rdl 3 44081 NULL
5466 9 $/Reports/Consolidated View/RDLs/A5CM_WB1.rdl 3 44082 NULL

These are all from the TXID that is failing. All items added to Vault on the same day in 2017.

[Tonya]

Would you be willing to send us your SQL Server database so we could troubleshoot the problem? We may have a special build to provide you.

Thanks,

Tonya

[dsalter]

Hi,

We will work around for now. Given our time constraint we can make do. Thanks.

[Tonya]

When you have time and would like to move forward with additional troubleshooting, please get back in touch and let us know.

Thanks,

Tonya