Le lundi 4 décembre 2006 15:17, John Drescher a écrit :
> ---------- Forwarded message ----------
> From: John Drescher <[EMAIL PROTECTED]>
> Date: Dec 4, 2006 9:17 AM
> Subject: Re: [Bacula-users] How to understand this error
> To: Arnaud Mombrial <[EMAIL PROTECTED]>
>
> I'm afraid Things go wrong with my monthly backup.
>
> > I use a Sony SAIT1-500 Cartridge and don't know if compression is active
> > or
> > not.
> >
> > Here is a sample of /var/log/bacula/bacula.log.1 :
> >
> > ##########################################
> > #
> > # I've only post the parts that are relevant to my Sony SDZ-100 device
> > #
> > # I've add some comments for myself to check if I understand well
> > # what Bacula tells me
> > #
> > ##########################################
> >
> > # Job Name
> >
> > 03-Dec 01:00 Backup: Start Backup JobId 2247,
> > Job=server-compta-archive.2006-12-03_01.00.00
> >
> > # Before job's actions for the Win Server :
> >
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob:
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob: C:\WINDOWS\system32>REM
> > STOP
> > MSSQL SERVEUR 2000
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob:
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob: C:\WINDOWS\system32>NET
> > STOP "SQLSERVERAGENT"
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob: Le service SQLSERVERAGENT
> > s'arrte.
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob: Le service SQLSERVERAGENT
> > a t
> > arrt.
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob:
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob:
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob: C:\WINDOWS\system32>NET
> > STOP "MSSQLServer"
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob: Le service MSSQLSERVER
> > s'arrte..
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob: Le service MSSQLSERVER a
> > t arrt.
> > 03-Dec 01:00 server-compta: ClientRunBeforeJob:
> >
> > # The previous Error I mentioned in the last Post
> > # Quote :  "John Drescher" < [EMAIL PROTECTED]>
> > # I believe I have this error with every drive I have when a new blank
> > tape is
> > # inserted basically
> > # this means that bacula tried to read a tape with no data on it and that
> > was
> > # an error.
> >
> > 03-Dec 01:00 Storage: server-compta-archive.2006-12-03_01.00.00 Error:
> > block.c:940 Read error at file:blk 0:0 on device "Sony SDZ-100"
> > (/dev/st0).
> > ERR=Input/output error.
>
> As I said  before this is normal during the label command if the tape is
> blank.
>
> # A label Archives.3 is created
>
> > # I've to check what is a label... Sorry for being anoying
>
> Every tape that bacula uses must be labeled so bacula can identify it so it
> will not overwrite
> your important data.
>
> 03-Dec 01:01 Storage: Labeled new Volume "archives.3" on device "Sony
>
> > SDZ-100"
> > (/dev/st0).
> > 03-Dec 01:01 Storage: Wrote label to prelabeled Volume "archives.3" on
> > device "Sony SDZ-100" (/dev/st0)
> > 03-Dec 01:01 Storage: Spooling data ...
> > 03-Dec 01:59 Storage: Committing spooled data to Volume " archives.3".
> > Despooling 28,217,078,749 bytes ...
> > 03-Dec 02:17 Storage: Sending spooled attrs to the Director. Despooling
> > 14,492,414 bytes ...
> >
> > # After job's actions for the Win Server :
> >
> > 03-Dec 02:17 server-compta: ClientRunAfterJob:
> > 03-Dec 02:17 server-compta: ClientRunAfterJob: C:\WINDOWS\system32>REM
> > DEM MSSQL SERVEUR 2000
> > 03-Dec 02:17 server-compta: ClientRunAfterJob:
> > 03-Dec 02:17 server-compta: ClientRunAfterJob: C:\WINDOWS\system32>NET
> > START "MSSQLServer"
> > 03-Dec 02:17 server-compta: ClientRunAfterJob: Le service MSSQLSERVER
> > dmarre...
> > 03-Dec 02:17 server-compta: ClientRunAfterJob: Le service MSSQLSERVER a
> > dmarr.
> > 03-Dec 02:17 server-compta: ClientRunAfterJob:
> > 03-Dec 02:17 server-compta: ClientRunAfterJob:
> > 03-Dec 02:17 server-compta: ClientRunAfterJob: C:\WINDOWS\system32>NET
> > START "SQLSERVERAGENT"
> > 03-Dec 02:17 server-compta: ClientRunAfterJob: Le service SQLSERVERAGENT
> > dmarre.
> > 03-Dec 02:17 server-compta: ClientRunAfterJob: Le service SQLSERVERAGENT
> > a dmarr.
> > 03-Dec 02:17 server-compta: ClientRunAfterJob:
> >
> > # Here is the description of the Job ?
> >
> > 03-Dec 02:17 Backup: Bacula 1.38.5 (18Jan06): 03-Dec-2006 02:17:55
> >   JobId:                  2247
> >   Job:                    server-compta-archive.2006-12-03_01.00.00
> >   Backup Level:           Full
> >   Client:                 "server-compta" Windows Server 2003,MVS,NT
> > 5.2.3790
> >   FileSet:                "server-compta-archive" 2006-07-02 01:00:02
> >   Pool:                   "archives"
> >   Storage:                "Sony SDZ-100"
> >   Scheduled time:         03-Dec-2006 01:00:00
> >   Start time:             03-Dec-2006 01:00:02
> >   End time:               03-Dec-2006 02:17:55
> >   Priority:               40
> >   FD Files Written:       39,595
> >   SD Files Written:       39,595
> >   FD Bytes Written:       28,182,421,035
> >   SD Bytes Written:       28,189,631,833
> >   Rate:                   6030.9 KB/s
> >   Software Compression:   None
> >   Volume name(s):         archives.3
> >   Volume Session Id:      11
> >   Volume Session Time:    1164994961
> >   Last Volume Bytes:      28,211,831,006
> >   Non-fatal FD errors:    0
> >   SD Errors:              0
> >   FD termination status:  OK
> >   SD termination status:  OK
> >   Termination:            Backup OK
> >
> > 03-Dec 02:17 Backup: Begin pruning Jobs.
> > 03-Dec 02:17 Backup: No Jobs found to prune.
> > 03-Dec 02:17 Backup: Begin pruning Files.
> > 03-Dec 02:17 Backup: No Files found to prune.
> > 03-Dec 02:17 Backup: End auto prune.
> >
> > # End of Win Server 2003 Backup
> >
> > # Here is the problem
> >
> > 03-Dec 02:17 Backup: Start Backup JobId 2248,
> > Job=server-prod-archive.2006-12-03_01.00.01
> > 03-Dec 02:17 Storage: Spooling data ...
> > 03-Dec 05:47 Storage: Writing spooled data to Volume. Despooling
> > 145,884,180,936 bytes ...
> > 03-Dec 10:59 Storage: Writing spooled data to Volume. Despooling
> > 145,883,986,933 bytes ...
> > 03-Dec 16:03 Storage: Writing spooled data to Volume. Despooling
> > 145,883,986,714 bytes ...
> > 03-Dec 21:09 Storage: Writing spooled data to Volume. Despooling
> > 145,883,922,757 bytes ...
> > 03-Dec 22:21 Storage: End of Volume "archives.3" at 583:14505 on device
> > "Sony
> > SDZ-100" (/dev/st0). Write of 64512 bytes got -1.
> > 03-Dec 22:21 Storage: Re-read of last block succeeded.
> > 03-Dec 22:21 Storage: End of medium on Volume "archives.3"
> > Bytes=583,112,177,708 Blocks=9,038,818 at 03-Dec-2006 22:21.
>
> This says the tape is full and has 583Gb on it. Have you used this tape for
> other jobs?
>
> BTW, You can type
>
> list media
>
> in bconsole to show all your tapes and how much is written to each one.
>
> # A label Archives.4 is created
>
> > 03-Dec 22:23 Backup: Created new Volume "archives.4" in catalog.
> > 03-Dec 22:23 Storage: Please mount Volume "archives.4" on Storage Device
> > "Sony
> > SDZ-100" (/dev/st0) for Job server-prod-archive.2006-12-03_01.00.01
> > 03-Dec 23:23 Storage: Please mount Volume "archives.4" on Storage Device
> > "Sony
> > SDZ-100" (/dev/st0) for Job server-prod-archive.2006-12-03_01.00.01
> > 04-Dec 01:23 Storage: Please mount Volume " archives.4" on Storage Device
> > "Sony
> > SDZ-100" (/dev/st0) for Job server-prod-archive.2006-12-03_01.00.01
> > 04-Dec 05:24 Storage: server-prod-archive.2006-12-03_01.00.01 Warning:
> > Director wanted Volume " archives.4".
> >     Current Volume "archives.3" not acceptable because:
> >     1998 Volume "archives.3" status is Full, but should be Append, Purged
> > or
> > Recycle.
> > 04-Dec 05:24 Storage: Please mount Volume " archives.4" on Storage Device
> > "Sony
> > SDZ-100" (/dev/st0) for Job server-prod-archive.2006-12-03_01.00.01
> > 04-Dec 05:24 Storage: Please mount Volume "archives.4" on Storage Device
> > "Sony
> > SDZ-100" (/dev/st0) for Job server-prod-archive.2006-12-03_01.00.01
> >
> > So here is my problem.
> >
> > The tape, as said before is a 500 Gb SAIT1. How can it be full, as the
> > server-compta-archive.2006-12-03_01.00.00 job did only take
> > 28,182,421,035 Bytes ?
>
> Here is the Disk Usage output on the bacula server :
> > server-backup:/home/bacula# du --max-depth=1 -h
> >
> > 16K     ./lost+found
> > 61G     ./postes
> > 1.8T    ./server-prod
> > 132G    ./server-compta
> > 136G    ./spool
> > 3.5G    ./firewall
> > 2.7G    ./server-printer
> > 2.0G    ./server-ldap
> > 2.0G    ./catalog
> > 2.2T    .
> >
> > Another Question : Why did the job backup only 28 Gbytes, instead of the
> > full
> > 132 G mentioned ?
>
> Do you have more than one filesystem mounted ? bacula by default will not
> cross filesystem
> boundries.
>
> Last question, how to know the % used on this kind of tape, since a basic
>
> > command like mt -f /dev/st0 gives a device busy
>
> There is a setting in the bacula-sd.conf file that tells bacula to always
> keep the drive open. If this is on
> you can not do any mt commands while the bacula-sd daemon is running.
>
> John

