Re: [Veritas-bu] open files to be backed up

[Ed Wilts]

On Mon, Mar 22, 2010 at 10:45 AM, Dustin Damour wrote:

>  I think the technical terms for this is Cold Backup which requires the
> database to be stopped before backup. Hot  Backup is when there is an agent
> or some other software that doesn’t shut down the database, and instead
> takes a snapshot in a point of time while data can be written still after
> snapshot.
>

The key concepts here are crash-consistent or transactionally-consistent.

If you attempt to use a snapshot approach, you'll get a crash-consistent
copy.  Transactions could be in the middle of being applied and it's
possible you'll get half a transaction on disk/tape.  This will not make for
a clean recovery.  Transactionally-consistent database backups are done
either through the of host agents, database-specific tools, or shutting down
the database.

You need to focus the questions on what you want your recovery to look
like.  Don't focus on the BACKUPS - focus on the RECOVERIES.  If you have no
plans to recover, don't bother backing it up in the first place.

Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewi...@ewilts.org
Linkedin 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] open files to be backed up

[Dustin Damour]

I think the technical terms for this is Cold Backup which requires the
database to be stopped before backup. Hot  Backup is when there is an
agent or some other software that doesn't shut down the database, and
instead takes a snapshot in a point of time while data can be written
still after snapshot.  

 

 

Dustin D'Amour

Wireless Switch Technician

Plateau Wireless

575.389.4189 - office

575.309.6372 - cell

dust...@plateautel.com

  <http://www.linkedin.com/in/ikafx> 

 

(\_/)

(O.o)

(> <)

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan,
Patrick
Sent: Monday, March 22, 2010 9:20 AM
To: Lightner, Jeff; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

 

The keyword in your statement is "down". You can backup any database
that is down, their just regular files. It's while the database is
running that the problem arises.

 

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 

 

 



From: Lightner, Jeff [mailto:jlight...@water.com] 
Sent: 22 March 2010 14:37
To: Whelan, Patrick; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] open files to be backed up

I don't know how it works on Windows since we use the SQL agents but on
UNIX/Linux you can backup database files from the filesystem so long as
the database is down at the time you do it.  You can then restore from
that backup to the same filesystems or to an alternate server and/or
filesystems.



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan,
Patrick
Sent: Monday, March 22, 2010 10:10 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

It's not a matter of whether you can or can not backup an open file,
it's the type of open file that you are backing up. If it is a database
file and the database isn't aware that you are backing up its file the
file will not be in a state that the database can use if/when you
restore it. MOST database consist of more than one file so the current
file that is being backed up will be in one state whereas the next file
will be in a different state and so on. So that when the files are
restored they will all be in different "positions" and the database
won't know how to reconcile that difference. Database can be backed up
without agents but the database must be in control of the backup in
order to insure a stable environment for the restore. I hope this makes
sense.

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin,
Jonathan
Sent: 22 March 2010 14:04
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Didn't Curtis' book include some information on backing up databases
without the database agent?

I was waiting for the plug. =P

-Jonathan

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN
ARORA
Sent: Saturday, March 20, 2010 11:01 AM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Thanks for replying...

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"

 Can't these filed be backed up via open file file backup (VSS/VSP)

Regards

Sachin



 

On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz 
wrote:

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them
up if they keep changing when you back them up.  Usually you need a
connector to backup databases.

Justin. 



On Sat, 20 Mar 2010, SACHIN ARORA wrote:

Hi All,

I have a small issue here :


Backup of one of the server is getting partially successfull

Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5.4

Here the files that are not getting backed up :

03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access
the
file because it is being used by another process. )
03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file:

Re: [Veritas-bu] open files to be backed up

[Whelan, Patrick]

The keyword in your statement is "down". You can backup any database
that is down, their just regular files. It's while the database is
running that the problem arises.
 

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 

 



From: Lightner, Jeff [mailto:jlight...@water.com] 
Sent: 22 March 2010 14:37
To: Whelan, Patrick; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] open files to be backed up



I don't know how it works on Windows since we use the SQL agents but on
UNIX/Linux you can backup database files from the filesystem so long as
the database is down at the time you do it.  You can then restore from
that backup to the same filesystems or to an alternate server and/or
filesystems.



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan,
Patrick
Sent: Monday, March 22, 2010 10:10 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

