Hello,
we use two different VSS-DBs on two computers with virtually the same contents. These computers are only connected to replicate these contents. In meantime changes made to both DBs but not to the same projects in each DB (this is ensured by checkin out each project in one of the DBs).
To replicate a specific project (the more recent is by definition always the "master") we archived the more recent projekt in one DB and tried to restore this archive in the other DB "over" the older project with the same name.
Is this procedure generally possible
It didn't work, yet!
Please help!
Thanks in advance!
Klaus
Replication of two VSS-Databases by using archiv and restore
Hot Topic
- Why text editor classes is so closed in Avalon?
- z-order in XAML?
- CreateNewWorkItem fails, thus failing the build
- Repeating MediaElement
- What happened to Cells(row,column)? Also Late Binding.
- Charts in VSTO Word
- Adding drop down list control to an Appointment Form
- Stepping through the debugger takes a life time.
- ReportViewer not generating online
- Attaching digital signature after reading the entire word document/Excel sheet
Visual Studio
- Does VSS 2005 Internet Require a Server Share?
- Create Dynamic Reports
- modifying xps document
- Printing Reports: Layout help
- Using Crystal Reports 10 with C# EE 2005
- Unable to debug System.Net.DigestClient throws an exception
- devenv /setup takes a lot of time...
- Installing SDK April 2006 Error code 112
- View sorting does not work for me
- pass a local property into another target
Replication of two VSS-Databases by using archiv and restore
Paolo Hutchison
Hi Patrick,
thank you for your help, even if it's no good news.
These two databases ARE copies of each other and yes they be updated independently but not regarding to the same project.
I could life with the delete/create-method (and the detour over a blank DB) if it would be assured that all the shares and branches are still remaining. And if it would work, is it possible to repeat such a process any number of times
Klaus Staehle
Soeren D.
I am not sure if what you are attempting to do is possible. If you have two databases and would like to replace entirely a project in one database with the up to date copy from another database than you should be able to rename or delete the older project and archive and restore the newer project to the database you would like to update. If the two databases have been independantly create (not copies of each other containing unique GUI) this procedure should work. I not sure if this is the goal. Alternatively you could restore to a blank independent copy of the database and archive and restore to the database you wish to update if the two databases are copies of each other. The point is when you do the restore the restore has to identify the database as a new database so that new physical files will be assigned to the updated copy.
It is not possible to simply update the existing physical files with new versions using archive and restore you can create an new set of physical files in the way decribe above.
Also rember if you update the two databases idependently it will be impossible to keep them in sync with each other via straight file copy. If you start with 2 identical databases and someone adds a file to each database independently then one file will be trfaaaaa(file1.txt) the other file will be trfaaaaa(file2.txt).