Wednesday, September 26, 2012

What is a Blade Server?


A blade server is a stripped-down computer optimized to consume a minimal amount of power and use the available space in a data center as efficiently as possible. Depending on the server vendor's design, server density with blades can be six times higher than that of regular servers.

Because efficiency is an important design goal for blades, only the core server components are on the blade itself. Everything that can be shared between servers is in the blade chassis. A blade cannot be used without the blade chassis, which provides vital functions like power, cooling, etc. If you're investing in a blade chassis, it follows that you don't buy just one blade server: You would buy a chassis to install multiple blades.

Storage usually isn't available on the blade; it's typically provided by a storage area network (SAN). The blade chassis is connected to the SAN and the blades themselves boot from the SAN. As blades normally don't have optical disk drives either, they typically are installed by using installation servers. Putting all this together, using blades makes the data center more efficient, but blades don't make the process of installation and maintenance any easier.

Tuesday, September 25, 2012

Using Portable-VirtualBox to run any OS from a USB device

Oracle VM VirtualBox is open source software for server and desktop virtualization, which means that it can be bent, shaped and reworked in many different ways. Portable-VirtualBox is one trick that lets you run an OS from a USB -- great for testing purposes or whatever else you need.

Oracle VM VirtualBox is included as a standard software package option in many Linux distributions (Ubuntu, for instance), and you can download and run it with very few restrictions. This means VirtualBox can be put to more uses than just running as a desktop application. The best example I've encountered so far is Portable-VirtualBox, a system for repackaging VirtualBox installations that allows a virtualized OS to be booted and run via VirtualBox from a USB drive. The best part is that you don't need a copy of VirtualBox installed on the host PC; VirtualBox runs directly from the drive.

Here's how to install and run Portable-VirtualBox, which allows you the flexibility of running any OS from a USB:

Downloading and installing Portable-VirtualBox
Portable-VirtualBox (P-V) works by downloading a copy of Oracle VM VirtualBox, customizing it according to your instructions, and then packing the resulting files for distribution on a USB drive or other portable media. When you run P-V, all the necessary kernel-level drives are registered and started automatically. When you close P-V, it unregisters everything and cleans up after itself. It's a little like a PortableApps version of VirtualBox.

MORE ON ORACLE VM VIRTUALBOX
Setting up VirtualBox remote display

Recovering VirtualBox VMs

How to create virtual machines with Oracle VM VirtualBox

VirtualBox vs. VMware Workstation

