Backup Exec 7.01 and SQL 7SP1 
Author Message
 Backup Exec 7.01 and SQL 7SP1
Seagate Backup Exec 7.01 fails when I try to select a SQL 7 server to be
backed up with SQL agent installed.  The message I get is "A database query
failed".  Does anyone have any answers on this one?

Thanks in advance.

-Kevin Evoy



Mon, 22 Jul 2002 03:00:00 GMT
 Backup Exec 7.01 and SQL 7SP1

Kevin - you need the very latest version/patches from Veritas to work with SQL 7 ok

Quote:
> Seagate Backup Exec 7.01 fails when I try to select a SQL 7 server to be
> backed up with SQL agent installed.  The message I get is "A database query
> failed".  Does anyone have any answers on this one?

> Thanks in advance.

> -Kevin Evoy

 Neil Pike MVP/MCSE.  Protech Computing Ltd
 (Please reply only to newsgroups)
 SQL FAQ (412 entries) see

 or www.ntfaq.com/sql.html (+ ntfaq download)
 or http://www.sql-server.co.uk


Tue, 23 Jul 2002 03:00:00 GMT
 Backup Exec 7.01 and SQL 7SP1
I have no faith in BackupExec, we have version 4.2 (if I'm not mistaken) and
it doesn't grab our most important DB. So the option I use is this one:

In SQL terminology you backup a databases to a "backup device", which can be
a file located on your server or another. Once this is done, have BackupExec
grab this backup device (file) and put it to tape. Don't forget to backup
Master, Msdb, Model.

You need to be familiar with SQL Enterprise Mangager. It's a bit of reading
(Books On Line) since you need to know how to backup and do a recovery from
SQL Enterprise Mangager. But that'$ a cheaper $olution to upgrading
BackupExec.

In any case, act fast. A recovery with no valid backup = unemployment.


Quote:
> Kevin - you need the very latest version/patches from Veritas to work with
SQL 7 ok

> > Seagate Backup Exec 7.01 fails when I try to select a SQL 7 server to be
> > backed up with SQL agent installed.  The message I get is "A database
query
> > failed".  Does anyone have any answers on this one?

> > Thanks in advance.

> > -Kevin Evoy

>  Neil Pike MVP/MCSE.  Protech Computing Ltd
>  (Please reply only to newsgroups)
>  SQL FAQ (412 entries) see


http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps

- Show quoted text -

Quote:
>  or www.ntfaq.com/sql.html (+ ntfaq download)
>  or http://www.sql-server.co.uk



Wed, 24 Jul 2002 03:00:00 GMT
 Backup Exec 7.01 and SQL 7SP1
No backup tool is going to backup the .mdf and .ldf files for a database
unless the sql server is shut down. This is because it cannot take a backup
of an open file and sql keeps a lock on those files.  The proper way to do
this is to backup the databases to .BAK files and then backup the .BAK files
with the OS backup utility.
Jaime


Quote:
> I have no faith in BackupExec, we have version 4.2 (if I'm not mistaken)
and
> it doesn't grab our most important DB. So the option I use is this one:

> In SQL terminology you backup a databases to a "backup device", which can
be
> a file located on your server or another. Once this is done, have
BackupExec
> grab this backup device (file) and put it to tape. Don't forget to backup
> Master, Msdb, Model.

> You need to be familiar with SQL Enterprise Mangager. It's a bit of
reading
> (Books On Line) since you need to know how to backup and do a recovery
from
> SQL Enterprise Mangager. But that'$ a cheaper $olution to upgrading
> BackupExec.

> In any case, act fast. A recovery with no valid backup = unemployment.



> > Kevin - you need the very latest version/patches from Veritas to work
with
> SQL 7 ok

> > > Seagate Backup Exec 7.01 fails when I try to select a SQL 7 server to
be
> > > backed up with SQL agent installed.  The message I get is "A database
> query
> > > failed".  Does anyone have any answers on this one?

> > > Thanks in advance.

> > > -Kevin Evoy

> >  Neil Pike MVP/MCSE.  Protech Computing Ltd
> >  (Please reply only to newsgroups)
> >  SQL FAQ (412 entries) see

> http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
> >  or www.ntfaq.com/sql.html (+ ntfaq download)
> >  or http://www.sql-server.co.uk



Fri, 26 Jul 2002 03:00:00 GMT
 Backup Exec 7.01 and SQL 7SP1
Jaime,

Quote:
>No backup tool is going to backup the .mdf and .ldf files for a database
>unless the sql server is shut down.

You are absolutely correct that the files can not be backed up.
However the original question said that they were using the SQL Agent.
Such agents are add-ons to standard third party backup software that
lets them back up SQL Server databases.  What they actually do is
perform database dumps under the covers, with SQL Server sending the
data to a pipe.  At the other end of the pipe is the backup program,
which writes it to the backup.

Roy



Fri, 26 Jul 2002 03:00:00 GMT
 Backup Exec 7.01 and SQL 7SP1
Jaime:

If U use software such as the latest version of Veritas BackUp Exec in
cojunction with its SQL backUp Agent U can backup the .mdf & .ldf files
successfully.

Thx

DW

Quote:
> No backup tool is going to backup the .mdf and .ldf files for a database
> unless the sql server is shut down. This is because it cannot take a
backup
> of an open file and sql keeps a lock on those files.  The proper way to do
> this is to backup the databases to .BAK files and then backup the .BAK
files
> with the OS backup utility.
> Jaime



> > I have no faith in BackupExec, we have version 4.2 (if I'm not mistaken)
> and
> > it doesn't grab our most important DB. So the option I use is this one:

> > In SQL terminology you backup a databases to a "backup device", which
can
> be
> > a file located on your server or another. Once this is done, have
> BackupExec
> > grab this backup device (file) and put it to tape. Don't forget to
backup
> > Master, Msdb, Model.

> > You need to be familiar with SQL Enterprise Mangager. It's a bit of
> reading
> > (Books On Line) since you need to know how to backup and do a recovery
> from
> > SQL Enterprise Mangager. But that'$ a cheaper $olution to upgrading
> > BackupExec.

> > In any case, act fast. A recovery with no valid backup = unemployment.



> > > Kevin - you need the very latest version/patches from Veritas to work
> with
> > SQL 7 ok

> > > > Seagate Backup Exec 7.01 fails when I try to select a SQL 7 server
to
> be
> > > > backed up with SQL agent installed.  The message I get is "A
database
> > query
> > > > failed".  Does anyone have any answers on this one?

> > > > Thanks in advance.

> > > > -Kevin Evoy

> > >  Neil Pike MVP/MCSE.  Protech Computing Ltd
> > >  (Please reply only to newsgroups)
> > >  SQL FAQ (412 entries) see

> > http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
> > >  or www.ntfaq.com/sql.html (+ ntfaq download)
> > >  or http://www.sql-server.co.uk



Sat, 10 Aug 2002 03:00:00 GMT
 Backup Exec 7.01 and SQL 7SP1
Your still taking a risk if you rely on that as your backup.  Restoring the
database backup is a more reliable method than reattaching the files.  If
you can get your .mdf and .ldf, more power to you, but take regular backups
also.

Jaime


Quote:
> Jaime:

> If U use software such as the latest version of Veritas BackUp Exec in
> cojunction with its SQL backUp Agent U can backup the .mdf & .ldf files
> successfully.

> Thx

> DW


> > No backup tool is going to backup the .mdf and .ldf files for a database
> > unless the sql server is shut down. This is because it cannot take a
> backup
> > of an open file and sql keeps a lock on those files.  The proper way to
do
> > this is to backup the databases to .BAK files and then backup the .BAK
> files
> > with the OS backup utility.
> > Jaime



> > > I have no faith in BackupExec, we have version 4.2 (if I'm not
mistaken)
> > and
> > > it doesn't grab our most important DB. So the option I use is this
one:

> > > In SQL terminology you backup a databases to a "backup device", which
> can
> > be
> > > a file located on your server or another. Once this is done, have
> > BackupExec
> > > grab this backup device (file) and put it to tape. Don't forget to
> backup
> > > Master, Msdb, Model.

> > > You need to be familiar with SQL Enterprise Mangager. It's a bit of
> > reading
> > > (Books On Line) since you need to know how to backup and do a recovery
> > from
> > > SQL Enterprise Mangager. But that'$ a cheaper $olution to upgrading
> > > BackupExec.

> > > In any case, act fast. A recovery with no valid backup = unemployment.



> > > > Kevin - you need the very latest version/patches from Veritas to
work
> > with
> > > SQL 7 ok

> > > > > Seagate Backup Exec 7.01 fails when I try to select a SQL 7 server
> to
> > be
> > > > > backed up with SQL agent installed.  The message I get is "A
> database
> > > query
> > > > > failed".  Does anyone have any answers on this one?

> > > > > Thanks in advance.

> > > > > -Kevin Evoy

> > > >  Neil Pike MVP/MCSE.  Protech Computing Ltd
> > > >  (Please reply only to newsgroups)
> > > >  SQL FAQ (412 entries) see

> > > http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
> > > >  or www.ntfaq.com/sql.html (+ ntfaq download)
> > > >  or http://www.sql-server.co.uk



Sun, 11 Aug 2002 03:00:00 GMT
 Backup Exec 7.01 and SQL 7SP1
True!  Always a good idea to use the "belt & Suspenders" approach to
backups!   B-)

Quote:
> Your still taking a risk if you rely on that as your backup.  Restoring
the
> database backup is a more reliable method than reattaching the files.  If
> you can get your .mdf and .ldf, more power to you, but take regular
backups
> also.

> Jaime



> > Jaime:

> > If U use software such as the latest version of Veritas BackUp Exec in
> > cojunction with its SQL backUp Agent U can backup the .mdf & .ldf files
> > successfully.

> > Thx

> > DW


> > > No backup tool is going to backup the .mdf and .ldf files for a
database
> > > unless the sql server is shut down. This is because it cannot take a
> > backup
> > > of an open file and sql keeps a lock on those files.  The proper way
to
> do
> > > this is to backup the databases to .BAK files and then backup the .BAK
> > files
> > > with the OS backup utility.
> > > Jaime



> > > > I have no faith in BackupExec, we have version 4.2 (if I'm not
> mistaken)
> > > and
> > > > it doesn't grab our most important DB. So the option I use is this
> one:

> > > > In SQL terminology you backup a databases to a "backup device",
which
> > can
> > > be
> > > > a file located on your server or another. Once this is done, have
> > > BackupExec
> > > > grab this backup device (file) and put it to tape. Don't forget to
> > backup
> > > > Master, Msdb, Model.

> > > > You need to be familiar with SQL Enterprise Mangager. It's a bit of
> > > reading
> > > > (Books On Line) since you need to know how to backup and do a
recovery
> > > from
> > > > SQL Enterprise Mangager. But that'$ a cheaper $olution to upgrading
> > > > BackupExec.

> > > > In any case, act fast. A recovery with no valid backup =
unemployment.



> > > > > Kevin - you need the very latest version/patches from Veritas to
> work
> > > with
> > > > SQL 7 ok

> > > > > > Seagate Backup Exec 7.01 fails when I try to select a SQL 7
server
> > to
> > > be
> > > > > > backed up with SQL agent installed.  The message I get is "A
> > database
> > > > query
> > > > > > failed".  Does anyone have any answers on this one?

> > > > > > Thanks in advance.

> > > > > > -Kevin Evoy

> > > > >  Neil Pike MVP/MCSE.  Protech Computing Ltd
> > > > >  (Please reply only to newsgroups)
> > > > >  SQL FAQ (412 entries) see

> > > > http://forumsb.compuserve.com/vlforums/UK/default.asp?SRV=MSDevApps
> > > > >  or www.ntfaq.com/sql.html (+ ntfaq download)
> > > > >  or http://www.sql-server.co.uk



Tue, 20 Aug 2002 03:00:00 GMT
 
 [ 8 post ] 

 Relevant Pages 

1. Backup of SQL 2K with Backup Exec 8.6 SQL agent

2. SQL 7.0 Backup and Backup Exec

3. SQL Server backup utility vs Seagate Backup Exec

4. Problems backup up SQL Server 7.0 with Backup Exec

5. Visual Basic 6.0 vs. Visual Dbase 7.01

6. ADO 2.5, ASA 7.01 Problem with LONG VARCHARS

7. Oracle 7.01 problem - HELP

8. IDS 7.3UC2 on SCO Unixware Version 7.01 Hangs everyday

9. Informix 7.30 on SCO Unixware 7.01

10. Informix Version 7.01 (?)


 
Powered by phpBB® Forum Software