Backup Strategy : Microsoft Backup or Veritas

I am trying to decide if we should use Microsoft Backup (Database Maintenance
Plans) or use Veritas. We already own Veritas, and the SQL clients.
Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
.BAK file on the SAN. Use the Network install of Veritas (not on SQL svr) to
backup the .BAKs from the SAN. Downside: disk space on SAN is required.
Upside: using standard Microsoft tools. Downside: Need to store more than one
.BAK on the SAN for safety.
Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
tools. Veritas SQL client will backup directly to tape. No space on the SAN
is required.
I am looking for a pros and cons of each to help me make my decision
thank you
ChrisChris
I have no experience with this vendor so I can tell you nothing but based
on lots of years of experience with MS BACKUP strategy I can tell that I
had never problems with it , I mean if you have a proper .BAK (using BACKUP
DATABASE...) file and you attempt to do a RESTORE command you are going to
get a healthy database always
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>I am trying to decide if we should use Microsoft Backup (Database
>Maintenance
> Plans) or use Veritas. We already own Veritas, and the SQL clients.
> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
> to
> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
> Upside: using standard Microsoft tools. Downside: Need to store more than
> one
> .BAK on the SAN for safety.
> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
> tools. Veritas SQL client will backup directly to tape. No space on the
> SAN
> is required.
>
> I am looking for a pros and cons of each to help me make my decision
> thank you
> Chris|||Uri Dimant wrote:
> Chris
> I have no experience with this vendor so I can tell you nothing but based
> on lots of years of experience with MS BACKUP strategy I can tell that I
> had never problems with it , I mean if you have a proper .BAK (using BACKUP
> DATABASE...) file and you attempt to do a RESTORE command you are going to
> get a healthy database always
>
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>> I am trying to decide if we should use Microsoft Backup (Database
>> Maintenance
>> Plans) or use Veritas. We already own Veritas, and the SQL clients.
>> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
>> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
>> to
>> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
>> Upside: using standard Microsoft tools. Downside: Need to store more than
>> one
>> .BAK on the SAN for safety.
>> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
>> tools. Veritas SQL client will backup directly to tape. No space on the
>> SAN
>> is required.
>>
>> I am looking for a pros and cons of each to help me make my decision
>> thank you
>> Chris
>
I agree with Uri. It's quite easy to let SQL server handle the backup in
any way you like and then just backup the backup file. In this way it's
only a regular file backup you need to do and you'll always have a
native SQL server backup file at hand.
An extra plus is that you save the cost of a Veritas SQL server backup
Agent. It might not the the case for you, but in many cases you have to
pay extra to get this agent - just like if you need the Exchange server
Agent.
Regards
Steen

Backup Strategy : Microsoft Backup or Veritas

I am trying to decide if we should use Microsoft Backup (Database Maintenance
Plans) or use Veritas. We already own Veritas, and the SQL clients.
Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
..BAK file on the SAN. Use the Network install of Veritas (not on SQL svr) to
backup the .BAKs from the SAN. Downside: disk space on SAN is required.
Upside: using standard Microsoft tools. Downside: Need to store more than one
..BAK on the SAN for safety.
Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
tools. Veritas SQL client will backup directly to tape. No space on the SAN
is required.
I am looking for a pros and cons of each to help me make my decision
thank you
Chris
Chris
I have no experience with this vendor so I can tell you nothing but based
on lots of years of experience with MS BACKUP strategy I can tell that I
had never problems with it , I mean if you have a proper .BAK (using BACKUP
DATABASE...) file and you attempt to do a RESTORE command you are going to
get a healthy database always
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>I am trying to decide if we should use Microsoft Backup (Database
>Maintenance
> Plans) or use Veritas. We already own Veritas, and the SQL clients.
> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
> to
> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
> Upside: using standard Microsoft tools. Downside: Need to store more than
> one
> .BAK on the SAN for safety.
> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
> tools. Veritas SQL client will backup directly to tape. No space on the
> SAN
> is required.
>
> I am looking for a pros and cons of each to help me make my decision
> thank you
> Chris
|||Uri Dimant wrote:
> Chris
> I have no experience with this vendor so I can tell you nothing but based
> on lots of years of experience with MS BACKUP strategy I can tell that I
> had never problems with it , I mean if you have a proper .BAK (using BACKUP
> DATABASE...) file and you attempt to do a RESTORE command you are going to
> get a healthy database always
>
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>
I agree with Uri. It's quite easy to let SQL server handle the backup in
any way you like and then just backup the backup file. In this way it's
only a regular file backup you need to do and you'll always have a
native SQL server backup file at hand.
An extra plus is that you save the cost of a Veritas SQL server backup
Agent. It might not the the case for you, but in many cases you have to
pay extra to get this agent - just like if you need the Exchange server
Agent.
Regards
Steen

