Backup Exec 2012 - a step backwards

[Sheridan]

I've used Backup Exec for years and recently have bought 2012 SBE for our new 2008 Server. We backup to a local tape and also to a share on a NAS box.

 

On all the older versions of BE, I simply give write permissions to the network account I use as the system account and it works fine. BE 2012 just doesn't work like that - it doesn't seem to be able to access the share using the same credentials all the other servers user, and seems to try and use the local system account to connect, which is completely useless!

 

Anyone else got BE 2012 connecting to a NAS for backup? I'm expecting to install an older copy instead as symantecs support is non existent.

[RabbieBurns]

just add SYSTEM to the network share permissions?

[Sheridan]

It doesn't work quite like that - the NAS box is AD linked and a specific AD account is used for all backups. This account has full permissions on the NAS and is the system account on all the BE servers - its just the 2012 edition that doesn't work. All the other versions from 9.0 to 2010 are working ok.

 

Mind the 2012 version is an utter pile, awful menus and bug ridden! It even declares a mapped network drive can't be used as its a 'CDRom'!

[RabbieBurns]

you can change the account that is used under Test/Edit Credentials of a backup job:

 

Edited November 26, 2012 by RabbieBurns

[Sheridan]

I can't even create the disk though - the backups are all set to use the system account (which is the ad account with the permissions)

 

So it fails to authenticate with the nas box which prevents me from even creating a backup to disk job! Tape jobs work fine but 2012 can't cope with the nas. A total step backwards from the previous version which I've been backing up to nas for years.

[Michael]

This is somewhat odd I have to agree. Sheridan's right about the local vs domain account issue. If the server is a Domain Controller, local accounts no longer exist. They're only available in Directory Services Restore Mode.

 

I'd suggest you get onto their support and download any available software patches.

[Michael]

For your reference Sheridan, I use Backup Assist 6.3 on Windows Server 2008 R2. Works absolutely fine

[Sheridan]

Thanks! I've used BE for years though and the nas thing has been fine until this nasty buggy 2012 release. I might try and downgrade the license but I need the SQL server part to backup an MIS database!

[Michael]

Backup Assist also has an optional database backup module too (if you decide to give up with Backup Exec).

[glennda]

Thanks! I've used BE for years though and the nas thing has been fine until this nasty buggy 2012 release. I might try and downgrade the license but I need the SQL server part to backup an MIS database!

 

Backup Exec 2012 is terrible, for virtual (Vmware/Hyper-V) environments Veeam is brilliant.

 

With regards to the SQL Agent are you running Sims?

[Sheridan]

Yes, SIMS will be on this server hence the SQL agent. Now I need to try and get a refund for this pile of poo that is BE 2012!

[Duke5A]

Yes, SIMS will be on this server hence the SQL agent. Now I need to try and get a refund for this pile of poo that is BE 2012!

 

Note to self, do not upgrade BE.

[glennda]

Yes, SIMS will be on this server hence the SQL agent. Now I need to try and get a refund for this pile of poo that is BE 2012!

 

You don't need the sql agent. You can simple schedule a task within sql to backup the data, you can then backup these backup files.