Bacula-users

Re: [Bacula-users] Problem or trouble??

2009-05-26 07:29:26
Subject: Re: [Bacula-users] Problem or trouble??
From: Arno Lehmann <al AT its-lehmann DOT de>
To: bacula-users AT lists.sourceforge DOT net
Date: Tue, 26 May 2009 13:22:22 +0200
Hello,

26.05.2009 12:47, Personal Técnico wrote:
> Hi,
> 
> I have got some importants problems that have caused to me a big 
> trouble... Well, a client was doing a scheduled backup when, with no 
> reason, backup finished with error:
> 
> 25-May 13:04 aosnap JobId 6804: User defined maximum volume capacity 
> 15,000,000,000 exceeded on device "BaculaBackups" (/backups).
> 25-May 13:04 aosnap JobId 6804: End of medium on Volume 
> "Backup-Cliente0242" Bytes=14,999,937,740 Blocks=232,520 at 25-May-2009 
> 13:04.
> 25-May 13:04 aosnap JobId 6804: Volume "Backup-Cliente0258" previously 
> written, moving to end of data.
> 25-May 13:04 aosnap JobId 6804: Error: Bacula cannot write on disk 
> Volume "Backup-Cliente0258" because: The sizes do not match! 
> Volume=3216612453 Catalog=2999808151

This might indicate a disk full condition or even a file system or 
hardware corruption. You'd do well to make sure you don't lose data - 
if it's not a disk space problem, unmount the disk, use dd_recover to 
get an image of the disk, and keep the original disk safe for now.

> 25-May 13:04 aosnap JobId 6804: Marking Volume "Backup-Cliente0258" in 
> Error in Catalog.
> 25-May 13:04 aosnap JobId 6804: Warning: Unable add Scratch Volume, Pool 
> "Cliente" full MaxVols=2
> 25-May 13:04 aosnap JobId 6804: Purging oldest volume "Backup-Cliente0242"
> 25-May 13:04 aosnap JobId 6804: 3 Files on Volume "Backup-Cliente0242" 
> purged from catalog.
> 25-May 13:04 aosnap JobId 6804: Warning: Unable add Scratch Volume, Pool 
> "Cliente" full MaxVols=2
> 25-May 13:04 aosnap JobId 6804: Purging oldest volume "Backup-Cliente0242"
> 25-May 13:04 aosnap JobId 6804: 0 Files on Volume "Backup-Cliente0242" 
> purged from catalog.
> 25-May 14:04 aosnap JobId 6804: Warning: Unable add Scratch Volume, Pool 
> "Cliente" full MaxVols=2
> 25-May 14:04 aosnap JobId 6804: Purging oldest volume "Backup-Cliente0242"
> 25-May 14:04 aosnap JobId 6804: 0 Files on Volume "Backup-Cliente0242" 
> purged from catalog.
> 25-May 16:04 aosnap JobId 6804: Warning: Unable add Scratch Volume, Pool 
> "Cliente" full MaxVols=2
> 25-May 16:04 aosnap JobId 6804: Purging oldest volume "Backup-Cliente0242"
> 25-May 16:04 aosnap JobId 6804: 0 Files on Volume "Backup-Cliente0242" 
> purged from catalog.
> 25-May 18:33 aosnap JobId 6804: Fatal error: Network error with FD 
> during Backup: ERR=Connection reset by peer
> 25-May 18:33 aosnap JobId 6804: Job Backup-Cliente.2009-05-25_13.00.34 
> canceled while waiting for mount on Storage Device ""BaculaBackups" 
> (/backups)".
> 25-May 18:33 aosnap JobId 6804: Fatal error: append.c:259 Network error 
> on data channel. ERR=Connection reset by peer
> 25-May 18:33 aosnap JobId 6804: Job write elapsed time = 05:31:53, 
> Transfer rate = 35.22 K bytes/second
> 25-May 18:33 aosnap JobId 6804: Fatal error: No Job status returned from FD.
> 25-May 18:33 aosnap JobId 6804: Error: Bacula aosnap 2.4.3 (10Oct08): 
> 25-May-2009 18:33:11
> 
> 
> After it, a folder in user computer dissapeared. User told me he needed 
> to recovery the folder, so I tried to do a Bacula Restore... but volume 
> had finished with error, had been pruned and I couldn't recovery any file.

