Stopped a remote Blade for Backup, After backing up....

[Dan Loring]

After backing up a blade I went into the CM, edit Device, Admin, Virtualization, Actions, Start Blade.  It is up and running, I can ping it, but I cannot RDP to the server to verify that it is backup.  It seems like the server is shut down still.  What options do I have to restart this remote virtual server???

[Michael Korenbaum]

If you need to rebuild the VB you can follow the guide here:

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v411/wow/guide/wowguide.html#wp41634

[Dan Loring]

Ok, so after reviewing that article I notoiced that it said there is an iso in the vbs directory.  I noticed that earlier and tried to boot to that, but that would not boot.  Do you think that not only the blade is corrupt, but the iso as well??  Does it sound like something else is going on here or is it common fior the blade and the iso image to get corrupted at the same time??? Also is there a way to check what cd is in the cd drive??

[Michael Korenbaum]

Dan,

That .iso file in the vbs directory was put there by a user, it does not come default when you enable virtual blade.

In your instance it looks like a windows-2003.iso file?

If you can't boot to the iso I suspect that's a bad ISO file. 

If you can't boot to the disk, I suspect it was never installed properly, or was corrupted for some reason.

I don't believe there is a way to view the files in a cdrom.

[Dan Loring]

ok, so I got a new iso out to the device, setup a new server, installed backup client and restoring the server.  So I am back to square one.  I wanted to just back up  the blade so that I could take it out of the backups, because it takes so long.  Initially when I went to backup the blade I shut down the server, stopped the blade and ran the copy ftp virtual blade 1 ..... command to our FTP server.  After doing this it got completely corrupted any thoughts on what went awry, or what I should do differently in the future.  I really do not want to have to keep these servers in our backup schedule, and it is timely to rebuild and restore rather than copying an image over???