I have a Windows Server 2012 with an active repository on VisualSVN version 3.3.1.
We want to copy this to a new VisualSVN Server instance version 5.1.0 on a Windows Server 2019 and replace the old server.
Is there a way to duplicate the repository completely and with all permissions etc. and import it on the other server?
We have already done it with the commands
svnadmin dump REPOS_PATH [-r LOWER[:UPPER]] [--incremental] [--deltas]
and
svnadmin load REPOS_PATH [-r LOWER[:UPPER]].
However, it does not retain the permissions and locks here.
Also, I found a post saying to only copy the files in the repository directory but I am not sure whether this is the right and correct way: Post
Migrating VisualSVN Server
You don't need to use svnadmin dump and svnadmin load when migrating VisualSVN Server onto a new server computer.
You should not mix up the server migration and upgrade tasks. They have to be approached separately if you plan to migrate the server and all repositories from one computer to another. Normally, you need to either to upgrade your existing server installation to the latest version and then upgrade, or upgrade you existing server installation and upgrade later.
Migration instructions are given in the article KB166: Migrating VisualSVN Server to another computer.
Upgrade instructions are given in the article KB204: Upgrading to VisualSVN Server 5.1.
Migrating a repository
You don't need to use svnadmin dump and svnadmin load when importing only one or a few repositories onto another VisualSVN Server installation.
If your task is to migrate the server with all the repositories, see the section above.
When you want to import an individual repository from another server installation (without needing to migrate the server itself and all other repositories), you need to follow the instructions from the article KB10: Importing Repositories into VisualSVN Server:
Create a backup of the repository and restore it on the new computer.
or
Copy the directory of the individual repository onto a new computer and import it.
Repository settings including user permissions and hook scripts will be retained with both approaches.
Related
I'm an IT project manager. A developer on my team is complaining that she keeps losing her connection to TFS and that VS requires a constant connection to TFS to work for her. Our CIO is asking me why she doesn't only need a connection to TFS while checking in and out code. I do not know the answer.
Thank you,
Val
TFVC, Team Foundation Version Control, is one of the ways to store sources in Team Foundation Server (TFS), if your TFS serves is 2015 or later, Git is the new default. TFVC is a centralized version control system and assumes your developer has a persistent connection to the server. This is especially true when the workspace of the developer is configured as a "server" workspace, in which case each file system operation is synced to the central server.
In Workspace Type = Server mode your options are:
Use the Go Offline option to temporarily disconnect from the server and work locally in isolation.
Of Change the workspace type to local, which creates a local folder with a compressed copy of each file in the workspace.
This will reduce the number of interactions with the server, making it more pleasant to work when authentication is messed up. But a developer should be checking in and out code at a regular interval, preferably each change that puts the code in a stable state. I'd get VERY frustrated when even something as a checkin/checkout requires an auth prompt.
But your real problem
Is not whether TFS is prompting for auth, it's why the workstation or the server infra isn't (allowing the) caching of the credentials. This can have many causes:
The TFS server isn't configured with a secure connection (https)
The TFS server name doesn't match the server configuration
A proxy server is interfering
A local development proxy (like Fiddler) is turned on and not configured to ignore the TFS server
The Active Directory policy is forcing the credentials to not be stored
The TPM of the computer isn't working well and keeps resetting
There is a VPN interfering
Some endpoint monitoring system is detecting suspicious behavior and is triggering a re-auth
An incorrect credential is cached in the Windows Credential Manager.
The TFS server is in the wrong internet security zone
The Internet security zone settings are configured to not store credentials
...
...
Solve that and the developer will be much happier.
And TFVC is getting old (and most teams have moved to Git)
As others already commented, TFVC is getting old and many development teams have migrated to Git. Git gives developers a local copy of the sources and its history to work with, giving much more power to the developers to work locally without a need to connect to a central server.
If migration isn't an option (yet), tools like git tfs can help a developer to start working in Git locally, while still connecting to a central TFVC server to send the changes to the rest of the team.
But the long-term solution is to upgrade your development tools and get rid of TFVC.
TFS is getting old (is now Azure DevOps Server)
And while you're at it, TFS is getting old. It has been renamed in 2018 and is now called Azure DevOps Server. Azure DevOps Server 2020 is the latest. If you're having issues with TFS, making sure it's up to date and installed on a recent Windows Server version helps too.
I am using AnkhSVN v2.5 and TortoiseSVN 1.9.4
I am not able to browse through the directories on my local drive.
Running as administrator didn't help either. However when using VisualSVN the issue is resolved.
Unfortunately, I can only use AnkhSVN, please help.
TortoiseSVN 1.9.x is based on Subversion 1.9. Local repository it creates and that you access via file:/// has FSFS format 7, by default. This FSFS format is new in SVN 1.9; SVN 1.8 and older clients and servers will not be able to read this repository unless you dump-load its data into an clean repository with older format.
AnkhSVN 2.5.x is based on SVN 1.8 (via SharpSVN) and this explains why it is unable to access this repository. The problem is that AnkhSVN does not display full error message in your case. The error could help you find out what's going on. I'm not sure, but I guess that this is the error that AnkhSVN had to display in your case: svnadmin: E125006: 'REPOS\db\format' contains invalid filesystem format option 'addressing physical'.
These steps should help you solve the problem:
Install VisualSVN Server or another Subversion server on Windows and access your repositories via HTTP(S) or svnserve instead of local file:/// access. The repository internals will not matter for your client in this case as the client will communicate with the server, not with the repository directly. This will help you avoid such problems in future.
Update to AnkhSVN 2.6.x. It should be compatible with SVN 1.9.x and Visual Studio 2012. I guess will access that repository without errors. I'm not sure, but I guess that there is no practical reason to use older AnkhSVN builds.
I'm building few scala libraries and use them in business projects. To share libraries i use 'publishLocal' in sbt. This command uploads artifacts into my local folder. This is ok, it's fast but when i work from another machine i have to republish all this libraries because some changes had been made. So, this my is question: Is my workflow correct? Or i have to publish my artifacts to remote binary repository (ex. nexus) and add it to my business projects as resolvers? Should i use 'publishLocal' at all?
As indicated in the comments, it is strongly suggested to use a Repository Manager such as Nexus Repository Manager, or Artifactory.
You might try Nexus Repository Manager 3.x, as it should help quite a bit with your problem. You can install it on your server, as well as locally if you'd like as it can be used with other tools such as npm, NuGet, etc...
You can download the Open Source Software Edition of Nexus Repository Manager from this link: https://www.sonatype.com/download-oss-sonatype
I am a teamcity developer and our organisation currently uses Team-city 9.0.3 Free version. Now we maxed out Builds. So we are planning to take an enterprise edition.
But before that we need to upgrade the teamcity to latest version 10.x. while i am doing the upgrade it throws the following error.
Please click the link to see the error
The steps i did for the upgrade are
-- Take a back up of entire Teamcity which will be in /root/.BuildServer/backup
-- Stop the Teamcity server and delete the whole teamcity directory
-- copy the backup .Zip file into import section.
-- download the latest teamcity and do the necessary configurations and start the teamcity server.
-- go to Administration/Import and start importing the file from /root/.BuildServer/import
While importing i am getting the above error as version is not supported.
Please help me on this so that i have to upgrade the Teamcity and go for enterprise edition
Thankyou in advance..
It sounds like you are trying to import a backup created with TeamCity 9 into TeamCity 10, that isn't supported, backups can only be restored with the same version they were created with.
When you install TeamCity you usually have a data directory (probably ".BuildServer" in your case) and the software in a different location. You shouldn't delete the data directory, you should upgrade the database and data directory in place (TeamCity will prompt to do this when the new software starts, refer maintenance mode below).
If you continue with your proposed route you'll need to create a fresh TeamCity 10 database with the new schema version, however you'll loose all the other settings and data as that backup sounds like a project config only backup.
JetBrains provide detailed guides to perform upgrades:
https://confluence.jetbrains.com/display/TCD10/Upgrade
https://confluence.jetbrains.com/display/TCD10/TeamCity+Maintenance+Mode
I'm currently using TeamCity 9.0 with MS-SQL as the repository. I want to upgrade to version 9.1.1. I run the installer and I see 9.0 being uninstalled, followed by the 9.1.1 installation. After the installation is done TeamCity won't come back. The Web portal shows this error:
TeamCity server is connecting to MSSQL database. The database server is not started yet, or the database specified in '/config/database.properties' file is inaccessible.
I am using the same user account as the previous installation so it doesn't look like a permissions issue.
According to the documentation the installer should prompt for the data directory, but I never got that prompt.
While uninstalling I removed the TeamCity/lib/jdbc folder (those are the libraries to use MS-SQL). After installing 9.1.1 I copied back the folder and restarted the TC service.
Thoughts?
Check your config/database.properties file, and see if your database is still there.