It's not a matter of whether you can or can not backup an open file,
it's the type of open file that you are backing up. If it is a database
file and the database isn't aware that you are backing up its file the
file will not be in a state that the database can use if/when you
restore it. MOST database consist of more than one file so the current
file that is being backed up will be in one state whereas the next file
will be in a different state and so on. So that when the files are
restored they will all be in different "positions" and the database
won't know how to reconcile that difference. Database can be backed up
without agents but the database must be in control of the backup in
order to insure a stable environment for the restore. I hope this makes
sense.

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin,
Jonathan
Sent: 22 March 2010 14:04
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Didn't Curtis' book include some information on backing up databases
without the database agent?

I was waiting for the plug. =P

-Jonathan

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN
ARORA
Sent: Saturday, March 20, 2010 11:01 AM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Thanks for replying...

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"

 Can't these filed be backed up via open file file backup (VSS/VSP)

Regards

Sachin



 

On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz 
wrote:

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them
up if they keep changing when you back them up.  Usually you need a
connector to backup databases.

Justin. 



On Sat, 20 Mar 2010, SACHIN ARORA wrote:

Hi All,

I have a small issue here :


Backup of one of the server is getting partially successfull

Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5.4

Here the files that are not getting backed up :

03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access
the
file because it is being used by another process. )
03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Data.MDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:42 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
(WIN32 32:

Re: [Veritas-bu] open files to be backed up

[Lightner, Jeff]

Right - wasn't saying it was the best way to do things - just that it
could be done.   

 

Here we actually do backups of filesystem mounts of BCV copies of our
main Production (Oracle) DB so don't have to take it down.  

 

We do have a couple of large ancillary DBs such as data warehouse that
can be taken down over weekends so do backups directly from those.

 

I just wasn't sure if it was possible on Windows SQL stuff as I don't
really look at it myself.

 



From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] 
Sent: Monday, March 22, 2010 10:48 AM
To: Lightner, Jeff; Whelan, Patrick; VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] open files to be backed up

 

You can take SQL down (stop the services) - run backup to perform a
"file level" backup, but when you got a 24 x 7 environment, this is not
practical.

 

Best method is to get your SQL Admin to backup the Databased to Disk,
using the built in SQL Backup tool or get the MS-SQL-Server Agent option
license, and apply to your NetBackup environment.

 

Live Database files, or even Personal Email folders that are in use
(like .pst files) cannot be touched correctly.

Once you have got a decent backup of your SQL Files, I would EXCLUDE the
files that NetBackup cannot touch, therefore giving you a STATUS 0 for
your job, rather than STATUS 1 and reporting the same files being
skipped.

 

Sachin - VSP / VSS would not help in this occasion (same as Oracle, SAP,
Exchange, SQL, ect). 

 

Anyhow, get your SQL DBA Administrator to configure the backups inside
SQL Server Express (or Standard, enterprise) and go from there.

 

Regards

Simon

 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
Lightner, Jeff
Sent: Monday, March 22, 2010 2:37 PM
To: Whelan, Patrick; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

I don't know how it works on Windows since we use the SQL agents but on
UNIX/Linux you can backup database files from the filesystem so long as
the database is down at the time you do it.  You can then restore from
that backup to the same filesystems or to an alternate server and/or
filesystems.



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan,
Patrick
Sent: Monday, March 22, 2010 10:10 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

It's not a matter of whether you can or can not backup an open file,
it's the type of open file that you are backing up. If it is a database
file and the database isn't aware that you are backing up its file the
file will not be in a state that the database can use if/when you
restore it. MOST database consist of more than one file so the current
file that is being backed up will be in one state whereas the next file
will be in a different state and so on. So that when the files are
restored they will all be in different "positions" and the database
won't know how to reconcile that difference. Database can be backed up
without agents but the database must be in control of the backup in
order to insure a stable environment for the restore. I hope this makes
sense.

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin,
Jonathan
Sent: 22 March 2010 14:04
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Didn't Curtis' book include some information on backing up databases
without the database agent?

I was waiting for the plug. =P

-Jonathan

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN
ARORA
Sent: Saturday, March 20, 2010 11:01 AM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Thanks for replying...

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"

 Can't these filed be backed up via open file file backup (VSS/VSP)

Regards

Sachin



 

On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz 
wrote:

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them
up if they keep changing when you back them up.  Usually you need a
connector to backup databases.

