Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL 2000, Advanced Server, BE not able to attach to SQL

Status
Not open for further replies.

htoth

MIS
Jan 25, 2001
22
US
Greetings,

I am trying to back up SQL 2000 databases from Backup Exec v.8.6. I am constantly getting the box that wants a user name and password. No matter what account I enter, and I have double checked the passwords on all of them, it wont' accept it. The backup account has sql admin rights to the databases, is a member of the domain admins group, and it has explicitly defined rights to the folders where the databases are.

The event log says "SQL error number 4818" and SQL error message "Login failed for user backupexec"

I have applied all service packs to both sql and w2k, it seems to have made no difference. For a while the sql enterprise manager was also unable to register the two sql boxes I am trying to back up, but I entered the IP addresses and it was able to register them. however, the Backup Exec program is still unable to attach to the MS SQL Server checkbox.

Any help would be greatly appreciated.

Heather
 
Heather

Have you tried the SA account yet? If that don't work, try the following:

Stop Backup Exec Services, go to the directory where Backup Exec is installed down to the Data folder. There you will find the Bewinui.uni file. This is the password database file. Rename this to .old and restart the services. In Backup Selections, highlight the SQL server and go to the Network menu. Select "Default Attach Info" and type in the Account you want to use. You can also use the SA account.
You should now be able to backup your sql server.

Tilo
 
Most definitely use the sa account. I had the same problem, and other problems until I used that account to log into my SQL Server 2000 installation.

Now, everything is spiffy.
 
CHEAT!

Drop the SQL agent. Use SQL 2000 backups to dump to disk then use remote agent to backup the text files from the backup folder. Much safer and faster. None disaster = restore from disk to SQL. DR = restore from tape to disk then restore from disk.

Real easy, been using it since SQL 6.5...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top