Recent content by manic47

Microsoft should indeed support it - ESX4 is on their list of approved Hypervisors for hosting Microsoft servers.

I'm 100% sure the SAN option only allows you to attach a library to the SAN, and then mount it onto various Backup Exec media servers, thats all. As far as I know, if you just present disk storage to a media server, it can do D2D backups onto it. It wont allow you to backup directly from...

aaah - the joys of dealing with Symantec :) :)

You would normally need an remote agent installed on the NAS to allow it to be backed up. If your Buffalo is capable of running a Backup Exec agent is another question, the little ones we run here can't.

All the ones I've done so far have been pretty straightforward, just an in-place update really, then update the remote agents. You'll need to reboot several times though if I remember correctly.

I'm afraid so - If you are upgrading you may as well go to Backup Exec 12 everywhere though. You'll gain some additional features, for example IDR is included, Windows 2008 and virtual server support etc.

1 - You should find the remote agent in a subfolder where BackupExec is installed - usually agents\raws32 or so. 2 - Have you tried the lastest service pack?

You seem to have a lot of NICs there - do you only have one per vSwitch in the ESX config?

login script ending in .txt? I've been there a few times :)

Have you taken the restrictions off and seen if it runs?

You only need 50 device CALs, these are valid no matter how many servers you are accessing. Per server licencing is no more.... Or you could get 75 user CALs if you want :)

That looks exactly like a SID problem Try running sidgen or ghostwalker if you have it.

You should be able to fit a PCI USB controller in it somewhere.

Are they remote filesystems? Exchange brick-level backups are painfully slow on 10d If it is the backup device generally slow, try new BExec drivers, and try experimenting with different block sizes on the device settings.

Seems not, I think you will need to create a DNS zone for whatever DNS name you have them configured for. If you push out your DNS name via DHCP, you can set DHCP to always update DNS. This is the method we use here and works fine for machines that are not in our AD Domain.