Skip to main content

Running web deploy from the command line: some useful commands

I talked about Web Deploy before. It allows you to easily deploy your web applications to IIS without much overhead. I use it most of the time. Last week I asked the server administrator to enable the automatic backup feature on the web server. 

Once I got the confirmation email that it was configured, I did a new deployment to test the backup feature.

After the deployment completed succesfully, I opened a command prompt and browsed to C:\Program Files (x86)\IIS\Microsoft Web Deploy V3.

Print the list of backups

I used the following command to dump the list of created backups:

msdeploy -verb:dump -source:backupManager="development.customer.be/appname",computerName="serverXX",userName="UserXYZ",password="PasswordXYZ"

But the output window returned nothing. No backups were created.

Print the backup settings

I switched to another command to dump the backupSettings from the server:

msdeploy -verb:dump -source:backupSettings="development.customer.be/appname",computerName="serverXX",userName="UserXYZ",password="PasswordXYZ"

This time I got some information back:

Info: Using ID '5263eab5-358c-4f3a-9d65-b60f2bade089' for connections to the remote server.

MSDeploy.backupSettings development.customer.be/appname

MSDeploy.backupSettings/backupSettings[@path=’development.customer.be/appname']/backupSetting[@turnedOn='False']

MSDeploy.backupSettings/backupSettings[@path='development.customer.be/appname]/backupSetting[@enabled='True']

MSDeploy.backupSettings/backupSettings[@path='development.customer.be/appname']/backupSetting[@numberOfBackups='4']

MSDeploy.backupSettings/backupSettings[@path='development.customer.be/appname']/backupSetting[@continueSyncOnBackupFailure='True']

MSDeploy.backupSettings/backupSettings[@path='development.customer.be/appname']/backupSetting[@excludedProviders='appPoolEnable32Bit; setAcl; appPoolPipeline; createApp; appHostAuthOverride; appPoolNetFx']

There are 2 important things I noticed in the config:

  • The Backup feature is enabled at the site level.
  • The Backup feature is turned off in IIS.

So that explains why we don’t see a backup. We still have to turn on the backup feature.

Turn on backups on the server

Log on to the webserver and execute the following Powershell command:

PS C:\Program Files\iis\Microsoft Web Deploy V3\scripts> TurnOn-Backups -On $true

11:43:53        Information     Turning Backup Feature On.  In order for backups to execute, they still need to be enabled at either the server or site level.

After doing this I did a new deploy. Let’s dump the list of packages again:

msdeploy -verb:dump -source:backupManager="development.customer.be/appname",computerName="serverXX",userName="UserXYZ",password="PasswordXYZ"

This time I got some data back:

Info: Using ID '7b36c65f-fcf1-48e7-a26b-16f8438473ae' for connections to the remote server.

MSDeploy.backupManager development.customer.be/appname

msdeploy_2013_03_15_11_17_34.zip

Labels:

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...
Read more

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.
Read more

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...
Read more