backup does not move to next storage
Erich Eckner
Hash: SHA256
Hi,
I have a file-based backup with bareos with mutliple disks to store the
files on:
- --------8<---------
Device {
Name = mnt
Media Type = File
Archive Device = /var/lib/bareos/storage/mnt
LabelMedia = yes;
Random Access = yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = yes;
Description = "File device. A connecting Director must have the same Name and MediaType."
Maximum Concurrent Jobs = 10
}
- -------->8---------
and
- --------8<---------
Device {
Name = mnt2
Media Type = File
Archive Device = /var/lib/bareos/storage/mnt2
LabelMedia = yes;
Random Access = yes;
AutomaticMount = yes;
RemovableMedia = no;
AlwaysOpen = yes;
Description = "File device. A connecting Director must have the same Name and MediaType."
Maximum Concurrent Jobs = 10
}
- -------->8--------
upto mnt5.
It has used other stores than mnt in the past:
# df -h /var/lib/bareos/storage/mnt*
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/bcrypt 1.4T 1.3T 0 100% /var/lib/bareos/storage/mnt
/dev/mapper/bcrypt2 1.4T 973G 332G 75% /var/lib/bareos/storage/mnt2
/dev/mapper/bcrypt3 1.4T 299G 1006G 23% /var/lib/bareos/storage/mnt3
/dev/mapper/bcrypt4 916G 77M 870G 1% /var/lib/bareos/storage/mnt4
/dev/mapper/bcrypt5 916G 77M 870G 1% /var/lib/bareos/storage/mnt5
However, now it is stuck, trying to put "Differential-0464" onto "mnt",
which is full (as you can see above):
20-Apr 08:02 bareos-sd JobId 869: Warning: stored/mount.cc:274 Open device "mnt" (/var/lib/bareos/storage/mnt) Volume "Differential-0464" failed: ERR=stored/dev.cc:746 Could not open: /var/lib/bareos/storage/mnt/Differential-0464, ERR=No such file or directory
Where is my error?
regards,
Erich
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl6dPeQACgkQCu7JB1Xa
e1ri3Q/8CxVbxuM4PAVgnj7LqUBvxYq1EaBUXzWW14QyY5DJl6ehuaUMH6B23HRR
AsX8Xa+bVDAbhDpGVmICHTAI/LsLEMi2Mqpal9qTRX2HlPYmJRMQ9oIXkq/87TbO
FcRLs0UivxTDq3icC3uq+JAVHRYJHfUeGwtJMfdJ7Padd6TBc9GbL4HsVK5NAKQd
FjDxyWM/T8GZo8UQV8kxvtNW+yg4Ce6mMBbNpsd2WZXq9FATDqmFlksmKNZgYeVl
igmguVOa8CQHwSOlxMVlAnOBziPWLH8+7N1xBUYmKOa39ZCtqoEqLxr6nTu6bLu8
awk58/d7jB0yKsKqeerUnCTCk6u+mD8CMQyloKdeiF4GtCw2C/iTenMT7gw6gIid
aA6slpBOE2vZqGVYK3oyj87x2eKYi81QdyyJOlqbwnlDqpmncLUWMJXGY6NQJ+TB
CWIxohjBlRGV/U+H5Dni83kfeG6CYXGLMbfeJVgCeEeDIbWvADQgW0IYAEztQBzB
Iy4p9gnWIJvmqEqBJFlm7Ws4N89QpHY5Y3PTkp+4p/GpF8C4WRifJoOnu1CN3yzk
koqHx6v1qTC5dw5YgeRVqO+GBNS5q0cw/rT1zNKLNDBROE7hqrLFM6R+H3wHMrO0
dD4hvRlfG6s7Na+nJ73Shgp8auTAjMm+/t4gBlqVXBO5LVW0awg=
=u/XI
-----END PGP SIGNATURE-----
Erich Eckner
Hash: SHA256
I restarted the machine which runs the storage daemon and the director
(which aborted all the differential backups). This evening, it scheduled
the usual incremental backups, reused some old volumes and now runs out of
incremental volume space:
20-Apr 21:50 bareos-sd JobId 896: Warning: stored/mount.cc:274 Open device "mnt" (/var/lib/bareos/storage/mnt) Volume "Incremental-0471" failed: ERR=stored/dev.cc:746 Could not open: /var/lib/bareos/storage/mnt/Incremental-0471, ERR=No such file or directory
I fear, I have done something really simple wrong, because this looks like
it should be a simple setup :-(
Just for sake of completeness, here my
/etc/bareos/bareos-dir.d/storage/File.conf:
- ----8<----
Storage {
Name = File
Address = sd.example.com
Password = "secret"
Device = mnt
Device = mnt2
Device = mnt3
Device = mnt4
Device = mnt5
Media Type = File
Maximum Concurrent Jobs = 20
}
- ---->8----
Another question as a workaround: Is it possible to move volumes from one
device to another? If so: how? Can I simply move the file and bareos will
correctly identify it again? Or is there a command in bconsole to do that
(I could not find one)?
regards,
Erich
-----BEGIN PGP SIGNATURE-----
e1oCWQ/+Poq05o9LpfP3p2dlvOMSkVqYlelEtdFfDj+dfIv6kXTsaqdiyciOWym4
D42aRaZ1v/iKas7DGgUWJMqJAsi+88nBiOFlLtXYnD8Fi2ovy2zfblJBG89n3LvT
z/B/oGUsOKyeUcEFuugeqU4/zGVWDvLMbrnXHToRfhl6YwNfcwwsVsBN2jMzuQbl
TmRJc9c1zeHhy5IV6+eHXs0BsYd4WxV++VGtDmGgciWiHsLCgiIit0v4ieIF9H3d
pObsJK0zaEnTADO6ZzW+erFv+mifeMNQUGMSC7dshAi0SwbdAZI2bRcXuHRWrPmD
AQ/ZKJwWTkilKqjRfTE8Cbtz3PvtaelA5GZJWsB/8ybM0a9JDVzXYqS1Qwh83yQD
iNsfIv5ZmEjFJlJCgfzhHy30xC4QgxpP7/pBEXbRfxisuA53+qjf3AuThl3AeIRr
DMqIX6Zmqp88mUWIFq9KAxT45TL5hFkyw8XkmxN4lm/tb0B/Jba9oXAsCWV90GdH
iDx28EKfEedTLgbrcTb79kFKn1LZVn4+0gHyA0xB6KcCqKFEp3//Zx9rV+322tt9
d0vaHBKppkKsCAISxvmW7a8hhMXpv4niR7M8/80ww1r3mbqojKoDoyexXTReveoG
Fn/wP2OrHRRTYNy/MgnrBJeoZc0eLIivm18iCVZCwn76UJ8+NPY=
=UXIc
-----END PGP SIGNATURE-----
Spadajspadaj
for present volumes but I'm not sure if it works with normal directory
storage.
Brock Palen
https://docs.bareos.org/TasksAndConcepts/HowToManuallyTransferDataVolumes.html
That said if your volumes and devices are all interchangeable I would configure the system to all work with them as a single entry.
Generally this means all your disk based volumes are in a single folder (really not an issue) so the device path all point to the same location.
For disk volumes devices are ‘virtual’ and almost not real but a hold over from scheduling tape drives and other external media.
Brock Palen
1 (989) 277-6075
bro...@mlds-networks.com
www.mlds-networks.com
Websites, Linux, Hosting, Joomla, Consulting
> You received this message because you are subscribed to the Google Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/alpine.LNX.2.22.419.2004202153540.18605%40desk.ddns.eckner.net.
Spadajspadaj
can also set up a vchanger. That way you can also control fixed number
of fixed-size volumes. I prefer this approach to dynamicaly created
media files but YMMV.
Erich Eckner
Hash: SHA256
thanks for all the feedback.
On Tue, 21 Apr 2020, Spadajspadaj wrote:
> Unless you really need the automatic fall-over to the next storage, you can
> also set up a vchanger. That way you can also control fixed number of
> fixed-size volumes. I prefer this approach to dynamicaly created media files
> but YMMV.
thought, it would be more complex, thus decided for the current variant.
Can you share the relevant vchanger config with me, please?
>
>
> On 21.04.2020 16:34, Brock Palen wrote:
>> It is possible to move volumes between devices see:
>> https://docs.bareos.org/TasksAndConcepts/HowToManuallyTransferDataVolumes.html
>>
>> That said if your volumes and devices are all interchangeable I would
>> configure the system to all work with them as a single entry.
simultanously, so how do I choose the correct block device, that bareos
currently "wants"?
>>
>> Generally this means all your disk based volumes are in a single folder
>> (really not an issue) so the device path all point to the same location.
>>
>> For disk volumes devices are ‘virtual’ and almost not real but a hold over
>> from scheduling tape drives and other external media.
use tapes. Has anyone done that before and could send me a guide? Or is
this identical to the approach with the autochanger above?
>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl6fFNMACgkQCu7JB1Xa
e1oAZg//brEosQwkweV2Edu3wJffS8U2An/w+B3TGglgNpxPhlPP/4adWoMF5Bqo
5eQFiZ7FaWTlx5Rque8Q/hviagcMfDBcxpj9iPav6rNRFGvv+s/6/mUJ2KnJizhQ
FeeG/S235pSWJzn3KwO7eQO7Wgj3+WGkS6DQrR0TxixSntnpVsToZkHJnbsMWunp
V4266FCzz1VIMQGzYexyCdTcZwfREzdWvVKZBXAWT2RJOgiUb9oU+eJ8jiAajpW5
2jJbvOSzMfTh98si6ByPnBHYVEYFivYa0XlYLORhX89Wv8IExhDPvmllnqaZzakr
/6HaW0/k/iuPWFkXkgKvnGsQGg1vu5vKtAJQLbe2NRRQCNPnzdEA6TqeDtJebDXH
z2O/k+Yatj4wvVrcxZz+zc2Y3mJrym9gJiAw/ziTXxb8lO34JIGhzVEIqoCyNwr8
Tkaq6jnqDWFCYOAzi1x3untOWA5O6muFciuDQ47P/htBPiSNntEr1YwaO9O8tcU+
6a2StLLtbPPkHOqin6YJzK4AIK7gbYYJ2ELvFjKLU0GdWCWf3ruv+Wk7yxhDixTq
YTzBRiW8DezfmqzMSRnUbUj3ah64dQdKSxkxVHem/sh1bdc82jh7EqZJ+BFWiSdV
aklv67P7tvHwSlCAgHzKMGb3DKzgHJope4IcDZZwffZiejzc0dA=
=YL6c
-----END PGP SIGNATURE-----
Spadajspadaj
On Tue, 21 Apr 2020, Spadajspadaj wrote:
Unless you really need the automatic fall-over to the next storage, you can also set up a vchanger. That way you can also control fixed number of fixed-size volumes. I prefer this approach to dynamicaly created media files but YMMV.
Yes, I thought to use something like this, in the beginning, too - but I thought, it would be more complex, thus decided for the current variant. Can you share the relevant vchanger config with me, please?
Firstly I must say that for me it was essential to have a removable storage. This is my home backup setup so I'm backing up to a usb-attached disks. I have a single USB-SATA cradle in which I'm simply changing disks so I needed a low-effort solution that I could easily keep some backups offline. I'm not sure how it would work with a permanently attached storage.
I used a howto as reference but I see that it's no longer
available. Maybe it's permanent, maybe not. Anyway, for reference,
the howto used to be here http://www.revpol.com/offsitebackups
Having said that, here goes my setup (on CentOS if it has any
significance).
First element of the config is the automount setup.
/etc/auto.master:
+dir:/etc/auto.master.d
+auto.master
/srv/backupstor /etc/auto.master.d/auto.vchanger --timeout=30
/etc/auto.master.d/auto.vchanger:
* -fstype=auto,rw :/dev/disk/by-uuid/&
With this setup I can just do a cd /srv/backupstor/UUID and the automounter should mount the drive if I know the UUID (easily obtainable by blkid).
So in case of:
blkid /dev/sda1
/dev/sda1: UUID="7B06F568090A6704" TYPE="ntfs" PTTYPE="dos"
PARTUUID="aae626c7-da6c-4707-8c91-0cb52703893c"
I just do cd /srv/backupstor/7B06F568090A6704 and am in the partition's root directory (regardless of the filesystem type - in this case it's NTFS).
Second part is the vchanger setup
/etc/vchanger/vchanger.conf:
Storage Resource = vchanger-1
User = bareos
Group = bareos
Logfile = /var/log/vchanger/vchanger-1.log
Work Dir = /var/spool/vchanger/vchanger-1
Log Level = 7
Magazine = /srv/backupstor/bde48cec-03db-4f36-bb68-dbd14455b700
Magazine = /srv/backupstor/7B06F568090A6704
Magazine = /srv/backupstor/46786fd5-4bc4-4799-aaa4-a7459bc5b603
Magazine = /srv/backupstor/881564a0-63db-4e49-8f31-9a4ccd7d5d22
bconsole config = /etc/bareos/bconsole.conf
Here you can see that I'm using four different disks in rotation.
If I remember correctly, I had to do some file rights sanitization on logfile and work dir.
And the bareos bart looks like this:
Storage daemon:
/etc/bareos/bareos-sd.d/autochanger/vchanger1.conf
Autochanger {
Name = vchanger1
Device = vchanger-1-0
Changer Command = "/usr/local/bin/vchanger %c %o %S %a %d"
Changer Device = /etc/vchanger/vchanger.conf
}
/etc/bareos/bareos-sd.d/device/vchanger1.conf
Device {
Name = vchanger-1-0
DriveIndex = 0
Autochanger = yes
Device Type = File
Media Type = Offsite-File
Label Media = no
Random Access = yes
Removable Media = yes
Automatic Mount = yes
Archive Device = /var/spool/vchanger/vchanger-1/0
}
Director:
/etc/bareos/bareos-dir.d/storage/vchanger-1.conf:
Storage {
Name = vchanger-1-changer
Address = backup1 # N.B. Use a fully qualified
name here (do not use "localhost" here).
Password = "password"
Device = vchanger1
Media Type = Offsite-File
Autochanger = yes
}
/etc/bareos/bareos-dir.d/pool/Offsite-eSATA.conf:
Pool {
Name = Offsite-eSATA
Storage = vchanger-1-changer
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 3 weeks
Recycle Oldest Volume = yes
Maximum Volume Bytes = 42949672960 # Small (40GB) easy to
move/transfer volume sizes
}
In this setup after initial disk plugin I create volumes like this:
/usr/local/bin/vchanger -u bareos -g bareos
/etc/vchanger/vchanger.conf createvols 3 104
Where 3 is a disk number (in this case if we look it up in vchanger.conf we'll see that it corresponds to /srv/backupstor/881564a0-63db-4e49-8f31-9a4ccd7d5d22 (units are numbered from 0)) and 104 is number of volumes to create.
Initially the volumes are created empty and can grow to Maximum Volume Bytes so in this case it's a 4TB drive.
It's supposed to perform a label command automaticaly but for some reason it wasn't working too god for me and I dind't have much time to debug it so after creating volumes I run bconsole and do "label barcodes".
After that the only commands I use after the initial creation of volumes are mount and update slots. Just keep in mind that the volume name is one off vs. slot number in vchanger. So if the console message wants you to, for example, mount volume vchanger-1_1_0030 you have to mount slot 29.
Hope this makes some sense :-)
If you have any more questions don't hesitate to ask. I might be
able to recall something back from when I deployed this.
Erich Eckner
Hash: SHA256
I never came back to say "thanks", so here you go:
Thank you!
the vchanger config really got me started - so far, it looks, like it's
all perfect. Now, I only need to fully understand, what I configured there
;-) (and especially, what I was doing wrong before).
>
> Second part is the vchanger setup
>
> /etc/vchanger/vchanger.conf:
>
> Storage Resource = vchanger-1
> User = bareos
> Group = bareos
> Logfile = /var/log/vchanger/vchanger-1.log
> Work Dir = /var/spool/vchanger/vchanger-1
> Log Level = 7
> Magazine = /srv/backupstor/bde48cec-03db-4f36-bb68-dbd14455b700
> Magazine = /srv/backupstor/7B06F568090A6704
> Magazine = /srv/backupstor/46786fd5-4bc4-4799-aaa4-a7459bc5b603
> Magazine = /srv/backupstor/881564a0-63db-4e49-8f31-9a4ccd7d5d22
> bconsole config = /etc/bareos/bconsole.conf
>
> Here you can see that I'm using four different disks in rotation.
>
> If I remember correctly, I had to do some file rights sanitization on
> logfile and work dir.
>
>
> And the bareos bart looks like this:
>
> Storage daemon:
>
> /etc/bareos/bareos-sd.d/autochanger/vchanger1.conf
> Autochanger {
> Name = vchanger1
> Device = vchanger-1-0
> Changer Command = "/usr/local/bin/vchanger %c %o %S %a %d"
> Changer Device = /etc/vchanger/vchanger.conf
> }
>
> /etc/bareos/bareos-sd.d/device/vchanger1.conf
>
> Device {
> Name = vchanger-1-0
> DriveIndex = 0
> Autochanger = yes
> Device Type = File
> Media Type = Offsite-File
> Label Media = no
that and it did not work?)
first volume, but all others were mounted automatically (thank god, this
works - an evening worth of backup spans multiple volumes here)
>
> Hope this makes some sense :-)
>
> If you have any more questions don't hesitate to ask. I might be able to
> recall something back from when I deployed this.
>
>
>
provide a (quite trivial) PKGBUILD for that, if that's desired.
Cheers,
Erich
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl6klT8ACgkQCu7JB1Xa
e1p0bRAAgYcFtSVF8Fh71hJy6YmlXHoBtEQQabKsMblFyf4CLKtMXH5DOksdCJmq
bStcGf710nquOzSVNNpSy9HgkTdfdqMIn4j9vre+XoPw+MC9PLp5+muiR6LUo26P
1eX6aV3PI8OzERMpo1DsZyQ+SwvzIFmF8/W4T/E6vuBN/qrHqlMgU4bigaxOcVLR
MbUAQqbZXrbQoMMjK92uhfJXODRKRhXow6fMsNl8j96oafppz1ZPQv5wExEQqUfR
0xIzKuxd6jyxDjs1zzG1B+zHdpuWSTcSZsCHb3jDKEzGgDXQzbL22NQMgZoq0+t3
7u0j8zJqOSX4mFD8ZYbvyuYZyjazP1dJFfGbsE/ABxnlrXogv5kpve/7UZ8+72Px
oYMGoXeXQnixjwCexL4yMUsP+5f1tlDhtdIrE9HZQq4MZRqUnzuInozcbsMZoVcf
GiRLAD+Qnu1UtIw5dmIh9BF5ROZqUnLpgvOkPlBxO1bcO/sEELtxnHumlEPpfEZq
9iFk/VWkQGLrlcZOTQnfnZ35gDfcFUeSorohEOWnuretx6KRb2utslBhc4psOjvB
ncaas37ZAq12EQkFIdC2he4OQkdpw0q/Mn41EGml2DcM5sJ8YQH5wiO3wCeU23Sv
tqGsLKA/GHTEfpCByMRUiqYqi+daO+owc6c44fUc2+9IiqT9AYw=
=u+11
-----END PGP SIGNATURE-----
Erich Eckner
Hash: SHA256
I have a follow-up to my original problem: Is it possible to make vchanger
load more than one virtual tape simultanously - preferably one for each
pool? Because I now have a bunch of incremental backups waiting for a
drive, because there are some long-running full backups still in progress.
Currently, I can only think of the possibility to run multiple vchangers,
but then I would need to divide my volumes into "Full", "Differential" and
"Incremental" manually - and I'd like to avoid this.
Cheers,
Erich
On Sun, 26 Apr 2020, spadaj wrote:
> No problem, mate.
> Hope this is of some help. If you have any questions, don't hesitate to ask.
> I can't guarantee I'll be able to give reasonable advice but I'll try :-)
>
> Cheers.
>
> W dniu 25.04.2020 o 21:53, Erich Eckner pisze:
>> Hi spadajspadaj,
>>
>> I never came back to say "thanks", so here you go:
>> Thank you!
>>
>
iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl61Y+AACgkQCu7JB1Xa
e1o7Dw/9GB74tmUypbwRU121tVYtFIq3UK2R8rHOaQ3+Hi94TWEZ6mIolErBGO5w
plE3Y2g/lL8fJA5f0a438MegPcKFnJKpk3dNUS2XKXiWDdQZVFEIO8LQ7M9nzfde
AELIsjr9FyppgY/9xZOX0neEeifF7iA2J+0tVhtqfYscV2F3gRIaZYJ62OKsyYlI
3IwGaDxMEWvR9QKF70hpg6agk5ueSsarPtxLRFltkxhHKeavRZFU6QhLA/yJPg+m
hFC2NclZhPS2KCqVcGMPJKYPbsCu5eG2EyKgzoNtROUSQJbWKdFsu/XyLK00aYjZ
1pb9MLyDkiLOIYuHv0ul3QVK0fgTzznWZV/ZW5JerlGrYxQ0giUcPxmjRU4YtL0Z
LawY73LF1bQ5BNG3EQY2PvHpWySnmtDzY/lVz8w1u4HGvyKr10E58NBreJuywYk2
ff5IK8KK1jz5t03Z2cJ7iK1JJC6x/9Cgw1Qv/32ojd+tvNUv97S7yff7lLx1j+c5
qKaPPpIkqkBMYR8C79XajXalahhX/kXd3KDqNTKFDnOwenIdKMkNB059Ay27EAAh
UNHCIpxH7bCNEFmjgyHehoohmVCNITbokzEDoPO14554YUOBbYggi4yZg1aaJ3/c
DKe5bx/mQlAjDzRicb1mTRRmWJbXqfWdmwXhBwDuzqH9ECKq/eA=
=FDqs
-----END PGP SIGNATURE-----
Spadajspadaj
should be possible to have more than one "device".
I've never tried that myself but you could try defining another device
as per
https://docs.bareos.org/TasksAndConcepts/AutochangerSupport.html#multiple-devices
And you can of course allow interlacing multiple jobs on a single tape
by allowing multiple concurrent jobs (I don't do it myself but I read
that it can cause some problems if you lose the directory and try to
restore from media only).
Best regards,
MK
Erich Eckner
Hash: SHA256
thanks, this seems to work (somewhat). I needed to give it a kick by
manually mounting the second device via bconsole (vchanger reported it
mounted, but the director reported it as unmounted). I'll keep an eye
open, whether this is necessary each time, or if it was only a single
issue.
btw: I run backups in parallel anyways (same pool, only - because of
different retention times, I guess) to speed it up. My assumption is, that
loosing the catalog is just as probable as loosing the actual backups
(they're stored on similar disks, really), so it's nothing I need to
specifically prepare for.
regards,
Erich
e1oEWw/+MpzR919UqIJcWnRx1mtx5SXu6Q85vPfP85gQNDsndWXopoTrrZKxvaG6
qGXvnsy5KuJn9/FMm1G+11Fb5QhBatZKN8ggqrGVx5rdW+4Ufcattx0iCmIrI334
mWEMpxW0lgKW0nutw3GlebnJIKr3ZdkDnAvjGP9ac/eABzIoW1TMsBM5uKsGHGTI
3+nQa9uDJuEZDJqgIHeZxNhIdXaaBvDLWTSXJ4wDa8V/uCI5ftS+YQO+c/gBI2Il
q4hOFLynF/kTgX1X31o5D7Wt4xM6Ej7GWXmTX15BWZZtN311VjOep9CuXSFY07It
8JP9uFVlvaZQB8Zckip5EbRcF850wNcyzoEM1EDSE/eOydVnMfkyAdLMBotLk9c6
lSpVDM3TGvLfuz1uP+GZU0WFqJ84UyMUC3cDxmlNaBWr7doHwaCyk88ZpLnHGcTw
0bSo7jIIxwHwD9o5radsEsy1AjnMR1aB3kSOIRErLtf4VpZcUjp9X1w2tADzsOpA
YfkNU7uhXqs3de3Q33YFbq2CBUBRuFunahbqeXxT3gcV7dmxMTXpK2WlaNh4dLBW
Xd8iWwfkFrpJ1wPkOB4TqDmuunM8866BVl+m3hG7MO/9U1j1IMv+xYfmWw2tMy/f
qqSTKjiNYvmy5Ev9hyWCHrbg/wMId2/Gsw1uP+kE6heWPNw6FtA=
=xOme
-----END PGP SIGNATURE-----