- Posts: 1
- Liked: never
- Joined: May 28, 2010 6:18 am
- Full Name: Stadt Zirndorf, EDV
This is how I did it:
Create a new local windows-user "veeam", password: "xxx"
Not member of administrators, a simple user.
Windows service "Veeam Backup and FastSCP Service", Login not as User ".\administrator" but as user "veeam" now, you have to tell windows the password from above. Stop and start service.
Now user "veeam" is not allowed to communicate with SQL Express 2005 which was installed with Veeam Backup software. Give user "veeam" the right to deal with the database as needed:
Open command line window with: Start - cmd
c:\> sqlcmd -S .\VEEAM -E
List all databases:
1> EXEC sp_databases
> VeeamBackup <<<<<<<<<<<<<< this is it!
1> CREATE LOGIN [fw-backupserver\veeam] FROM WINDOWS
1> USE VeeamBackup
1> select DB_NAME()
1> EXEC sp_changedbowner 'fw-backupserver\veeam'
Start the program "Veeam Backup and FastSCP" and start a backup job to test wether it worked well.
- Product Manager
- Posts: 23858
- Liked: 1751 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Users browsing this forum: Google [Bot] and 22 guests