To set up P-V, download the installer and run it. The installer is actually nothing more than a self-extracting archive, which you then unpack into a directory of your choice. Run the program and it will obtain a copy of VirtualBox from Oracle's site, which it then sets up in your directory. If you run the program and it finds a newer version of VirtualBox, you'll be prompted to upgrade. (It will back up the old version in case you discover that the new version doesn't work for you.)

The installer also includes options that allow you to use 32-bit and 64-bit versions of VirtualBox and that provide file compression to use less room on the target media.

When you run Portable-VirtualBox after its local copy of VirtualBox has been set up, it fires up the VirtualBox interface from the full product, but you'll notice a few changes. Press Ctrl+5 and you'll see a pop-up menu that lets you edit settings such as: launching a given virtual machine (VM) by default when the program starts, assigning hotkeys to the VirtualBox interface, starting VirtualBox with or without the USB or network support, and ignoring the "Check for a new version" notice at startup. The rest of Portable-VirtualBox behaves more or less as you would expect it to.

Nuances of Portable-VirtualBox
There are a couple of issues you could encounter with Portable-VirtualBox.

First, if you install P-V on a flash drive and run it from there, the speed of the drive will affect VM performance. Depending on the write speed of the flash drive, saving and restoring the state of the VM can take a very long time -- sometimes even longer than a clean boot of the guest OS. I used a flash drive with 5 MBps sequential write and 25 MBps read, and saving the VM state was agonizingly slow, but restoring it was many times faster than from a spinning drive.

Second, if you run the Portable-VirtualBox packager application on a system where Oracle VM VirtualBox is already installed, it may simply launch your existing edition of VirtualBox. Be sure to unpack and prepare P-V on a system where no copy of VirtualBox is already installed.

Other folks are finding clever ways to make Portable-VirtualBox useful as well. The makers of Linux Live USB, for instance, use P-V to allow Linux distributions to be packaged on USB drives so they can either be booted as a VM in Windows or directly from the USB drive on the host machine itself. The former approach is a great way to try out an OS without having to shut everything down first.

A two-pronged approach to disaster recovery planning for VDI

A VDI outage can have a major effect on the users' ability to do their jobs. With that in mind, you need to approach disaster recovery planning from two angles in a virtual desktop environment.

When it comes to virtual desktop infrastructure (VDI), disaster recovery (DR) planning alone is not enough. An organization that depends on VDI typically can't tolerate the infrastructure going offline. As such, its first priority must be disaster prevention rather than disaster recovery. There's always the chance, however, that a completely unexpected catastrophic event could wipe out the VDI environment, so it's still important to have disaster recovery techniques at your fingertips.

Here's how to take a two-pronged approach to DR through prevention and recovery.

DR preparation starts with prevention
Disaster prevention involves using redundancy to prevent an outage. It's important to use redundant servers, but you should keep an eye on other aspects of your infrastructure that could result in a single point of failure.

MORE ON VDI DISASTER RECOVERY PLANNING
Using VHD backups for VDI disaster recovery

Creating a disaster recovery plan for View desktops

Backup strategies for virtual desktop infrastructure

For example, virtual desktops typically reside on shared storage. The storage array should use a form of redundancy such as RAID 10 to protect against a disk failure or a disk controller failure. It is also a good idea to use redundant connectivity to the shared storage. You wouldn't want a bad host bus adapter to cause your VDI environment to fail.

Backing up VDI servers
Disaster recovery planning for VDI is relatively easy. What helps to simplify VDI disaster recovery is the fact that the underlying servers tend to run a pretty static configuration.

Front-end servers, connection brokers and virtualization host servers are rarely reconfigured aside from routine patch management. So, a good strategy for protecting those servers is to create and test a backup copy of each server. Normally, you don't need to back up the VDI servers on a regular basis unless you're making modifications to them. If you ever have to restore a VDI server, then your patch management server should be able to bring it up to date.

Recovering virtual desktops
Not only do you have to back up servers, but you must also take into account virtual desktop backups. Your VDI project's unique configuration will determine which virtual desktop disaster recovery techniques you'll use.

Most organizations generate virtual desktops from a golden image. Usually, there's no need to back up individual virtual desktops as long as you have a backup copy of the latest golden image.

Keep in mind, however, that with Windows virtual desktops, you'll need to protect user profile data. In most cases, the user profile data is not stored directly within the virtual desktop; it's usually on a file server. Regardless of the location, it's important to back up the user profiles because they contain application-specific settings, Web browser favorites, desktop customizations and in some cases even documents -- all things the user will want back.

Other components you need to protect
As you develop a VDI DR strategy, remember that creating and testing your server and virtual desktop backups is only one aspect of good disaster recovery planning. You must also consider other factors that might stand in the way of recovery. For instance, if a disaster is severe enough to significantly affect your VDI environment, then you'll probably lose some server hardware, too. Make sure you have either spare hardware on hand or a plan for shifting workloads to alternate hardware.

Finally, be sure to adequately back up servers that impact the VDI environment but that may not be technically classified as VDI servers, including infrastructure servers such as domain controllers, DNS servers, Dynamic Host Configuration Protocol servers and enterprise certificate authorities (if you use them). VDI can't function without the services these types of servers provide.

The only way to adequately protect your VDI environment is to use a two-pronged approach. First, use redundancy to prevent a disaster from occurring in the first place. Second, make sure you have reliable backups and a solid virtual desktop disaster recovery plan you can put into place if something does happen to your environment.

Monday, September 24, 2012

How to detach and attach database on SQL Management Studio Express

How to detach and attach database for software on SQL Management Studio Express??

I am using my Test software as ACR


1. Open SQL server management studio express
Break Databases Tree
Right click on ACR
Select properties (Database Properties - ACR dialogue box will open up)
Select Files
Get database file path for ACR.mdf and ACR_log.LDF

2. Right click on ACR and select task
Select detach
Check Drop Connections and Ok (this immediately removes ACR from Databases)

3. Go to database file path
Select and cut ACR.mdf and ACR_log.LDF files
Create a folder (e.g. ABC_ACRSQLData) on the secondary Hard Drive and paste above files

4. Right click on Databases and select attach
Click on Add
Select and break ABC_ACRSQLData
Select ACR.mdf and hit OK


To confirm the change:
Right click on ACR
Select Properties
Select Files
Verify database files path

Sunday, September 16, 2012

First Blog

This is my first Blog, I am not putting anything special here, but I will put my inputs with my day to day issues@work and how I resolved them. Lets Begin today Sun 16th Sept 2012 a marathon of blogs which will help others  resolving similar issues