Greetings,
Sorry you are having difficulty with SQL Backup.
The error:
Backup could not access [HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobalEST] running as user [1495823-S12EST1].
Typically indicates a permissions issue.
The log on account of the SQL Backup agent requires access to the registy. Specifically the following keys.
â¢The SQL Backup Pro backup settings registry folder HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\<instance>
â¢The SQL Backup Pro backup settings global registry folder HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<instance>
â¢The Red Gate licensing registry folder HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\Licensing\SQL Backup or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Red Gate\Licensing\SQL Backup (for 64-bit machines).
Please go over the following document on the permissions required for SQL Backup to ensure that you have the necessary permissions.
http://documentation.red-gate.com/display/SBU7/Permissions#
Regarding your issue copying to a network share on a different domain the above link states that you will need to set up matching accounts in each domain.
From the documentation:
"
Working with servers on different Windows domains
If you are working with servers which do not participate in the same Windows domain, you can still use SQL Backup Pro to work with them as usual by setting up "matching accounts". This will be necessary if you want to copy backups to a locked down network share on a different Windows domain, or set up log shipping between servers on different domains.
1.Create accounts on each machine with identical user names and passwords.
2.Set the SQL Backup Agent service to log in to the SQL Server using the account created in step 1, using the sqbsetlogin extended stored procedure. For more information, see Changing the authentication mode above.
When log shipping, the SQL Backup Agent on both SQL Servers must log in using the matched account.
3.Give the account on the other domain access permissions to the relevant locations.
"
Sincerely,
Manfred
Sorry you are having difficulty with SQL Backup.
The error:
Backup could not access [HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobalEST] running as user [1495823-S12EST1].
Typically indicates a permissions issue.
The log on account of the SQL Backup agent requires access to the registy. Specifically the following keys.
â¢The SQL Backup Pro backup settings registry folder HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettings\<instance>
â¢The SQL Backup Pro backup settings global registry folder HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\<instance>
â¢The Red Gate licensing registry folder HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\Licensing\SQL Backup or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Red Gate\Licensing\SQL Backup (for 64-bit machines).
Please go over the following document on the permissions required for SQL Backup to ensure that you have the necessary permissions.
http://documentation.red-gate.com/display/SBU7/Permissions#
Regarding your issue copying to a network share on a different domain the above link states that you will need to set up matching accounts in each domain.
From the documentation:
"
Working with servers on different Windows domains
If you are working with servers which do not participate in the same Windows domain, you can still use SQL Backup Pro to work with them as usual by setting up "matching accounts". This will be necessary if you want to copy backups to a locked down network share on a different Windows domain, or set up log shipping between servers on different domains.
1.Create accounts on each machine with identical user names and passwords.
2.Set the SQL Backup Agent service to log in to the SQL Server using the account created in step 1, using the sqbsetlogin extended stored procedure. For more information, see Changing the authentication mode above.
When log shipping, the SQL Backup Agent on both SQL Servers must log in using the matched account.
3.Give the account on the other domain access permissions to the relevant locations.
"
Sincerely,
Manfred