Justin. 



On Sat, 20 Mar 2010, SACHIN ARORA wrote:

Hi All,

I have a small issue here :


Backup of one of the server is getting partially successfull

Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5

Re: [Veritas-bu] open files to be backed up

[WEAVER, Simon (external)]

You can take SQL down (stop the services) - run backup to perform a
"file level" backup, but when you got a 24 x 7 environment, this is not
practical.
 
Best method is to get your SQL Admin to backup the Databased to Disk,
using the built in SQL Backup tool or get the MS-SQL-Server Agent option
license, and apply to your NetBackup environment.
 
Live Database files, or even Personal Email folders that are in use
(like .pst files) cannot be touched correctly.
Once you have got a decent backup of your SQL Files, I would EXCLUDE the
files that NetBackup cannot touch, therefore giving you a STATUS 0 for
your job, rather than STATUS 1 and reporting the same files being
skipped.
 
Sachin - VSP / VSS would not help in this occasion (same as Oracle, SAP,
Exchange, SQL, ect). 
 
Anyhow, get your SQL DBA Administrator to configure the backups inside
SQL Server Express (or Standard, enterprise) and go from there.
 
Regards
Simon



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
Lightner, Jeff
Sent: Monday, March 22, 2010 2:37 PM
To: Whelan, Patrick; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up



I don't know how it works on Windows since we use the SQL agents but on
UNIX/Linux you can backup database files from the filesystem so long as
the database is down at the time you do it.  You can then restore from
that backup to the same filesystems or to an alternate server and/or
filesystems.



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan,
Patrick
Sent: Monday, March 22, 2010 10:10 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

It's not a matter of whether you can or can not backup an open file,
it's the type of open file that you are backing up. If it is a database
file and the database isn't aware that you are backing up its file the
file will not be in a state that the database can use if/when you
restore it. MOST database consist of more than one file so the current
file that is being backed up will be in one state whereas the next file
will be in a different state and so on. So that when the files are
restored they will all be in different "positions" and the database
won't know how to reconcile that difference. Database can be backed up
without agents but the database must be in control of the backup in
order to insure a stable environment for the restore. I hope this makes
sense.

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin,
Jonathan
Sent: 22 March 2010 14:04
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Didn't Curtis' book include some information on backing up databases
without the database agent?

I was waiting for the plug. =P

-Jonathan

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN
ARORA
Sent: Saturday, March 20, 2010 11:01 AM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Thanks for replying...

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"

 Can't these filed be backed up via open file file backup (VSS/VSP)

Regards

Sachin



 

On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz 
wrote:

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them
up if they keep changing when you back them up.  Usually you need a
connector to backup databases.

Justin. 



On Sat, 20 Mar 2010, SACHIN ARORA wrote:

Hi All,

I have a small issue here :


Backup of one of the server is getting partially successfull

Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5.4

Here the files that are not getting backed up :