Backup Strategy : Microsoft Backup or Veritas

I am trying to decide if we should use Microsoft Backup (Database Maintenanc
e
Plans) or use Veritas. We already own Veritas, and the SQL clients.
Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
.BAK file on the SAN. Use the Network install of Veritas (not on SQL svr) t
o
backup the .BAKs from the SAN. Downside: disk space on SAN is required.
Upside: using standard Microsoft tools. Downside: Need to store more than on
e
.BAK on the SAN for safety.
Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
tools. Veritas SQL client will backup directly to tape. No space on the SAN
is required.
I am looking for a pros and cons of each to help me make my decision
thank you
ChrisChris
I have no experience with this vendor so I can tell you nothing but based
on lots of years of experience with MS BACKUP strategy I can tell that I
had never problems with it , I mean if you have a proper .BAK (using BACKUP
DATABASE...) file and you attempt to do a RESTORE command you are going to
get a healthy database always
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>I am trying to decide if we should use Microsoft Backup (Database
>Maintenance
> Plans) or use Veritas. We already own Veritas, and the SQL clients.
> Option 1. Do Not use Veritas SQL client. Use Microsoft Backup to produce a
> .BAK file on the SAN. Use the Network install of Veritas (not on SQL svr)
> to
> backup the .BAKs from the SAN. Downside: disk space on SAN is required.
> Upside: using standard Microsoft tools. Downside: Need to store more than
> one
> .BAK on the SAN for safety.
> Option 2. Use Veritas SQL client. Do not use standard Microsoft backup
> tools. Veritas SQL client will backup directly to tape. No space on the
> SAN
> is required.
>
> I am looking for a pros and cons of each to help me make my decision
> thank you
> Chris|||Uri Dimant wrote:
> Chris
> I have no experience with this vendor so I can tell you nothing but bas
ed
> on lots of years of experience with MS BACKUP strategy I can tell that I
> had never problems with it , I mean if you have a proper .BAK (using BACKU
P
> DATABASE...) file and you attempt to do a RESTORE command you are going
to
> get a healthy database always
>
>
> "Chris" <Chris@.discussions.microsoft.com> wrote in message
> news:0DA2F41F-8CF7-4EAB-B0E3-C368D403A947@.microsoft.com...
>
I agree with Uri. It's quite easy to let SQL server handle the backup in
any way you like and then just backup the backup file. In this way it's
only a regular file backup you need to do and you'll always have a
native SQL server backup file at hand.
An extra plus is that you save the cost of a Veritas SQL server backup
Agent. It might not the the case for you, but in many cases you have to
pay extra to get this agent - just like if you need the Exchange server
Agent.
Regards
Steen

Backup Restore question

