1359772567 Q * clopez Ping timeout: 480 seconds
1359793417 J * Ghislain ~aqueos@adsl2.aqueos.com
1359796130 Q * BlackPanx Remote host closed the connection
1359796504 J * BlackPanx ~alen@77.111.2.36
1359798479 Q * Ghislain Read error: Connection reset by peer
1359800544 J * Ghislain ~aqueos@adsl2.aqueos.com
1359801657 M * Bertl off to bed now ... have a good one everyone!
1359801665 N * Bertl Bertl_zZ
1359801990 J * Ghislain1 ~aqueos@adsl1.aqueos.com
1359802317 Q * Ghislain Ping timeout: 480 seconds
1359802810 Q * fisted Remote host closed the connection
1359802870 J * fisted ~fisted@xdsl-78-35-94-210.netcologne.de
1359808211 Q * ircuser-1 Ping timeout: 480 seconds
1359809951 Q * Aiken Remote host closed the connection
1359810839 N * ensc Guest451
1359810848 J * ensc ~irc-ensc@p54ADF61B.dip.t-dialin.net
1359811257 Q * Guest451 Ping timeout: 480 seconds
1359813231 Q * Ghislain1 Quit: Leaving.
1359816995 Q * hparker Ping timeout: 480 seconds
1359817933 J * hparker ~hparker@linux.homershut.net
1359818842 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net
1359822542 N * click_ click
1359823066 N * Bertl_zZ Bertl
1359823070 M * Bertl morning folks!
1359825807 Q * BlackPanx Ping timeout: 480 seconds
1359826159 J * BlackPanx ~alen@77-111-2-36.ipv4.tusmobil.si
1359828722 J * clopez ~clopez@9.12.117.91.dynamic.mundo-r.com
1359835042 Q * fisted Remote host closed the connection
1359835042 J * fisted ~fisted@xdsl-78-35-94-210.netcologne.de
1359835347 Q * fisted Quit: bbl
1359835359 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1359835360 J * cuba33ci_ ~cuba33ci@114-36-236-60.dynamic.hinet.net
1359835704 J * Walex ~Walex@78-86-80-54.zone2.bethere.co.uk
1359835712 Q * cuba33ci Ping timeout: 480 seconds
1359835720 N * cuba33ci_ cuba33ci
1359837827 J * fisted ~fisted@xdsl-78-35-94-210.netcologne.de
1359838483 J * nkukard_ ~nkukard@196-215-197-16.dynamic.isadsl.co.za
1359838632 Q * nkukard Ping timeout: 480 seconds
1359839616 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net
1359839673 M * Seattle Hi all - we've been working at learning vserver, and are to the point of thinking about backups and failover.  Q:  from what we've read, is rsync the wrong solution for backups?
1359839687 M * Seattle I.e., backing up guests
1359839692 M * Bertl nope, just get the options right
1359839709 M * Bertl e.g. something like rsync -axHPSD --numeric-ids
1359839741 M * Seattle OH!  Cool!  Will try some changes in options and get back....
1359840076 M * Seattle Is it possible then to 1) have a backup host 2) rsync the guest as well as other vserver config areas and have a "clone" that we could cut over too if the primary host failed?
1359840102 M * Bertl yep, that's one way to do HA/Failover
1359840166 M * Bertl i.e. group two (or more) hosts into a redundant (rsync or drbd) system ... if one host fails, the other(s) take over
1359840264 M * Seattle OK, thanks - are starting to look for links (e.g., http://linux-vserver.org/Fail-over)....probably too ill defined a question, but is there a "best practice" for doing HA/Failover for vservers?
1359840295 M * Bertl back in the beginning, heartbeat was quite popular
1359840339 M * Bertl nowadays there are several options, starting from simple cron jobs to highly sophisticated HA systems
1359840383 M * Seattle So if we're "getting our feet wet in this", would rsync cron jobs be a comparatively easy way to get started?
1359840390 M * Bertl the basic principle is simple, keep an up to date version somewhere, and when the host goes down, simply start all the guests on the backup
1359840412 M * Bertl on each host, ensure that the guest is not already running on another host when it boots up
1359840439 M * Seattle OK...thanks Bertl (as always)
1359840443 M * Bertl you're welcome!
1359840447 M * daniel_hozac and it always depends  on how much your data changes
1359840457 M * daniel_hozac if you have updates every few months, rsync is great.
1359840478 M * daniel_hozac if you have them every few minutes, you will want something more advanced.
1359840507 M * Seattle Hi Daniel - what would you suggest (i.e., data on the guests will be changing continuously)?
1359840549 M * Bertl SAN/NAS, NFS, drbd
1359840577 M * Seattle OK, thanks....sounds like we have some reading to do....(!)
1359840700 M * Bertl for example, multipath on SAS
1359840860 M * Seattle OK...thanks - these chats are great...always get pointed in good directions
1359840920 M * Bertl np, that's what the channel is for after all
1359841164 M * Seattle Will do some research.....get back as to what we end up doing...possibly post if it looks like it would help others..
1359841182 M * Seattle Bye for now
1359841189 M * Bertl cya
1359841190 Q * Seattle Quit: ChatZilla 0.9.89 [Firefox 17.0/20121119183901]
1359842484 Q * Walex 
1359846012 Q * fisted Remote host closed the connection
1359846161 J * fisted ~fisted@xdsl-81-173-189-118.netcologne.de