Skip to main content

Azure DevOps Server–Move collections–Offline detach

One of the basic building blocks of Azure DevOps Server is a “Project collection”.

The documentation describes it like this:

The primary organizational unit for all data in Azure DevOps Server. Collections determine the resources available to the projects added to them. 

From a technical standpoint, a project collection is a separate database. It is possible to move project collection between different database instances but be aware that just backing up a collection on one database server and restoring it on another database server is not sufficient.  The well documented way is through a detach/attach operation as I explained last week.

But another ‘hidden’ option exists through an “Offline detach”.

Backup the collection and configuration database

Take a backup of the collection database that you want to move using a tool of your choice and restore it on the database server used by your target Azure DevOps server. Also take a backup of the configuration database and restore it as well(using a different name to avoid overriding the real configuration database).

Convert the database to an attachable collection

The trick is to convert the database to an attachable collection by copying over the configuration data from the configuration database to the collection database.

TfsConfig offlineDetach /configurationDB:DevOpsSQL;Tfs_Configuration /collectionDB:DevOpsSQL;Tfs_ExampleCollection

Attach the collection

Now you can to attach the collection again as with the normal procedure. So back to the Azure DevOps Administration console:

Remark:

Although I tested the approach above and it worked, it isn’t recommended. The collection and configuration database should be perfectly in sync. So preferably only do this when your Azure DevOps instance is offline.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...