Hi,
SQL Server 2000 SP3 running on Windows 2000 server
Current Backups:
Daily full backup at 10 PM done by Veritas Netbackup
New Backups that will be setup:
Daily Full backup at 3 AM in the morning
Transaction Log backups every hour.
Now my question is, during a restore from the full backup done at 3 AM how
would the restore from transaction logs be affected by the full backup taking
place at 10 PM?
Thanks in advance.You cannot do a restore to a database that is having a backup done at the
same time - and why would you?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:5C8C825F-D498-48ED-A143-4EAD1FB0066C@.microsoft.com...
Hi,
SQL Server 2000 SP3 running on Windows 2000 server
Current Backups:
Daily full backup at 10 PM done by Veritas Netbackup
New Backups that will be setup:
Daily Full backup at 3 AM in the morning
Transaction Log backups every hour.
Now my question is, during a restore from the full backup done at 3 AM how
would the restore from transaction logs be affected by the full backup
taking
place at 10 PM?
Thanks in advance.|||Also, you will have to the use the previous full backup if you want to
restore the 10 p.m. transaction log backup
Ash
"sharman" wrote:
> Hi,
> SQL Server 2000 SP3 running on Windows 2000 server
> Current Backups:
> Daily full backup at 10 PM done by Veritas Netbackup
> New Backups that will be setup:
> Daily Full backup at 3 AM in the morning
> Transaction Log backups every hour.
> Now my question is, during a restore from the full backup done at 3 AM how
> would the restore from transaction logs be affected by the full backup taking
> place at 10 PM?
> Thanks in advance.
>|||Sorry for not making myself clear. I want to know if I start the new full
backup and the new hourly transaction log backup would I be able to restore
at 11PM with just the 3AM full backup and then restoring the transaction logs
in sequence until 11 PM and just IGNORING the 10 PM full backup.
The reason I ask is because many times during the testing to restore from
the 10 PM backups (that is done by the third party software), I get an error
message and I do not trust that full backup. Therefore I want to set up these
new backups through Enterprise Manager( I have done it this way earlier and I
find them very trustworthy)
Thanks.
"Tom Moreau" wrote:
> You cannot do a restore to a database that is having a backup done at the
> same time - and why would you?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:5C8C825F-D498-48ED-A143-4EAD1FB0066C@.microsoft.com...
> Hi,
> SQL Server 2000 SP3 running on Windows 2000 server
> Current Backups:
> Daily full backup at 10 PM done by Veritas Netbackup
> New Backups that will be setup:
> Daily Full backup at 3 AM in the morning
> Transaction Log backups every hour.
> Now my question is, during a restore from the full backup done at 3 AM how
> would the restore from transaction logs be affected by the full backup
> taking
> place at 10 PM?
> Thanks in advance.
>
>|||Yes, you don't have to use the most recent full backup. You can use a
previous full backup and then all of the logs taken after that point in
time.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:F39EAE37-615B-4AF7-BA67-13C56F34AB0B@.microsoft.com...
Sorry for not making myself clear. I want to know if I start the new full
backup and the new hourly transaction log backup would I be able to restore
at 11PM with just the 3AM full backup and then restoring the transaction
logs
in sequence until 11 PM and just IGNORING the 10 PM full backup.
The reason I ask is because many times during the testing to restore from
the 10 PM backups (that is done by the third party software), I get an error
message and I do not trust that full backup. Therefore I want to set up
these
new backups through Enterprise Manager( I have done it this way earlier and
I
find them very trustworthy)
Thanks.
"Tom Moreau" wrote:
> You cannot do a restore to a database that is having a backup done at the
> same time - and why would you?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> https://mvp.support.microsoft.com/profile/Tom.Moreau
>
> "sharman" <sharman@.discussions.microsoft.com> wrote in message
> news:5C8C825F-D498-48ED-A143-4EAD1FB0066C@.microsoft.com...
> Hi,
> SQL Server 2000 SP3 running on Windows 2000 server
> Current Backups:
> Daily full backup at 10 PM done by Veritas Netbackup
> New Backups that will be setup:
> Daily Full backup at 3 AM in the morning
> Transaction Log backups every hour.
> Now my question is, during a restore from the full backup done at 3 AM
> how
> would the restore from transaction logs be affected by the full backup
> taking
> place at 10 PM?
> Thanks in advance.
>
>

Backup of SQL DB with Veritas Agents

Help!
We just upgraded to version 10d of the Veritas/Symantec software - part of
upgrade was to update the remote backup exec agent that is used to backup SQ
L
db's.
This is the event log entries for the job that fails.
Source MSSQL Server
Event ID 17055
18210 :
BackupVirtualDeviceSet::Initialize: Open failure on backup device
'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'. Operating system error
-2147024891(Access is denied.).
---
Source Backup Exec
Event ID 57859
An error occurred while executing the following query: "BACKUP DATABASE
[master] TO virtual_device =
'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'".
On server: "CD_PA".
SQL error number: "0BC5".
SQL error message: "Backup or restore operation terminating abnormally.
".
For more information, click the following link:
http://eventlookup.veritas.com/even...entLookup.jhtml
The jobs worked until we upgraded... Veritas wants me to make all these
changes... we are only running SQL7.0 no SQL 2000
Anybody have this issue...and had any luck getting it resolved withou
upgrading SQL?
Please advise.
Thanks.
-John
Citigate Cunningham HelpdeskHi
Have you checked account which is running veritas to see whether it has
privileges?
John
"Citigate Cunningham Helpdesk" wrote:

