Discussion Locked

Backup Exec for Windows NT and 2000 8.5

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Has anyone encountered any problems with the abovementioned package running on Windows 2000? I reinstalled our Backup server with 2000 today, since most of our file servers are being moved to 2000. The problem is as follows:

I cannot launch theBackup Exec console from the local machine, however i can launch it from another machine connecting to the backup server with the Remote Console, and perform all the neccessary tasks. The error is as follows:

"You have insufficient rights to runBackup Exec. You must be a either a backup operator or administrator ro run Backup Exec."

The account that I am logging on with is in both the local Administrators group and the Backup Operators group - and the account is the Administrator of the domain.

The version of Backup Exex is 8.5.

Any suggestions?

Thanx

5 replies

by micktagg

When starting Backup exec it requires a login to start each service automatically go into services and check each bacckupo exec service as to which system /administrator starts the system, then ensure that the Domain Adminstrators group ahas full rights on the Vertasa Folder in the route of C:

by demongp

All the services are started. We use a special account for services, and this account has full admin rights on the domain and on the local server.

I cannot see any Veritas folder on the root? As far as i know t does not create the folder on the root of c:, but well in Program files??? At least this is the way it is in NT server??

by adeal

During the install, BackupExec is normally supposed to create a domain profile on the backup machine with the appropriate backup (and administrator) credentials. Was such an account created on the local machine?

by demongp

I am not sure that i understand your answer. Are you referring to the account it wants to create to start the services with? If so, it did not create its own, since it told it to use a specific User Name, which we use for all our Services (Exchange, SQL etc).

This discussion is closed to new replies.