03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access
the
file because it is being used by another process. )
03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Data.MDF
(WIN32 32: The process cannot access the file because it is bein

Re: [Veritas-bu] open files to be backed up

[Lightner, Jeff]

I don't know how it works on Windows since we use the SQL agents but on
UNIX/Linux you can backup database files from the filesystem so long as
the database is down at the time you do it.  You can then restore from
that backup to the same filesystems or to an alternate server and/or
filesystems.

 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Whelan,
Patrick
Sent: Monday, March 22, 2010 10:10 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

 

It's not a matter of whether you can or can not backup an open file,
it's the type of open file that you are backing up. If it is a database
file and the database isn't aware that you are backing up its file the
file will not be in a state that the database can use if/when you
restore it. MOST database consist of more than one file so the current
file that is being backed up will be in one state whereas the next file
will be in a different state and so on. So that when the files are
restored they will all be in different "positions" and the database
won't know how to reconcile that difference. Database can be backed up
without agents but the database must be in control of the backup in
order to insure a stable environment for the restore. I hope this makes
sense.

 

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 

 

 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin,
Jonathan
Sent: 22 March 2010 14:04
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

Didn't Curtis' book include some information on backing up databases
without the database agent?

 

I was waiting for the plug. =P

 

-Jonathan

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN
ARORA
Sent: Saturday, March 20, 2010 11:01 AM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

 

Thanks for replying...

 

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"

 Can't these filed be backed up via open file file backup (VSS/VSP)

 

Regards

Sachin



 

On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz 
wrote:

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them
up if they keep changing when you back them up.  Usually you need a
connector to backup databases.

Justin. 



On Sat, 20 Mar 2010, SACHIN ARORA wrote:

Hi All,

I have a small issue here :


Backup of one of the server is getting partially successfull

Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5.4

Here the files that are not getting backed up :

03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access
the
file because it is being used by another process. )
03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Data.MDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:42 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:43 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf
(WIN32
32: The process cannot access the file because it is being used by
another
process. )
03/19/2010 21:31:44 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
(WIN32 32: The process cannot access the file because it is being u

Re: [Veritas-bu] open files to be backed up

[Whelan, Patrick]

It's not a matter of whether you can or can not backup an open file,
it's the type of open file that you are backing up. If it is a database
file and the database isn't aware that you are backing up its file the
file will not be in a state that the database can use if/when you
restore it. MOST database consist of more than one file so the current
file that is being backed up will be in one state whereas the next file
will be in a different state and so on. So that when the files are
restored they will all be in different "positions" and the database
won't know how to reconcile that difference. Database can be backed up
without agents but the database must be in control of the backup in
order to insure a stable environment for the restore. I hope this makes
sense.
 

Regards, 

Patrick Whelan 
NetBackup Specialist 
Wholesale Markets and Treasury & Trading 
Lloyds Banking Group 
Desk: +44 (0) 207 158 6123 
Loc: OBS 2C-132 

 



From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin,
Jonathan
Sent: 22 March 2010 14:04
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up



Didn't Curtis' book include some information on backing up databases
without the database agent?

 

I was waiting for the plug. =P

 

-Jonathan

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN
ARORA
Sent: Saturday, March 20, 2010 11:01 AM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

 

Thanks for replying...

 

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"

 Can't these filed be backed up via open file file backup (VSS/VSP)

 

Regards

Sachin



 

On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz 
wrote:

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them
up if they keep changing when you back them up.  Usually you need a
connector to backup databases.

Justin. 



On Sat, 20 Mar 2010, SACHIN ARORA wrote:

Hi All,

I have a small issue here :


Backup of one of the server is getting partially successfull

Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5.4

Here the files that are not getting backed up :

03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access
the
file because it is being used by another process. )
03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Data.MDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:42 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:43 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf
(WIN32
32: The process cannot access the file because it is being used by
another
process. )
03/19/2010 21:31:44 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:45 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:46 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:59:29 - end writing; write time: 0:58:17
the requested operation was 

Re: [Veritas-bu] open files to be backed up

[Martin, Jonathan]

Didn't Curtis' book include some information on backing up databases
without the database agent?

 

I was waiting for the plug. =P

 

-Jonathan

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of SACHIN
ARORA
Sent: Saturday, March 20, 2010 11:01 AM
To: Justin Piszcz
Cc: VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] open files to be backed up

 

Thanks for replying...

 

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"

 Can't these filed be backed up via open file file backup (VSS/VSP)

 

Regards

Sachin



 

On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz 
wrote:

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them
up if they keep changing when you back them up.  Usually you need a
connector to backup databases.

Justin. 



On Sat, 20 Mar 2010, SACHIN ARORA wrote:

Hi All,

I have a small issue here :


Backup of one of the server is getting partially successfull

Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5.4

Here the files that are not getting backed up :

03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access
the
file because it is being used by another process. )
03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\Audit_DB_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Data.MDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL
Server\MSSQL\Data\crnmr4_Log.LDF
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:42 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:43 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf
(WIN32
32: The process cannot access the file because it is being used by
another
process. )
03/19/2010 21:31:44 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:45 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:31:46 - Warning bpbrm (pid=14837) from client : WRN -
can't
open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf
(WIN32 32: The process cannot access the file because it is being used
by
another process. )
03/19/2010 21:59:29 - end writing; write time: 0:58:17
the requested operation was partially successful (1)

I want these files to be backed up. I tried
Disabled Open file backup and refired backup - -- still didnot backup
these
files
Selcted -- Enabled VSP , Individual drive snapshot, Abort on error --
refired backup -- still didnot backup these files
Selcted -- Enabled VSS , Individual drive snapshot, Abort on error --
refired backup -- still didnot backup these files