> Help!
> We just upgraded to version 10d of the Veritas/Symantec software - part of
> upgrade was to update the remote backup exec agent that is used to backup
SQL
> db's.
> This is the event log entries for the job that fails.
> Source MSSQL Server
> Event ID 17055
> 18210 :
> BackupVirtualDeviceSet::Initialize: Open failure on backup device
> 'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'. Operating system error
> -2147024891(Access is denied.).
>
> ---
> Source Backup Exec
> Event ID 57859
> An error occurred while executing the following query: "BACKUP DATABASE
> [master] TO virtual_device =
> 'master_00__96b4386f_92d9_42ae_8cd2_0063
0edf161d_'".
> On server: "CD_PA".
> SQL error number: "0BC5".
> SQL error message: "Backup or restore operation terminating abnormally.
> ".
> For more information, click the following link:
> http://eventlookup.veritas.com/even...entLookup.jhtml
> The jobs worked until we upgraded... Veritas wants me to make all these
> changes... we are only running SQL7.0 no SQL 2000
> Anybody have this issue...and had any luck getting it resolved withou
> upgrading SQL?
> Please advise.
> Thanks.
> -John
> Citigate Cunningham Helpdesk
>|||John,
http://support.microsoft.com/defaul...kb;en-us;280759
Veritas has me trying renaming some of the dll's ... I did update the
Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
did not work on the NT40 box.
There were some additonal dlls that it recommended that also get copied
over... this is our finance server... and I don't want to mess it up.
Prior to the upgrade.... from 9.x to 10d it worked fine.
-John
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked account which is running veritas to see whether it has
> privileges?
> John
> "Citigate Cunningham Helpdesk" wrote:
>|||Hi
If you have the disc space you may want to do away with the agent and just
back up to disc. Then you can schedule the normal file backup to put this
onto tape. Unless absolutly necessary I try an avoid using the agents as the
y
can cause so many issues like yours!
John
"Citigate Cunningham Helpdesk" wrote:
[vbcol=seagreen]
> John,
> http://support.microsoft.com/defaul...kb;en-us;280759
> Veritas has me trying renaming some of the dll's ... I did update the
> Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
> did not work on the NT40 box.
> There were some additonal dlls that it recommended that also get copied
> over... this is our finance server... and I don't want to mess it up.
> Prior to the upgrade.... from 9.x to 10d it worked fine.
> -John
> "John Bell" wrote:
>

Backup of SQL DB with Veritas Agents

