[Bacula-users] Still present

[Crystian Dorabiatto]

Good morning. How are you?

Some of my Jobs I see this warning when I recycle volumes.

alucard1.provo1.latam-eig.com-sd JobId 5151: Recycled volume "Daily-S3-7"
on Cloud device "S3-Cloud-16" (/var/bacula/S3-Cloud), all previous data
lost.
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.218 is still present
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.217 is still present
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.216 is still present
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.215 is still present
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.214 is still present
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.213 is still present
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.212 is still present
alucard1.provo1.latam-eig.com-sd JobId 5151: Warning:
truncate_cloud_volume: Daily-S3-7/part.211 is still present

Do I need to worry about anything?

Do I need to do anything?

Thanks.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Repo Bacula

[Crystian Dorabiatto]

Awesome, thanks!

Em sex, 3 de jul de 2020 03:49, Davide Franco  escreveu:

> Hello,
>
> Centos 6 packages for Bacula 9.6.5 are now available in the repo.
>
> Best regards
>
> Davide
>
> On Thu, 2 Jul 2020 at 22:49, Crystian Dorabiatto <
> geovani.dorabia...@gmail.com> wrote:
>
>> Ok, thanks.
>>
>> On Thu, Jul 2, 2020 at 5:46 PM Davide Franco  wrote:
>>
>>> Hello Geovani,
>>>
>>> I will build Centos 6 packages when I have a bit of time.
>>>
>>> Best,
>>>
>>> Davide
>>>
>>> On Wed, 1 Jul 2020 at 19:03, Crystian Dorabiatto <
>>> geovani.dorabia...@gmail.com> wrote:
>>>
>>>> Good afternoon,
>>>>
>>>> I have a doubt.
>>>>
>>>> On repo RPM version 9.6.5. Will we have a version for CentOS 6 (EL6)?
>>>>
>>>> Thanks
>>>>
>>>> Regards.
>>>> ___
>>>> Bacula-users mailing list
>>>> Bacula-users@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>>>
>>>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Repo Bacula

[Crystian Dorabiatto]

Ok, thanks.

On Thu, Jul 2, 2020 at 5:46 PM Davide Franco  wrote:

> Hello Geovani,
>
> I will build Centos 6 packages when I have a bit of time.
>
> Best,
>
> Davide
>
> On Wed, 1 Jul 2020 at 19:03, Crystian Dorabiatto <
> geovani.dorabia...@gmail.com> wrote:
>
>> Good afternoon,
>>
>> I have a doubt.
>>
>> On repo RPM version 9.6.5. Will we have a version for CentOS 6 (EL6)?
>>
>> Thanks
>>
>> Regards.
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Repo Bacula

[Crystian Dorabiatto]

Good afternoon,

I have a doubt.

On repo RPM version 9.6.5. Will we have a version for CentOS 6 (EL6)?

Thanks

Regards.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Driver S3

[Crystian Dorabiatto]

Good morning

How are you?

After update .rpm repo to 9.6.5 I tried first job. After I tried for test
restart the bacula-sd I saw it.

A lot of line with it:

[root@alucard2 ~]# tail -n150 /var/log/messages
Jun 29 11:55:37 alucard2 bacula-sd[13177]:
alucard2.provo1.latam-eig.com-sd: smartall.c:420-0 Orphaned buffer:
alucard2.provo1.latam-eig.com-sd 24 bytes at 7fca6825b9f8 from
s3_driver.c:629
Jun 29 11:55:37 alucard2 bacula-sd[13177]:
alucard2.provo1.latam-eig.com-sd: smartall.c:420-0 Orphaned buffer:
alucard2.provo1.latam-eig.com-sd 24 bytes at 7fca6825ba48 from
s3_driver.c:629
Jun 29 11:55:37 alucard2 bacula-sd[13177]:
alucard2.provo1.latam-eig.com-sd: smartall.c:420-0 Orphaned buffer:
alucard2.provo1.latam-eig.com-sd 24 bytes at 7fca6825ba98 from
s3_driver.c:629
Jun 29 11:55:37 alucard2 bacula-sd[13177]:
alucard2.provo1.latam-eig.com-sd: smartall.c:420-0 Orphaned buffer:
alucard2.provo1.latam-eig.com-sd 24 bytes at 7fca68257328 from
s3_driver.c:629