Ok, so the Output of 
* list media is 
Pool: archives
+---------+------------+-----------+-----------------+----------+--------------+---------+------+-----------+-----------+---------------------+
| MediaId | VolumeName | VolStatus | VolBytes        | VolFiles | 
VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten         |
+---------+------------+-----------+-----------------+----------+--------------+---------+------+-----------+-----------+---------------------+
|     233 | archives.0 | Used      | 339,987,772,181 |      341 |   
15,552,000 |       1 |    0 |         0 | SAIT      | 2006-07-09 13:09:24 |
|     254 | archives.1 | Used      | 395,273,517,833 |      396 |   
15,552,000 |       1 |    0 |         0 | SAIT      | 2006-08-13 15:12:19 |
|     261 | archives.2 | Used      | 453,631,722,444 |      455 |   
15,552,000 |       1 |    0 |         0 | SAIT      | 2006-09-10 17:12:25 |
|     265 | archives.3 | Full      | 583,112,113,196 |      584 |   
15,552,000 |       1 |    0 |         0 | SAIT      | 2006-12-03 22:21:46 |
|     293 | archives.4 | Append    |  27,998,143,255 |       28 |   
15,552,000 |       1 |    0 |         0 | SAIT      | 2006-12-04 13:41:33 |
+---------+------------+-----------+-----------------+----------+--------------+---------+------+-----------+-----------+---------------------+

Sorry for the format but it is said on MediaID 293 that there's only 27 Gb 
written on the Tape I've changed today. The Disk Space of this server has 
changed since this morning and I'm happy with it. 

Now, I just want to unmount the device with the "unmount" command as I think 
the job is now definitely completed, but bacula tells me :

3937 Device "Sony SDZ-100" (/dev/st0) is busy with 1 writer(s).

My questions are :

How to know a job is ended ? 
Is there a way to tell Bacula to use a compression something for the tape, 
since they are 1.300 Gbytes capable ?

Again, sorry for all this noise, but I'm really new with Bacula, this server 
is in use since a long time and No one in my job can tell me what to do with 
it ....

Regards

-- 
Arnaud Mombrial
T : +33 141 123 041
F : +33 141 123 001
[EMAIL PROTECTED]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to