Help!
We just upgraded to version 10d of the Veritas/Symantec software - part of
upgrade was to update the remote backup exec agent that is used to backup SQL
db's.
This is the event log entries for the job that fails.
Source MSSQL Server
Event ID 17055
18210 :
BackupVirtualDeviceSet::Initialize: Open failure on backup device
'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
-2147024891(Access is denied.).
---
Source Backup Exec
Event ID 57859
An error occurred while executing the following query: "BACKUP DATABASE
[master] TO virtual_device = 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
On server: "CD_PA".
SQL error number: "0BC5".
SQL error message: "Backup or restore operation terminating abnormally.
".
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
The jobs worked until we upgraded... Veritas wants me to make all these
changes... we are only running SQL7.0 no SQL 2000
Anybody have this issue...and had any luck getting it resolved withou
upgrading SQL?
Please advise.
Thanks.
-John
Citigate Cunningham HelpdeskHi
Have you checked account which is running veritas to see whether it has
privileges?
John
"Citigate Cunningham Helpdesk" wrote:
> Help!
> We just upgraded to version 10d of the Veritas/Symantec software - part of
> upgrade was to update the remote backup exec agent that is used to backup SQL
> db's.
> This is the event log entries for the job that fails.
> Source MSSQL Server
> Event ID 17055
> 18210 :
> BackupVirtualDeviceSet::Initialize: Open failure on backup device
> 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> -2147024891(Access is denied.).
>
> ---
> Source Backup Exec
> Event ID 57859
> An error occurred while executing the following query: "BACKUP DATABASE
> [master] TO virtual_device => 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> On server: "CD_PA".
> SQL error number: "0BC5".
> SQL error message: "Backup or restore operation terminating abnormally.
> ".
> For more information, click the following link:
> http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> The jobs worked until we upgraded... Veritas wants me to make all these
> changes... we are only running SQL7.0 no SQL 2000
> Anybody have this issue...and had any luck getting it resolved withou
> upgrading SQL?
> Please advise.
> Thanks.
> -John
> Citigate Cunningham Helpdesk
>|||John,
http://support.microsoft.com/default.aspx?scid=kb;en-us;280759
Veritas has me trying renaming some of the dll's ... I did update the
Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
did not work on the NT40 box.
There were some additonal dlls that it recommended that also get copied
over... this is our finance server... and I don't want to mess it up.
Prior to the upgrade.... from 9.x to 10d it worked fine.
-John
"John Bell" wrote:
> Hi
> Have you checked account which is running veritas to see whether it has
> privileges?
> John
> "Citigate Cunningham Helpdesk" wrote:
> > Help!
> >
> > We just upgraded to version 10d of the Veritas/Symantec software - part of
> > upgrade was to update the remote backup exec agent that is used to backup SQL
> > db's.
> >
> > This is the event log entries for the job that fails.
> >
> > Source MSSQL Server
> > Event ID 17055
> > 18210 :
> > BackupVirtualDeviceSet::Initialize: Open failure on backup device
> > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> > -2147024891(Access is denied.).
> >
> >
> > ---
> >
> > Source Backup Exec
> > Event ID 57859
> >
> > An error occurred while executing the following query: "BACKUP DATABASE
> > [master] TO virtual_device => > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> > On server: "CD_PA".
> > SQL error number: "0BC5".
> > SQL error message: "Backup or restore operation terminating abnormally.
> > ".
> >
> > For more information, click the following link:
> > http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> >
> > The jobs worked until we upgraded... Veritas wants me to make all these
> > changes... we are only running SQL7.0 no SQL 2000
> >
> > Anybody have this issue...and had any luck getting it resolved withou
> > upgrading SQL?
> >
> > Please advise.
> >
> > Thanks.
> >
> > -John
> > Citigate Cunningham Helpdesk
> >|||Hi
If you have the disc space you may want to do away with the agent and just
back up to disc. Then you can schedule the normal file backup to put this
onto tape. Unless absolutly necessary I try an avoid using the agents as they
can cause so many issues like yours!
John
"Citigate Cunningham Helpdesk" wrote:
> John,
> http://support.microsoft.com/default.aspx?scid=kb;en-us;280759
> Veritas has me trying renaming some of the dll's ... I did update the
> Sqlvdi.dll to the 2000 version.. it worked on one server a W2K server but
> did not work on the NT40 box.
> There were some additonal dlls that it recommended that also get copied
> over... this is our finance server... and I don't want to mess it up.
> Prior to the upgrade.... from 9.x to 10d it worked fine.
> -John
> "John Bell" wrote:
> > Hi
> >
> > Have you checked account which is running veritas to see whether it has
> > privileges?
> >
> > John
> >
> > "Citigate Cunningham Helpdesk" wrote:
> >
> > > Help!
> > >
> > > We just upgraded to version 10d of the Veritas/Symantec software - part of
> > > upgrade was to update the remote backup exec agent that is used to backup SQL
> > > db's.
> > >
> > > This is the event log entries for the job that fails.
> > >
> > > Source MSSQL Server
> > > Event ID 17055
> > > 18210 :
> > > BackupVirtualDeviceSet::Initialize: Open failure on backup device
> > > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'. Operating system error
> > > -2147024891(Access is denied.).
> > >
> > >
> > > ---
> > >
> > > Source Backup Exec
> > > Event ID 57859
> > >
> > > An error occurred while executing the following query: "BACKUP DATABASE
> > > [master] TO virtual_device => > > 'master_00__96b4386f_92d9_42ae_8cd2_00630edf161d_'".
> > > On server: "CD_PA".
> > > SQL error number: "0BC5".
> > > SQL error message: "Backup or restore operation terminating abnormally.
> > > ".
> > >
> > > For more information, click the following link:
> > > http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
> > >
> > > The jobs worked until we upgraded... Veritas wants me to make all these
> > > changes... we are only running SQL7.0 no SQL 2000
> > >
> > > Anybody have this issue...and had any luck getting it resolved withou
> > > upgrading SQL?
> > >
> > > Please advise.
> > >
> > > Thanks.
> > >
> > > -John
> > > Citigate Cunningham Helpdesk
> > >

backup history: 3d party vendor

Hello,
It seems that the system table [backupset] does *not* contain backups ma
de by our 3d party backup
tool (Veritas), but only backups made by the SQL Server tools (Q.A., Agent c
ontrolled Tasks...).
Is this true?
How can I query the backup history of the 3d party tool?
(SQL S. 2000)
Thank You
JoachimJoachim
Please refer to
backupfile, backupmediafamily, backupmediaset, backupset, restorefile,
restorefilegroup, and restorehistory.
"Joachim Hofmann" <speicher@.freenet.de> wrote in message
news:4056CD31.45AC9D4B@.freenet.de...
> Hello,
> It seems that the system table [backupset] does *not* contain backups made[/co
lor]
by our 3d party backup
> tool (Veritas), but only backups made by the SQL Server tools (Q.A., Agent
controlled Tasks...).
> Is this true?
> How can I query the backup history of the 3d party tool?
> (SQL S. 2000)
> Thank You
> Joachim|||Uri Dimant wrote:
> Joachim
> Please refer to
> backupfile, backupmediafamily, backupmediaset, backupset, restorefile,
> restorefilegroup, and restorehistory.
Thanks, I think I found the jobs. What really confuses me: The columns with
"software" in their name
always contain 'Microsoft SQL Server', in spite of the backup was made by th
e 'Veritas' Tool.
i.e:
select distinct software_name
from backupmediaset
Joachim