But I'm using 9.6.5, and I saw it too on file
/opt/bacula/scripts/bacula_config :

Configuration on Sat Jun 27 19:35:37 UTC 2020:

   Host:  x86_64-redhat-linux-gnu-bacula -- redhat
(Core)
   Bacula version:Bacula 9.6.5 (11 June 2020)
   Source code location:  .
   Install binaries:  /opt/bacula/bin
   Install libraries: /opt/bacula/lib64
   Install config files:  /opt/bacula/etc
   Scripts directory: /opt/bacula/scripts
   Archive directory: /tmp
   Working directory: /opt/bacula/working
   PID directory: /opt/bacula/working
   Subsys directory:  /opt/bacula/working
   Man directory: /usr/share/man
   Data directory:/opt/bacula/share
   Plugin directory:  /opt/bacula/plugins
   C Compiler:gcc 4.8.5
   C++ Compiler:  /usr/bin/g++ 4.8.5
   Compiler flags: -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
-fexceptions -fstack-protector-strong --param=ssp-buffer-size=4
-grecord-gcc-switches   -m64 -mtune=generic -x c++ -fno-strict-aliasing
-fno-exceptions -fno-rtti
   Linker flags:-L/home/bsbuild/redhat/BUILD/depkgs/lzo/lib
   Libraries: -lpthread -ldl -ldl
   Statically Linked Tools:   no
   Statically Linked FD:  no
   Statically Linked SD:  no
   Statically Linked DIR: no
   Statically Linked CONS:no
   Database backends: PostgreSQL
   Database port:
   Database name: bacula
   Database user: bacula
   Database SSL options:

   Job Output Email:  root@localhost
   Traceback Email:   root@localhost
   SMTP Host Address: localhost

   Director Port: 9101
   File daemon Port:  9102
   Storage daemon Port:   9103

   Director User: bacula
   Director Group:bacula
   Storage Daemon User:   bacula
   Storage DaemonGroup:   disk
   File Daemon User:  root
   File Daemon Group: bacula

   Large file support:yes
   Bacula conio support:  no -lreadline -ltinfo
   readline support:  yes
   TCP Wrappers support:  yes -lwrap
   TLS support:   yes
   Encryption support:yes
   ZLIB support:  yes
   LZO support:   yes
   *S3 support:no*
   enable-smartalloc: yes
   enable-lockmgr:no
   bat support:   no
   client-only:   no
   build-dird:yes
   build-stored:  yes
   Plugin support:yes
   AFS support:   no
   ACL support:   yes
   XATTR support: yes
   systemd support:   yes /lib/systemd/system
   Batch insert enabled:  PostgreSQL

   Plugins:
   - Docker:  yes

__EOC__

apparently everything was successfully updated

[root@alucard2 bacula]# ls -lha lib64/libs3.so.4
-rwxr-xr-x 1 root root 100K Jun 27 16:38 lib64/libs3.so.4
[root@alucard2 bacula]# ls -lha plugins/bacula-sd-cloud-driver-9.6.5.so
-rwxr-xr-x 1 root root 539K Jun 27 16:39 plugins/
bacula-sd-cloud-driver-9.6.5.so
[root@alucard2 bacula]#

do i need to do anything?
do i need to worry about something?
everything is alright?

Thanks

Regards
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.6.3 - Could not open Cloud driver

[Crystian Dorabiatto]

Good night. How are you?

Can you please tell us when version 9.6.5 will be released for the rpm
repository?

Thanks

Regards

On Tue, Jun 23, 2020 at 1:27 PM Kern Sibbald  wrote:

> Oops.  It should have read:
> "Unfortunately it seems that the S3 driver NEVER worked on 9.6.3.   You
> will need 9.6.4 or 9.6.5."
>
> Sorry for the confusion.
>
> Kern
>
> On 6/23/20 5:08 PM, kern wrote:
>
> Hello,
>
> Unfortunately it seems that the S3 driver worked on 9.6.3.   You will need
> 9.6.4 or 9.6.5.
>
> Best regards,
> Kern
>
>
>
> Sent from my Samsung Galaxy smartphone.
>
>
>  Original message 
> From: Mario Pranjic  
> Date: 6/22/20 13:23 (GMT+01:00)
> To: bacula-users@lists.sourceforge.net
> Subject: [Bacula-users] Bacula 9.6.3 - Could not open Cloud driver
>
> Hi,
>
> I am trying to set-up Bacula with Cloud driver to write to S3 bucket.
>
> OS: Ubuntu 18.04 LTS (fully patched)
>
> Bacula packages (installed from Bacula repository on bacula.org):
> ii  bacula-client
> 9.6.3-1 amd64Network
> backup, recovery and verification - file daemon
> ii  bacula-cloud-storage
> 9.6.3-1 amd64Network
> backup, recovery and verification - Cloud Storage Plugin
> ii  bacula-common
> 9.6.3-1 amd64Network
> backup, recovery and verification - common support files
> ii  bacula-console
> 9.6.3-1 amd64Network
> backup, recovery and verification - text console
> ii  bacula-postgresql
> 9.6.3-1 amd64Network
> backup, recovery and verification - PostgreSQL storage for Director
>
> Default installation works like a charm (as usual), but then I tried to
> set-up cloud storage in bacula-sd (following
> https://blog.bacula.org/whitepapers/CloudBackup.pdf).
>
> I followed example on pages 8 and 9 and came up with (keys and realnames
> are stripped):
>
> Device {
>   Name = CloudStorage
>   Device Type = Cloud
>   Cloud = TEST1
>   Archive Device = /data/bacula/backup-cloud
>   Maximum Part Size = 10 MB
>   Media Type = CloudType
>   LabelMedia = yes
>   Random Access = yes
>   AutomaticMount = yes
>   RemovableMedia = no
>   AlwaysOpen = no
> }
>
> Cloud {
>  Name = TEST1
>   Driver = "S3"
>   HostName = "s3.amazonaws.com"
>   BucketName = "mybycket"
>   AccessKey = "access_key_here"
>   SecretKey = "secret_access_key_here"
>   Protocol = HTTPS
>   UriStyle = VirtualHost
>   Truncate Cache = No
>   Upload = EachPart
>   Region = "us-east-1"
>   MaximumUploadBandwidth = 5MB/s
> }
>
> When I try to reference it in bacula-dir.conf:
>
> JobDefs {
>   Name = "DefaultJob"
>   Type = Backup
>   Level = Incremental
>   Client = bacula-fd
>   FileSet = "Full Set"
>   Schedule = "WeeklyCycle"
>   Storage = CloudType#referencing cloud storage
>   Messages = Standard
>   Pool = File
>   SpoolAttributes = yes
>   Priority = 10
>   Write Bootstrap = "/opt/bacula/working/%c.bsr"
> }
>
> Bacula director fails to start with bacula-sd error:
> Jun 22 12:38:42 bacula bacula-sd: cloud_dev.c:690 Could not open Cloud
> driver type=1 for Device=CloudStorage.
>
> Am I looking at some potential bug here or I got something wrong?
>
> All bacula packages are taken from bacula repository, bacula-cloud-storage.
>
> Plugin directory in bacula-sd is defined:
>   Plugin Directory = "/opt/bacula/plugins"
>
> And it contains:
> -rw-r--r-- 1 root root 509216 Apr  7 10:01 bacula-sd-cloud-driver-9.6.3.so
>
> Any help&advice is more than welcomed!
>
> Thanks!
>
> Best regards
> --
> *Mario*
>
>
>
> ___
> Bacula-users mailing 
> listBacula-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bacula-users
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Prune and Truncate Using Driver S3

[Crystian Dorabiatto]

Good morning, how are you?

After Prune and Truncate my volumes Daily using S3, the jobs getting me it.

alucard1.provo1.latam-eig.com-dir JobId 3194: Start Backup JobId 3194,
Job=vps-dbsmall.houston1.latam-eig.com-job-s3.2020-06-19_08.00.12_41
alucard1.provo1.latam-eig.com-dir JobId 3194: Using Device
"S3-Cloud-2" to write.
vps-dbsmall.houston1.latam-eig.com-fd JobId 3194: shell command: run
ClientBeforeJob "/opt/bacula/scripts/backup_bacula"
alucard1.provo1.latam-eig.com-dir JobId 3194: Sending Accurate
information to the FD.
alucard1.provo1.latam-eig.com-sd JobId 3194: Fatal error:
cloud_dev.c:997 Unable to download Volume="Daily-S3-3" label.
vps-dbsmall.houston1.latam-eig.com-fd JobId 3194: Fatal error:
job.c:3018 Bad response from SD to Append Data command. Wanted 3000 OK
data
, got len=25 msg="3903 Error append data:  "
alucard1.provo1.latam-eig.com-sd JobId 3194: Fatal error:
cloud_dev.c:997 Unable to download Volume="Daily-S3-3" label.
alucard1.provo1.latam-eig.com-sd JobId 3194: Warning: mount.c:215 Open
of Cloud device "S3-Cloud-2" (/var/bacula/S3-Cloud) Volume
"Daily-S3-3" failed: ERR=
alucard1.provo1.latam-eig.com-dir JobId 3194: Error: Bacula
alucard1.provo1.latam-eig.com-dir 9.6.3 (09Mar20):


Has this been adjusted in version 9.6.5? I'm still using 9.6.3 (RPM)


Some volumes work, others at the time of prune / truncate was removed
the direcotry of bucket , only Bacula has access to S3


Thanks


regards
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula RPM 9.6.5

[Crystian Dorabiatto]

Good morning

How are you?

I have a doubt.

When released version 9.6.5 of repo rpm, we have uninstall plugin driver s3
for update?

Or the process remove and install the new version automatically

Thanks

Regards
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum Volume Error

[Crystian Dorabiatto]

Good morning

Check the php.ini put on It the your timezone

/etc/php.ini or other place

https://www.php.net/manual/en/timezones.php

https://stackoverflow.com/questions/32224547/setting-the-timezone-for-php-in-the-php-ini-file

Regards

Em qui, 11 de jun de 2020 11:16, Jeff Thomas  escreveu:

> Error 1000 - Internal error. [Warning] strtotime(): It is not safe to rely
> on the system's timezone settings. You are *required* to use the
> date.timezone setting or the date_default_timezone_set() function. In case
> you used any of those methods and you are still getting this warning, you
> most likely misspelled the timezone identifier. We selected the timezone
> 'UTC' for now, but please set date.timezone to select your timezone. (@line
> 135 in file
> /usr/share/baculum/htdocs/protected/API/Class/VolumeManager.php).
>
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Upload Parts in S3

[Crystian Dorabiatto]

Good morning

On here:

https://www.bacula.org/9.4.x-manuals/en/main/New_Features_in_9_4_0.html

Section:







*Upload = Upload-kwThis directive specifies when local cache parts will
be uploaded to the Cloud. The options are:No Do not upload cache
parts. With this option you must manually upload the cache parts with a
bconsole Upload command, or do so with an Admin Job that runs an Upload
command. This is the default.EachPart With this option, each part
will be uploaded when it is complete i.e. when the next part is created or
at the end of the Job.AtEndOfJob With this option all parts that
have not been previously uploaded will be uploaded at the end of the Job.
Note: Not yet implemented.*

The option No, not to do Upload, dont works too using bconsole cloud upload.

Other doubt is in AtEndOfJob What does it mean Not yet implemented? Not
tested? or not Implanted in S3 Driver?

Thanks so much

regards
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Parts S3

[Crystian Dorabiatto]

Thanks!

On Tue, Jun 2, 2020 at 10:14 AM Heitor Faria  wrote:

> Hello Crystian,
>
> Good morning
> How are you?
>
> On it https://blog.bacula.org/whitepapers/CloudBackup.pdf
>
> In the section:
>
> *MaximumPartSizeThis directive specifies the maximum size for each
> CloudVolume part. Smaller part sizes will reduce restore costs, but may
> require asmall additional overhead to handle multiple parts. The maximum
> numberof parts permitted in a Cloud Volume is 524,288. The maximum size of
> anygiven part is approximately 17.5TB*
>
> I'm using 256MB, but, my doubt are:
>
> If there is a recommended size for this?
> The smaller the better?
> Is 256 MB a good size?
>
> The parts are the chunk of data that Bacula will be uploading during
> backup and downloading during restore.
> Object storage transactions are atomic. You can only transfer the entire
> object or nothing.
> Smaller parts mean less downloaded data (e.g.) if you only need to restore
> a small file. They are also easier to transfer, since a faulty transmission
> will require retransmiting all the chunk.
> However, I personally think very small part size is hard to manage because
> it will generate thousands of them. Also, I "guess" it might generate some
> performance overhead.
> That said, there is no magic number. It depends on your Internet link,
> object storage provider cost metrics, usability etc.
>
>
> Thanks
>
> Regards,
> --
>
> MSc Heitor Faria
> CEO Bacula LATAM
> mobile1: + 1 909 655-8971
> mobile2: + 55 61 98268-4220
> [image: linkedin icon]
> 
> [image: logo] 
> América Latina
> bacula.lat | bacula.com.br 
>
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Parts S3

[Crystian Dorabiatto]

Good morning

How are you?

On it https://blog.bacula.org/whitepapers/CloudBackup.pdf

In the section:

*MaximumPartSizeThis directive specifies the maximum size for each
CloudVolume part. Smaller part sizes will reduce restore costs, but may
require asmall additional overhead to handle multiple parts. The maximum
numberof parts permitted in a Cloud Volume is 524,288. The maximum size of
anygiven part is approximately 17.5TB*

I'm using 256MB, but, my doubt are:

If there is a recommended size for this?
The smaller the better?
Is 256 MB a good size?

Thanks

Have nice a week
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Check size volume using S3 Driver

[Crystian Dorabiatto]

Good morning,

Using S3 Driver and Feature Max Volume jobs=1, we can to see:

  Scheduled time: 12-May-2020 09:00:00
  Start time: 12-May-2020 11:29:49
  End time:   12-May-2020 11:53:57
  Elapsed time:   24 mins 8 secs
  Priority:   10
  FD Files Written:   445,194
  SD Files Written:   445,194
  FD Bytes Written:   4,850,167,345 (4.850 GB)
  SD Bytes Written:   4,945,815,820 (4.945 GB)
  Rate:   3349.6 KB/s
  Software Compression:   63.3% 2.7:1
  Comm Line Compression:  3.1% 1.0:1
  Snapshot/VSS:   no
  Encryption: no
  Accurate:   yes
  Volume name(s): daily-s3-19
  Volume Session Id:  20
  Volume Session Time:1589284634
  Last Volume Bytes:  766,368,138 (766.3 MB)
  Non-fatal FD errors:0
  SD Errors:  0
  FD termination status:  OK
  SD termination status:  OK
  Termination:Backup OK

But in volume:

Writing
Vol. jobs 1
Vol. files 0
Vol. bytes 766.3MB
First written 2020-05-12 11:29:49
Last written 2020-05-12 11:52:02

I think the select of volume get the info of  Last Volume Bytes: and not
size of job. Is it right?

Regards
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users