Here is a part of my log :

Here is an excerpt from the logs. The strange thing is I'm going to disk and 
not tape for this backup.

07.09.2006 13:23:21      ANR0513I Process 79 opened output volume               
   
                          /tsmadsmdbbkp/57649801.DBB. (SESSION: 2880, PROCESS: 
79) 
07.09.2006 13:23:21      ANR1360I Output volume /tsmadsmdbbkp/57649801.DBB 
opened  
                          (sequence number 6). (SESSION: 2880, PROCESS: 79)     
   
07.09.2006 13:23:37      ANR4554I Backed up 6690752 of 7901681 database pages.  
   
                          (SESSION: 2880, PROCESS: 79)                          
   
07.09.2006 13:24:07      ANR4554I Backed up 6954624 of 7901681 database pages.  
   
                          (SESSION: 2880, PROCESS: 79)                          
   
07.09.2006 13:24:37      ANR4554I Backed up 7205312 of 7901681 database pages.  
   
                          (SESSION: 2880, PROCESS: 79)                          
   
07.09.2006 13:25:07      ANR4554I Backed up 7368704 of 7901681 database pages.  
   
                          (SESSION: 2880, PROCESS: 79)                          
   
07.09.2006 13:25:17      ANR8785E Out-of-space in file system for FILE volume   
   
                          /tsmadsmdbbkp/57649801.DBB. (SESSION: 2880, PROCESS: 
79) 
07.09.2006 13:25:18      ANR4573E Database backup terminated - excessive write  
   
                          errors encountered. (SESSION: 2880, PROCESS: 79)      
   

I know DB backups do not lock nodes. I was wondering whether the nodes should 
be locked before the database backup was taken.

Rich

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Prather, Wanda
Sent: Friday, September 08, 2006 10:56 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Database backup during day


NO, "excessive write failures" is NOT a normal result of a DB backup,
even during times of very high contention.

Look carefully at the errors in your activity log to figure out why, or
send us the EXACT messages
.
DB backups don't "lock" nodes.



  

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Mochnaczewski
Sent: Friday, September 08, 2006 10:45 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Database backup during day

Hi Everybody,

We are looking into scheduling a database backup during the day as the
last database backup we have for our nightly process is done at around
4:00 AM in the morning. If something should happen in the afternoon,
then we can go back to the latest database backup  which we would have
go to disk as our database backup from the morning would be offsite.
I've tried running a database backup during the day but it constantly
fails with an error regarding excessive write failures. Is this because
the nodes are not locked ? If they need to be locked, doesn't that cause
contention if a backup/restore request is made by a client ?

Rich