[bareos-users] bareos and snapshots on linux

2017-08-07 Thread Stefan Klatt
Hello,

I have a xfs volume on lvm.

Is it better to use xfs or lvm snapshots?
On Centos/REL 7 there is the tool ssm, can it be used for this (I didn't
found information wich kind of snapshots - xfs or lvm - it generates)?
Or is it better to use xfsdump?
Which options I need to configure at bareos?
Has anybody scripts for this kind of backup?
Are there special tips for this?

A lot of questions, I know. Probably there are more, but I have no
experience with bareos and snapshots on Linux.

Regards

Stefan


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature


Re: [bareos-users] Re: Error: Fatal error: Network error with FD during Backup: ERR=Connection timed out

2017-08-07 Thread Bareos Flaregames
I got the answer, enabling "heartbeat interval" in bareos-dir.conf solved
the issue

On Sun, Aug 6, 2017 at 12:03 PM, fgbaros  wrote:

> On Tuesday, October 4, 2016 at 9:35:09 PM UTC+2, Jim Yeager wrote:
> > Anyone have experience with this error or able to tell me why this may
> be failing?
> >
> >
> >
> > 2016-10-04 02:05:00
> > BareOS_Server-dir JobId 5709: No prior Full backup Job record found.
> > 2016-10-04 02:05:00
> > BareOS_Server-dir JobId 5709: No prior or suitable Full backup found in
> catalog. Doing FULL backup.
> > 2016-10-04 02:50:51
> > BareOS_Server-dir JobId 5709: Start Backup JobId 5709,
> Job=Server_WS_all_job.2016-10-04_02.05.00_30
> > 2016-10-04 02:50:52
> > BareOS_Server-dir JobId 5709: Using Device "NFS_windows" to write.
> > 2016-10-04 02:50:52
> > BareOS_Server-sd JobId 5709: Volume "Full_Window-0188" previously
> written, moving to end of data.
> > 2016-10-04 02:50:52
> > BareOS_Server-sd JobId 5709: Warning: For Volume "Full_Window-0188":
> > The sizes do not match! Volume=39284065725 Catalog=38510953939
> > Correcting Catalog
> > 2016-10-04 02:50:54
> > Server_WS-fd JobId 5709: Generate VSS snapshots. Driver="Win64 VSS",
> Drive(s)="C"
> > 2016-10-04 05:02:12
> > BareOS_Server-dir JobId 5709: Fatal error: Network error with FD during
> Backup: ERR=Connection timed out
> > 2016-10-04 05:02:12
> > BareOS_Server-dir JobId 5709: Fatal error: No Job status returned from
> FD.
> > 2016-10-04 05:02:12
> > BareOS_Server-dir JobId 5709: Error: Bareos BareOS_Server-dir 15.2.2
> (16Nov15):
> > Build OS: x86_64-redhat-linux-gnu redhat Red Hat Enterprise Linux Server
> release 7.0 (Maipo)
> > JobId: 5709
> > Job: Server_WS_all_job.2016-10-04_02.05.00_30
> > Backup Level: Full (upgraded from Incremental)
> > Client: "Server_WS-fd" 12.4.4 (12Jun13) Microsoft Standard Edition
> (build 9200), 64-bit,Cross-compile,Win64
> > FileSet: "Windows All Drives" 2015-10-12 17:14:10
> > Pool: "Full-Window" (From Job FullPool override)
> > Catalog: "MyCatalog" (From Client resource)
> > Storage: "NFS_windows" (From Job resource)
> > Scheduled time: 04-Oct-2016 02:05:00
> > Start time: 04-Oct-2016 02:50:52
> > End time: 04-Oct-2016 05:02:12
> > Elapsed time: 2 hours 11 mins 20 secs
> > Priority: 10
> > FD Files Written: 0
> > SD Files Written: 0
> > FD Bytes Written: 0 (0 B)
> > SD Bytes Written: 17,668,399 (17.66 MB)
> > Rate: 0.0 KB/s
> > Software Compression: None
> > VSS: no
> > Encryption: no
> > Accurate: no
> > Volume name(s): Full_Window-0188
> > Volume Session Id: 19
> > Volume Session Time: 1475494872
> > Last Volume Bytes: 71,282,017,120 (71.28 GB)
> > Non-fatal FD errors: 1
> > SD Errors: 0
> > FD termination status: Error
> > SD termination status: Running
> > Termination: *** Backup Error ***
>
> Hello Jim,
>
> Did you find a solution for your problem. I am experiencing the exact same
> issue after the same amount of time spend (~2h10mn)
>
> I am not using a VPN and the connexion is solid, however it seems to have
> a timeout or something else who cause this issue. when the full back take
> less than 2h, it's fine.
>
>
> 06-Aug 01:27 bareos-dir JobId 298: Fatal error: Network error with FD
> during Backup: ERR=Connection timed out
> 06-Aug 01:27 bareos-dir JobId 298: Fatal error: No Job status returned
> from FD.
> 06-Aug 01:27 bareos-dir JobId 298: Error: Bareos bareos-dir 16.2.4
> (01Jul16):
>   Build OS:   x86_64-redhat-linux-gnu redhat CentOS Linux
> release 7.0.1406 (Core)
>   JobId:  298
>   Job:scm2-job.2017-08-05_23.15.00_55
>   Backup Level:   Full (upgraded from Incremental)
>   Client: "scm2.dmz" 16.2.4 (01Jul16)
> x86_64-pc-linux-gnu,ubuntu,Ubuntu 14.04 LTS,xUbuntu_14.04,x86_64
>   FileSet:"scm2-fileset" 2017-08-05 19:30:58
>   Pool:   "scm2-Full" (From Job FullPool override)
>   Catalog:"MyCatalog" (From Client resource)
>   Storage:"Storage01-scm2" (From Job resource)
>   Scheduled time: 05-Aug-2017 23:15:00
>   Start time: 05-Aug-2017 23:15:37
>   End time:   06-Aug-2017 01:27:38
>   Elapsed time:   2 hours 12 mins 1 sec
>   Priority:   10
>   FD Files Written:   0
>   SD Files Written:   0
>   FD Bytes Written:   0 (0 B)
>   SD Bytes Written:   1,347,931 (1.347 MB)
>   Rate:   0.0 KB/s
>   Software Compression:   None
>   VSS:no
>   Encryption: no
>   Accurate:   no
>   Volume name(s): scm2-Full-0053|scm2-Full-0054|
> scm2-Full-0055|scm2-Full-0056|scm2-Full-0057|scm2-Full-0058
>   Volume Session Id:  8
>   Volume Session Time:1501921897
>   Last Volume Bytes:  78,994,943,136 (78.99 GB)
>   Non-fatal FD errors:1
>   SD Errors:  0
>   FD termination status:  Error
>   SD termination status:  Running
>   Termination:*** Backup Error ***
>
> --
> You received this message be