sql backup files: exec

Showing posts with label exec. Show all posts

Saturday, February 25, 2012

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
> > >

Friday, February 24, 2012

backup method question

hi
We are evaluating our backup plans. We currently do a live backup with a
backup exec SQL agent. Thinking about doing it to disk instead without
using veritas, just dumping the database to a file and then backing up
the file. My veritas rep is telling me it will be hard to do a restore
that way.
Is that true? Any other suggestions on backing up?
Thanks
Will
What your Veritas rep is saying is "If you backup to disk, then you won't
need to pay me for an overpriced and underfeatured SQL agent for each
server". Backup to disk and archive to tape is the preferred method for SQL
backups. Make sure you don't backup to the same disk as your data or log
files. I prefer to backup across a dedicated network link to a file server.
That file server is also my tape host so it can backup the files locally.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:u0KoQkAIFHA.1392@.TK2MSFTNGP10.phx.gbl...
> hi
> We are evaluating our backup plans. We currently do a live backup with a
> backup exec SQL agent. Thinking about doing it to disk instead without
> using veritas, just dumping the database to a file and then backing up
> the file. My veritas rep is telling me it will be hard to do a restore
> that way.
> Is that true? Any other suggestions on backing up?
> Thanks
> Will
|||Geoff N. Hiten wrote:
> What your Veritas rep is saying is "If you backup to disk, then you won't
> need to pay me for an overpriced and underfeatured SQL agent for each
> server". Backup to disk and archive to tape is the preferred method for SQL
> backups. Make sure you don't backup to the same disk as your data or log
> files. I prefer to backup across a dedicated network link to a file server.
> That file server is also my tape host so it can backup the files locally.
>
That is kinda what I thought. I am not an SQL guru by any means. I do
more of the plumging. Are there any special considerations to restoring
that file into SQL?
Thanks
Will
|||Hi
I was using backup exec to do the backup of the sql server 2000 database.
It is easy and has good GUI to restore.
But apart from that I did not find any compelling reasons to use it.
I am doing a backup on the USB attached Network drive and it takes about the
same time as taking it on tape.
Mangesh
"Geoff N. Hiten" wrote:

> What your Veritas rep is saying is "If you backup to disk, then you won't
> need to pay me for an overpriced and underfeatured SQL agent for each
> server". Backup to disk and archive to tape is the preferred method for SQL
> backups. Make sure you don't backup to the same disk as your data or log
> files. I prefer to backup across a dedicated network link to a file server.
> That file server is also my tape host so it can backup the files locally.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Will Kubly" <wkubly@.wi.rr.com> wrote in message
> news:u0KoQkAIFHA.1392@.TK2MSFTNGP10.phx.gbl...
>
>
|||SQL backup files are self-contained and self-describing. That is, they
contain all the information required to recreate the database on the
original or any other SQL server. I strongly suggest you read the section
in BOL (Books On-Line) on Backing Up and Restoring Databases in the
Administering SQL Server section. There are some decisions you must make
when you set up a database or there will be painful consequences down the
road. Read and understand this section now, rather than when your system is
down.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:ep68s0AIFHA.560@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Geoff N. Hiten wrote:
won't[vbcol=seagreen]
SQL[vbcol=seagreen]
log[vbcol=seagreen]
server.[vbcol=seagreen]
locally.
> That is kinda what I thought. I am not an SQL guru by any means. I do
> more of the plumging. Are there any special considerations to restoring
> that file into SQL?
> Thanks
> Will

backup method question

hi
We are evaluating our backup plans. We currently do a live backup with a
backup exec SQL agent. Thinking about doing it to disk instead without
using veritas, just dumping the database to a file and then backing up
the file. My veritas rep is telling me it will be hard to do a restore
that way.
Is that true? Any other suggestions on backing up?
Thanks
WillWhat your Veritas rep is saying is "If you backup to disk, then you won't
need to pay me for an overpriced and underfeatured SQL agent for each
server". Backup to disk and archive to tape is the preferred method for SQL
backups. Make sure you don't backup to the same disk as your data or log
files. I prefer to backup across a dedicated network link to a file server.
That file server is also my tape host so it can backup the files locally.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:u0KoQkAIFHA.1392@.TK2MSFTNGP10.phx.gbl...
> hi
> We are evaluating our backup plans. We currently do a live backup with a
> backup exec SQL agent. Thinking about doing it to disk instead without
> using veritas, just dumping the database to a file and then backing up
> the file. My veritas rep is telling me it will be hard to do a restore
> that way.
> Is that true? Any other suggestions on backing up?
> Thanks
> Will|||Geoff N. Hiten wrote:
> What your Veritas rep is saying is "If you backup to disk, then you won't
> need to pay me for an overpriced and underfeatured SQL agent for each
> server". Backup to disk and archive to tape is the preferred method for S
QL
> backups. Make sure you don't backup to the same disk as your data or log
> files. I prefer to backup across a dedicated network link to a file serve
r.
> That file server is also my tape host so it can backup the files locally.
>
That is kinda what I thought. I am not an SQL guru by any means. I do
more of the plumging. Are there any special considerations to restoring
that file into SQL?
Thanks
Will|||Hi
I was using backup exec to do the backup of the sql server 2000 database.
It is easy and has good GUI to restore.
But apart from that I did not find any compelling reasons to use it.
I am doing a backup on the USB attached Network drive and it takes about the
same time as taking it on tape.
Mangesh
"Geoff N. Hiten" wrote:

> What your Veritas rep is saying is "If you backup to disk, then you won't
> need to pay me for an overpriced and underfeatured SQL agent for each
> server". Backup to disk and archive to tape is the preferred method for S
QL
> backups. Make sure you don't backup to the same disk as your data or log
> files. I prefer to backup across a dedicated network link to a file serve
r.
> That file server is also my tape host so it can backup the files locally.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Will Kubly" <wkubly@.wi.rr.com> wrote in message
> news:u0KoQkAIFHA.1392@.TK2MSFTNGP10.phx.gbl...
>
>|||SQL backup files are self-contained and self-describing. That is, they
contain all the information required to recreate the database on the
original or any other SQL server. I strongly suggest you read the section
in BOL (Books On-Line) on Backing Up and Restoring Databases in the
Administering SQL Server section. There are some decisions you must make
when you set up a database or there will be painful consequences down the
road. Read and understand this section now, rather than when your system is
down.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:ep68s0AIFHA.560@.TK2MSFTNGP12.phx.gbl...
> Geoff N. Hiten wrote:
won't[vbcol=seagreen]
SQL[vbcol=seagreen]
log[vbcol=seagreen]
server.[vbcol=seagreen]
locally.[vbcol=seagreen]
> That is kinda what I thought. I am not an SQL guru by any means. I do
> more of the plumging. Are there any special considerations to restoring
> that file into SQL?
> Thanks
> Will

backup method question

hi
We are evaluating our backup plans. We currently do a live backup with a
backup exec SQL agent. Thinking about doing it to disk instead without
using veritas, just dumping the database to a file and then backing up
the file. My veritas rep is telling me it will be hard to do a restore
that way.
Is that true? Any other suggestions on backing up?
Thanks
WillWhat your Veritas rep is saying is "If you backup to disk, then you won't
need to pay me for an overpriced and underfeatured SQL agent for each
server". Backup to disk and archive to tape is the preferred method for SQL
backups. Make sure you don't backup to the same disk as your data or log
files. I prefer to backup across a dedicated network link to a file server.
That file server is also my tape host so it can backup the files locally.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:u0KoQkAIFHA.1392@.TK2MSFTNGP10.phx.gbl...
> hi
> We are evaluating our backup plans. We currently do a live backup with a
> backup exec SQL agent. Thinking about doing it to disk instead without
> using veritas, just dumping the database to a file and then backing up
> the file. My veritas rep is telling me it will be hard to do a restore
> that way.
> Is that true? Any other suggestions on backing up?
> Thanks
> Will|||Geoff N. Hiten wrote:
> What your Veritas rep is saying is "If you backup to disk, then you won't
> need to pay me for an overpriced and underfeatured SQL agent for each
> server". Backup to disk and archive to tape is the preferred method for SQL
> backups. Make sure you don't backup to the same disk as your data or log
> files. I prefer to backup across a dedicated network link to a file server.
> That file server is also my tape host so it can backup the files locally.
>
That is kinda what I thought. I am not an SQL guru by any means. I do
more of the plumging. Are there any special considerations to restoring
that file into SQL?
Thanks
Will|||Hi
I was using backup exec to do the backup of the sql server 2000 database.
It is easy and has good GUI to restore.
But apart from that I did not find any compelling reasons to use it.
I am doing a backup on the USB attached Network drive and it takes about the
same time as taking it on tape.
Mangesh
"Geoff N. Hiten" wrote:
> What your Veritas rep is saying is "If you backup to disk, then you won't
> need to pay me for an overpriced and underfeatured SQL agent for each
> server". Backup to disk and archive to tape is the preferred method for SQL
> backups. Make sure you don't backup to the same disk as your data or log
> files. I prefer to backup across a dedicated network link to a file server.
> That file server is also my tape host so it can backup the files locally.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Will Kubly" <wkubly@.wi.rr.com> wrote in message
> news:u0KoQkAIFHA.1392@.TK2MSFTNGP10.phx.gbl...
> > hi
> >
> > We are evaluating our backup plans. We currently do a live backup with a
> > backup exec SQL agent. Thinking about doing it to disk instead without
> > using veritas, just dumping the database to a file and then backing up
> > the file. My veritas rep is telling me it will be hard to do a restore
> > that way.
> > Is that true? Any other suggestions on backing up?
> >
> > Thanks
> >
> > Will
>
>|||SQL backup files are self-contained and self-describing. That is, they
contain all the information required to recreate the database on the
original or any other SQL server. I strongly suggest you read the section
in BOL (Books On-Line) on Backing Up and Restoring Databases in the
Administering SQL Server section. There are some decisions you must make
when you set up a database or there will be painful consequences down the
road. Read and understand this section now, rather than when your system is
down.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Will Kubly" <wkubly@.wi.rr.com> wrote in message
news:ep68s0AIFHA.560@.TK2MSFTNGP12.phx.gbl...
> Geoff N. Hiten wrote:
> > What your Veritas rep is saying is "If you backup to disk, then you
won't
> > need to pay me for an overpriced and underfeatured SQL agent for each
> > server". Backup to disk and archive to tape is the preferred method for
SQL
> > backups. Make sure you don't backup to the same disk as your data or
log
> > files. I prefer to backup across a dedicated network link to a file
server.
> > That file server is also my tape host so it can backup the files
locally.
> >
> That is kinda what I thought. I am not an SQL guru by any means. I do
> more of the plumging. Are there any special considerations to restoring
> that file into SQL?
> Thanks
> Will

Saturday, February 25, 2012

Backup of SQL DB with Veritas Agents

Backup of SQL DB with Veritas Agents

Friday, February 24, 2012

backup method question

backup method question

backup method question

sql backup files

Blog Archive

About Me