Can sombody help me how to get these files to be backed up. its a
production
server , need to fix this quickly

Thanks
Sachin

 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] open files to be backed up

[bob944]

[re: the usual Windows SQL Server MDF and LDF files in use]

>  Can't these filed be backed up via open file file backup
> (VSS/VSP)

Not sure you can back them up even _with_ Windows open file backup
methods--try backing up the perflib stuff.  Microsoft seems to lock
these files with an exclusive write lock that even the volume snap
methods don't get past. 

Even if you could, to what point?  The data are effectively
useless--they are, at best, crash-consistent.  No DBA in his right
mind would think that was an acceptable backup strategy.

Like perfdata* files, I exclude SQL Server (and any other database)
files unless the database will be down and backed up as flat files.


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] open files to be backed up

[judy_hinchcliffe]

You cannot backup a live databse and these are the sql database
You have two options
Buy the netbackup sql database agent to back them up
Or as I do
The sql adin has set up a backup dir
He then schedules sql to do it own backup and up the backup files in that 
backup dir
My normal system backup policy exclides the sql data from backup abd excludes 
the backup dir
I then have a seperate policy that runs at 2 a (a time after I know th backup 
to disk has completed) and this policy just backups the backup dir

Good point about this is that I don't have to know how to backup or restore sql
I just back up or restore files
The sql dba does the restore from the disk files th the actual database



From: veritas-bu-boun...@mailman.eng.auburn.edu 
 
To: VERITAS-BU@mailman.eng.auburn.edu  
Sent: Sat Mar 20 09:34:34 2010
Subject: [Veritas-bu] open files to be backed up 



Hi All,
 
I have a small issue here :
 
 
Backup of one of the server is getting partially successfull
 
Master : Solaris 10 , netbackup 6.5.4
Client : window 2003 , netbackup 6.5.4
 
Here the files that are not getting backed up :
 
03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 
32: The process cannot access the file because it is being used by another 
process. )
03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\Audit_DB_Log.LDF (WIN32 
32: The process cannot access the file because it is being used by another 
process. )
03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\crnmr4_Data.MDF (WIN32 
32: The process cannot access the file because it is being used by another 
process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\crnmr4_Log.LDF (WIN32 
32: The process cannot access the file because it is being used by another 
process. )
03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf (WIN32 32: 
The process cannot access the file because it is being used by another process. 
)
03/19/2010 21:31:42 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf (WIN32 32: 
The process cannot access the file because it is being used by another process. 
)
03/19/2010 21:31:43 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf (WIN32 32: The 
process cannot access the file because it is being used by another process. )
03/19/2010 21:31:44 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf (WIN32 32: 
The process cannot access the file because it is being used by another process. 
)
03/19/2010 21:31:45 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf (WIN32 32: 
The process cannot access the file because it is being used by another process. 
)
03/19/2010 21:31:46 - Warning bpbrm (pid=14837) from client : WRN - can't open 
file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf (WIN32 32: 
The process cannot access the file because it is being used by another process. 
)
03/19/2010 21:59:29 - end writing; write time: 0:58:17
the requested operation was partially successful (1)

I want these files to be backed up. I tried 
Disabled Open file backup and refired backup - -- still didnot backup these 
files
Selcted -- Enabled VSP , Individual drive snapshot, Abort on error -- refired 
backup -- still didnot backup these files
Selcted -- Enabled VSS , Individual drive snapshot, Abort on error -- refired 
backup -- still didnot backup these files

Can sombody help me how to get these files to be backed up. its a production 
server , need to fix this quickly

Thanks
Sachin 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] open files to be backed up

[Ed Wilts]

On Sat, Mar 20, 2010 at 10:01 AM, SACHIN ARORA  wrote:

>
>  Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
> connector to backup databases"
>  Can't these filed be backed up via open file file backup (VSS/VSP)
>

No database can ever be backed up by VSS or VSP - databases need to be
transactionally consistent and an open file agent doesn't guarantee that.

You need an agent - something like the MS SQL agent.  Alternatively, you may
be able to write a script that runs on the client to backup the database to
a disk location and then back up that backup file using NetBackup.  That's
what we do with most of our SQL and Oracle databases

As always, after you've put your backup solution together, test a recovery
of that database and see if it still works.

A Google search for "netbackup sql server express" will certainly help you.

