|
Home > Archive > MS SQL Server > March 2005 > Re: SQL2000 backed by Veritas BackupExec9 on newly migrated W2003
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: SQL2000 backed by Veritas BackupExec9 on newly migrated W2003
|
|
| aabrams 2005-03-31, 8:01 pm |
| Hi Tibor,
Thank you for your posting. I agree, this is not much to go by except that
there is obviously a change in the permissions somewhere that is preventing
BackupExec from accessing the SQL server. Since the backup server to SQL
communication at the OS level is working, I doubt that it is a permission
issue regarding drives, it seems more like either a Veritas SQL client issue
or an issue with SQL server permissions as the Veritas server will backup the
local SQL DB but not the remote SQL server DB. What do you think?
"Tibor Karaszi" wrote:
> This doesn't give us anything to go on. The application (BE) executes some SQL statement which
> fails. We don't know the statement, nor the SQL Server error message. I suggest you talk to Veritas
> about this.
>
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www. solidqualitylearning
.com/
> http://www.sqlug.se/
>
>
> "aabrams" <aabrams@discussions.microsoft.com> wrote in message
> news:8D728A16-E573-4906-99FF- C4D4AFF46478@microso
ft.com...
>
>
>
| |
| Tibor Karaszi 2005-03-31, 8:01 pm |
| Hard to say as I don't really know the BE architecture. Does it have some kind of log? Or perhaps
you can run Profiler and through that try to capture which SQL statement goes wrong (assuming it is
a SQL statement)?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www. solidqualitylearning
.com/
http://www.sqlug.se/
"aabrams" <aabrams@discussions.microsoft.com> wrote in message
news:D79771A6-F14F-4AD5-8BC5- BB3E7AAD148A@microso
ft.com...[color=darkred]
> Hi Tibor,
>
> Thank you for your posting. I agree, this is not much to go by except that
> there is obviously a change in the permissions somewhere that is preventing
> BackupExec from accessing the SQL server. Since the backup server to SQL
> communication at the OS level is working, I doubt that it is a permission
> issue regarding drives, it seems more like either a Veritas SQL client issue
> or an issue with SQL server permissions as the Veritas server will backup the
> local SQL DB but not the remote SQL server DB. What do you think?
>
> "Tibor Karaszi" wrote:
>
|
|
|
|
|