Automated Poweshell backup script IIS 7.5

by Cricka at 2012-11-07 14:24:26

Hi.
My ideas of how to make automated full IIS backups on an Windows 7 with IIS 7.5 has run out.
It is an previous installed Windows7/IIS7.5 with an really important web-aplication running on it and I would like to make automated continous full backups on it so if ever neccesary I can restore the IIS to another Windows 7, Server 2008R2 or Server 2012.
All I found this far is AppCmd that gives mme the option to backup, restore and delete backups. But I want to make it completely automated so at first I started to make an AppCmd script for each day of the week and then run theese with scheduler but with AppCmd there is no way to wright over an old backup so this way I have to make scripts for every backup and it will also increse in size contionously.
I could even use an 3’rd party software that can make “baremetal” backups of IIS7.5 but I dont know of any so therefore I hope that someone allready solved this somehow with powershell :slight_smile:

//Cricka
by DonJ at 2012-11-08 11:12:17
Look at solutions from AppAssure, or perhaps Acronis, or UniCenter. These can all make continuous block-level server backups and restore to bare metal. You’re not going to have a lot of success trying to roll something like that on your own, unfortunately. You have to get pretty low-level to do it right.
by Cricka at 2012-11-08 11:49:31
I do not want to backup the entire Windows 7, Only Everything tog get the website running on Another IIS ifrÃ¥n needed…
by DonJ at 2012-11-08 11:57:06
Understood. And those solutions can all do that. If you’re hell bent on rolling your own recovery solution, I’d start with robocopy. Grab the right files and you can rebuild IIS. It’ll be work, though. The whole point of a tool is to make it easy and quick. But you’ll still be building your own script to rotate backups, purge old ones, etc. it’s a lot of work. That is why vendors sell those tools :). But if I absolutely had to DIY this I’d start with robocopy. Jason may have other ideas; he’s teaching this week but let’s see what he says when he checks this thread.
by Cricka at 2012-11-08 12:24:11
So far I know that if I backup with AppCmd and save c:\inetpub I should be able to restore the site to another IIS… so my thought is to make an AppCmd backup script for each day of the week and run them as scheduled tasks. Then I need a script that deletes them between friday and monday… I think that should do it :)**
by JasonHelmick at 2012-11-10 13:13:59
Hey Cricka!

I prefer using one of Don’s suggestions because I don’t usually see the need to DIY my own for this. In fact, RoboCopy (or even a PowerShell copy-item) works very well can can be scheduled. If your going down the AppCMD route and are happy to do your own automation than by all means have at it. I think you have already discovered that its pretty easy to backup a site using Appcmd and you can easily schedule it with the Windows scheduler.

One thing I questioned about your post was the reasoning behind the continuos backup…would a 2 server web farm with the website files located on share work better for you? In that case, a failover would be immediate. That might remove the need for the continous backup. Just checking as I was unclear from your original post and of course your specific case may vary.

Have a great day!

Jason
by Cricka at 2012-11-10 15:05:32
Hi Jason.
My reasoning behind continous backup is that this is a customer has a business critical website running a reportsystem set up by some other tech’s and because of that i would like to make shure that I really have everything essential backed up so if a computer issue apears then I can restore the site and the DB that I allready am backing up…