…/Ed

Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] open files to be backed up

[SACHIN ARORA]

Thanks for replying...

 Hovewer, i'm kinda illetrate in this...can you elaborate "you need a
connector to backup databases"
 Can't these filed be backed up via open file file backup (VSS/VSP)

Regards
Sachin



On Sat, Mar 20, 2010 at 9:52 AM, Justin Piszcz wrote:

> Hi,
>
> MDF is a SQL Server Express DB file, you will have problems backing them up
> if they keep changing when you back them up.  Usually you need a connector
> to backup databases.
>
> Justin.
>
>
> On Sat, 20 Mar 2010, SACHIN ARORA wrote:
>
> Hi All,
>>
>> I have a small issue here :
>>
>>
>> Backup of one of the server is getting partially successfull
>>
>> Master : Solaris 10 , netbackup 6.5.4
>> Client : window 2003 , netbackup 6.5.4
>>
>> Here the files that are not getting backed up :
>>
>> 03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL
>> Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access
>> the
>> file because it is being used by another process. )
>> 03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL
>> Server\MSSQL\Data\Audit_DB_Log.LDF
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL
>> Server\MSSQL\Data\crnmr4_Data.MDF
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\crnmr4_Log.LDF
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:31:42 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:31:43 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf
>> (WIN32
>> 32: The process cannot access the file because it is being used by another
>> process. )
>> 03/19/2010 21:31:44 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:31:45 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:31:46 - Warning bpbrm (pid=14837) from client : WRN - can't
>> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf
>> (WIN32 32: The process cannot access the file because it is being used by
>> another process. )
>> 03/19/2010 21:59:29 - end writing; write time: 0:58:17
>> the requested operation was partially successful (1)
>>
>> I want these files to be backed up. I tried
>> Disabled Open file backup and refired backup - -- still didnot backup
>> these
>> files
>> Selcted -- Enabled VSP , Individual drive snapshot, Abort on error --
>> refired backup -- still didnot backup these files
>> Selcted -- Enabled VSS , Individual drive snapshot, Abort on error --
>> refired backup -- still didnot backup these files
>>
>> Can sombody help me how to get these files to be backed up. its a
>> production
>> server , need to fix this quickly
>>
>> Thanks
>> Sachin
>>
>>
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] open files to be backed up

[Justin Piszcz]

Hi,

MDF is a SQL Server Express DB file, you will have problems backing them 
up if they keep changing when you back them up.  Usually you need a 
connector to backup databases.

Justin.

On Sat, 20 Mar 2010, SACHIN ARORA wrote:

> Hi All,
>
> I have a small issue here :
>
>
> Backup of one of the server is getting partially successfull
>
> Master : Solaris 10 , netbackup 6.5.4
> Client : window 2003 , netbackup 6.5.4
>
> Here the files that are not getting backed up :
>
> 03/19/2010 21:31:38 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL
> Server\MSSQL\Data\Audit_DB_Data.MDF (WIN32 32: The process cannot access the
> file because it is being used by another process. )
> 03/19/2010 21:31:39 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\Audit_DB_Log.LDF
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:31:40 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\crnmr4_Data.MDF
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\crnmr4_Log.LDF
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:31:41 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\master.mdf
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:31:42 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\mastlog.ldf
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:31:43 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\model.mdf (WIN32
> 32: The process cannot access the file because it is being used by another
> process. )
> 03/19/2010 21:31:44 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\modellog.ldf
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:31:45 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdbdata.mdf
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:31:46 - Warning bpbrm (pid=14837) from client : WRN - can't
> open file: D:\Program Files\Microsoft SQL Server\MSSQL\Data\msdblog.ldf
> (WIN32 32: The process cannot access the file because it is being used by
> another process. )
> 03/19/2010 21:59:29 - end writing; write time: 0:58:17
> the requested operation was partially successful (1)
>
> I want these files to be backed up. I tried
> Disabled Open file backup and refired backup - -- still didnot backup these
> files
> Selcted -- Enabled VSP , Individual drive snapshot, Abort on error --
> refired backup -- still didnot backup these files
> Selcted -- Enabled VSS , Individual drive snapshot, Abort on error --
> refired backup -- still didnot backup these files
>
> Can sombody help me how to get these files to be backed up. its a production
> server , need to fix this quickly
>
> Thanks
> Sachin
>
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu