Since the space on my SSD was getting scarce, I decided to transfer the database files to a different drive. It was much easier than I expected:
- Detach the DB (via ‘Tasks’)
- Move the mdf and ldf files to the new location. (They are usually located somewhere under ‘C:\Program Files\Microsoft SQL Server\’.)
- Attach the DB by choosing the mdf file.
Thanks to the instructions from katieandemil. They were especially appropriate since I also had SQL Server 2008 R2 installed.
If you rather like to use Transact-SQL follow this stackoverflow post.
I did not think it was that easy. I just followed these steps. Just create a certificate in Server Certificates feature on the server node in IIS. Then add https binding to your site (Port 443) and chose the certificate you just created.
Of course this self created certificate is only good for a website with users who trust you. For a bigger website you would usually get an authorized certificate from a trusted certificate authority.
Sometimes we need to configure a new server with the same websites / applications like on another server. Up until now we only used IIS 7.5 on our servers, and I always used these instructionsby Toni Pohl (in German). Sometimes I even then stumbled into problems – they had to do with different IIS installations (i.e. missing features) on the different machines.
Now, for the first time, we have a Windows Server 2012 with IIS 8. Since I could not find instructions on how to transfer the configuration from IIS 7 to IIS 8, I simply applied the same process like above. It went badly: the Application Pools and Sites folder were gone. Luckily IIS backs up its configuration to %systemdrive%\inetpub\history. I restored the default by copying and overwriting adminstration.config and applicationHost.config.
I applied the same method to get the IIS 7 configuration into the IIS 8 on the other server: copy and overwrite adminstration.config and applicationHost.config. And it seems to work – I had no problems upto now.
The setup
We use the build in Performance Monitor on our Windows Servers to chart the data. That way we can see in how much load running the web application Camping.Info results. We usually monitor “% Processor Time”, “Commited Bytes”, “Requests/Sec”, “Requests Current” and “Request Execution Time”.
The loss
The latter three did not show up after I repaired the mirror on the server. I could not add them back via Properties –> Data –> Add. The whole category ASP.NET v4.0.30319 was missing.
The solution
After trying a few things and googling, I finally found the answer on serverfault: http://serverfault.com/questions/25842/performance-monitor-cant-add-counters-from-net-data-providers (second answer).
All I had to do was to delete the entry “Disable Performance Counters" in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ASP.NET_4.0.30319\Performance. Then I restarted the Performance Monitor and everything was fine. A was able to see the missing category again.
We had problems with one of our servers. The mirror was broken. I am talking about the Windows Server Software-RAID (it is a RAID 1, by the way). We had problems restarting the server – it just did not come up again. We had to boot from a “secondary plex”, which usually involved setting up a Lara Console for that server. (Yes, you can adjust in the msconfig which mirror the booting should use.)
I was afraid to do anything with the disks and volume, because I have never done something like that, and I thought I might do something which would crash the server, and leave the hard disks inaccessible. Finally I tackled the problem, and it was quite easy. First off, of course I backed up all the vital data to another server.
At Microsoft TechNet I found a good page describing what I had to do. We had the problem of “Failed Redundancy”. All I had to do was: In the properties-dialog of the volume click “Reactivate Volume”. It then took some time until the disks were synced, but eventually everything was in order again.
The first restart of the server did not work out properly. I do not know why. From the second on, everything was fine.
Hoping that your Disk Management always looks like this:
Cheers, Anton.
