I started my day with building a 2008 R2 server on a test server I have.
I tried to load Symantec backup Exec 11d onto the server and it wouldnt install giving a compatiblity error. So I double checked and I was infact using the 32bit CD so i swapped it and the same problem wont work.
So I said work around. I installed Hyper-V and installed windows 2003 R2 server and then installed Backup Exec onto it. After an hour of updating my backup exec was working fine.
I then decided to try do a restore and found my VM wouldnt find the HP LTO4 drive.
I double checked the hyper-v manager SCSI cards are definitely added. I removed them added them again.. still nothing.
So I posted it on Twitter and then started Googling. My good friend and MVP Aidan finn found the first post but he knew already himself... backup tape drives dont work that way with hyper-V. What a pain I cant just do a restore using the SCSI card on the server to a VM running backup Exec.
I'm yet to find a solution but its looking like I'm going to have to drop back to windows 2003 server and do the restore or do the restore on a different legacy box and then move the data to the more powerful test server.
Subscribe to:
Post Comments (Atom)
Part of the roadblock you ran into here had to do with the fact that you can only backup Windows 2008 R2 with Backup Exec 12.5 and the following hotfix:
ReplyDeletehttp://seer.entsupport.symantec.com/docs/335868.htm
You should also notice in that KB article that you can only back it up remotely, you can't install BE 12.5 on 2008 R2 as a media server. The next release of Backup Exec (BE 2010) will support 2008 R2 as a media server.
With 12.5 and the hotfix you would also have the option of backing up the 2008 R2 machine as a VM (remotely), provided you have the Microsoft VM option/license (agent for Microsoft Virtual Servers).