First, work only with the disk image you created if this might be a 
hardware issue.

Then, as long as no other job has used the volume in question, you can 
use Bacula to try restores from it. Either get the contents into the 
catalog using bscan, or - preferred, in this case - use bextract to 
get at the missing files.

> 2009-05-26 11:08:22aosnap JobId 6822: Start Restore Job 
> RestoreFiles.2009-05-26_11.08.15
> 2009-05-26 11:08:22aosnap JobId 6822: Using Device "BaculaBackups"
> 2009-05-26 11:08:22aosnap JobId 6822: Ready to read from volume 
> "Backup-Cliente0242" on device "BaculaBackups" (/backups).
> 2009-05-26 11:08:22aosnap JobId 6822: Forward spacing Volume 
> "Backup-Cliente0242" to file:block 3:1413080808.
> 2009-05-26 11:09:24aosnap JobId 6822: End of Volume at file 3 on device 
> "BaculaBackups" (/backups), Volume "Backup-Cliente0242"
> 2009-05-26 11:09:24aosnap JobId 6822: End of all volumes.
> 2009-05-26 11:09:24aomail JobId 6822: Error: attribs.c:421 File size of 
> restored file /bacula-restores/D:/Documents and Settings/Joan Sorribes/Mis 
> documentos/correu/jsorribes/Mail/NOVES TITULACIONS not correct. Original 
> 439051283, restored 168558508.
> 2009-05-26 11:09:24aosnap JobId 6822: Error: Bacula aosnap 2.4.3 (10Oct08): 
> 26-May-2009 11:09:24

Most Bacula programs accept the -p option top make them ignore some 
errors and continue in spite of them.

> 
> How can I solve this BIG trouble? What is the correct configuration to 
> avoid this problem?

- Keep your disk healty
- Keep your file systems healty

> Job and other parameters are configured as follow:
> 
> Client {
>   Name = client-fd
>   Address = X.Y.Z.T
>   FDPort = 9102
>   Catalog = Catalogo-USUARIOS
>   Password = "cliente"
>   File Retention = 30 days            # 30 days
>   Job Retention = 6 months            # six months
>   AutoPrune = yes                     # Prune expired Jobs/Files
> }
> 
> Pool {
>         Name = Cliente
>         Label Format = "Backup-Cliente"
>         Use Volume Once = no
>         Pool Type = Backup
>         Recycle = yes
>         AutoPrune = yes
>         Storage = BackupRAID5
>         Volume Use Duration = 1 months
>         Volume Retention = 7 days
- re-think if seven days of retention time are enough. I consider that 
very short.
>         Maximum Volume Jobs = 0
>         Maximum Volumes = 2
- Use more volumes. The more you have, the better the chance to find 
needed data on others.
>         Recycle Oldest Volume = yes
>         Purge Oldest Volume = yes
- do not purge data that may still be valid.

>         Maximum Volume Bytes = 15GB
- 2 Volumes à 15 GB amre 30 GB. Why not use 10 Volumes of 3 GB each?

> }
> 
> Job {
>   Name = "Backup-Cliente"
>   JobDefs = "Usuarios"
>   FileSet = "Usuario-Windows"
>   Client = client-fd
>   Write Bootstrap = "/var/bacula/client.bsr"
>   Pool = Cliente
>   Enabled = yes
>   Messages = Cliente
>   #Max Run Time = 2h
>   Schedule = "Usuarios 13:00"
>   Run Before Job = "/etc/bacula/scripts/check-status-client.sh '%c'"
> }
> 
> Is there any way for avoiding this big problem?

Depends on the underlying problem, about which we don't know much.

If it's only the retention policy, some hints are given above. If it's 
a hardware issue, you need to monitor your hardware. And act 
accordingly :-)

Hope this helps you a bit,

Arno

> Help!!
> 
> Thanks!!!!!!!


-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>