RE: Remote backups, reading from and writing to the same file
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hans Nieser Sent: Friday, 13 January 2006 10:25 AM To: freebsd-questions@freebsd.org Subject: Remote backups, reading from and writing to the same file Hi list, For a while I have been doing remote backups from my little server at home (which hosts some personal websites and also serves as my testing webserver) by tarring everything I wanted to be backed up and piping it to another machine on my network with nc(1), for example: On the recieving machine: nc -l 1 backup-`date +%Y-%m-%d`.tar.gz On my server: tar -c -z --exclude /mnt* -f - / | nc -w 5 -o aphax 1 (Some excludes for tar(1) are left out for simplicity's sake) Among the things being backed up are my mysql database tables. This made me wonder wether the backup could possibly get borked when mysql writes to any of the mysql tables while tar is reading from them. Do I really have to use MySQL's tools to do a proper SQL dump or stop MySQL (and any other services that may write to files included in my backup) before doing a backup? Do any of the more involved remote-backup solutions have ways of working around this? Or is it simply not possible to write to a file while it is being read? hi hans, just some points to note in a general unix / db way ( not freebsd or mysql specific ) : tar ( and unix in general ) doesn't care if you're writing while you're reading, so the tar will 'work' - though I believe tar may get confused if you create new files while tar is running. just copying a 'live' db file will generally not give you a recoverable backup. e.g. with 'oracle' you need to put files into backup mode before copying them which lets oracle maintain extra recovery information. with 'ingres' you use the ingres backup command which records before images along with the database files ( and incidentally prevents table creation ( i.e. new files ) while it backs up the db - usually with tar! ). so you really need to find out what 'hot' backup is supported by your db and run accordingly. or just shut down your db's before running your backups. a common way to manage database backups ( if you have the space ) is to use normal db backup methods to backup to local disk, then use the remote backup to backup the db backup ( and exclude the live db files since they're probably not usable anyway ). the number one rule for ALL backup regimes is - TEST YOUR RECOVERY METHOD - preferably regularly. a real recovery is not the time to find out what the shortcomings in your backup methodology are. regards, siegfried. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: How to use X without installing X?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Morse Sent: Friday, 14 January 2005 07:37 To: Daniel S. Haischt Cc: [EMAIL PROTECTED] Subject: Re: How to use X without installing X? On 13 Jan 2005, at 2:15 PM, Daniel S. Haischt wrote: simply try to export/set the DISPLAY variable before installing any additional software. setenv DISPLAY foo.bar.com:0.0 | Your actual X-Server -ยด Hi! I tried this (I had to use xhost first on my local machine), and it sort of works. I get a lot of errors about fonts, and the Oracle installer keeps throwing various java exceptions and not doing anything, but I don't know if that's because of problems with the installer or the X connection. The font errors I get are: Font specified in font.properties not found [--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific] if you have any idea what I'm missing that would solve this... Thanks muchly, Ricky hi ricky, this is the way to go - you definitely don't need anything X related on the server - I've just done this recently ( albeit with hpux and reflection X ). the install notes should tell you what version of java you need and that should help you fix up those errors. the font thing I can't help you with - perhaps you just need to install a font with those properties? or make sure all your fonts are on the right path / list / whatever ? also, you could just use another X server - do you have a different working unix workstation ( sgi, sun, hp, etc )? or even a p.c. running reflection X or exceed. but note that I can't get cygwin to work for me - I only get about a quarter of the initial installer screen to show up so I have to kill it - although it's still worth a quick try if you have a windows box. hth, siegfried. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: KVM Switches
-Original Message- Need information on how to get a KVM switch to work with the FreeBSD mouse driver. The Monitor and keyboard work fine but I have to hook a mouse directly to the box for it to work. Thanks, Ron Martin I suspect it's more a hardware issue. I have a similar problem ( i.e. monitor and keyboard fine, mouse not ) at work with a compaq and ibm desktop. at home running generic pc's everything's fine. regards, siegfried. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum - suitablity for use with removable disks
hi all, i want to use vinum with some removable ( e.g. usb2 ) hard disks. i want to use vinum because : it lets me create as many appropriately sized volumes as i need ; and, it doesn't matter whether the disk connects as da0 or da1 since vinum uses it's own label. my question is, will vinum comfortably handle more than one disk where there is an equal chance that none, one or more will be online at any one time. if i plug in a disk, will i need to restart or bring up or whatever the disk, or the plex etc every time a disk comes back online? if so, what is the smallest set of commands i can use to do this? note that i only intend to run single plexes ( no mirrors or raid 5 ) where all subdisks reside on the same physical disk. any thoughts or experiences appreciated. thanx, siegfried. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: first time with growfs
hi scott, i believe you can only use growfs with contiguous disk space. but, with unix you don't need to increase the size of the freebsd partition ( actually called slice in this context ). you do not need to use growfs to use more space. you have at least three other options that will let you use any other space on your disk that will be transparent from an application / end-user perspective : 1. just partition the new slice any way you like and mount the space wherever you need it. remember that you can mount partitions anywhere in your directory tree. e.g. if /usr/src is taking up most of the space in /usr, just copy /usr/src to a new partition that you've temporarily mounted as /mnt, then rm -rf /usr/src, umount /mnt and mount the partition it under /usr/src. 2. just create a big /usr2, move directories and then use symlinks all over the place :) 3. use vinum for the entire new slice. move stuff to vinum supported partitions. reformat your old slice to use vinum where possible. then extend vinum volumes and use growfs to your heart's content. if this sounds too much like hard work, see options 1 and 2. regards, siegfried. -Original Message- From: Scott Renna [mailto:[EMAIL PROTECTED] Sent: Sunday, 12 October 2003 1:54 To: [EMAIL PROTECTED] Subject: first time with growfs Hello all, So I've been reading the man page for growfs and I'm ready to use it, however, I'm concerned about not utilizing it properly and destroying things. Here's what I got: I have my primary drive(ad0) split up like this. The first partition is a 6GB space which holds all of the slices for my FreeBSD 5.0. The second partition following that I've reserved as 6GB for my future OpenBSD install. Now, I'd like to create a new partition right AFTER the OpenBSD reserved space and I'd like to add that additional space on for the FreeBSD portion. I'd like this to be transparent. Basically, I'm trying to increase the overall size of the FreeBSD partition. Can anyone recommend a best practice for this or point me to a good reference? Scott Renna ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 80GB IDE Drive Compatible?
-Original Message- From: Drew Tomlinson [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 17 July 2002 8:33 To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: 80GB IDE Drive Compatible? - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 16, 2002 8:41 AM Subject: 80GB IDE Drive Compatible? Setting up a new P4 1.7Ghz system, Maxtor ATA100 80GB HD. The BIOS see's the drive fine, size is correct. When I try to install 4.6Release, I am receiving the following: WARNING: A geometry of 155114/16/63 for ad0 is incorrect. Using a more likely geometry. If this geometry is incorrect or you are unsure as to whether or not it's correct, please consult the Hardware Guide in the Documentation submenu or use the (G)eometry command to change it now. etc Any suggestions? Try the G command and just specify? Any possible problems with this down the road? I am using an 80 GB IDE drive on my system and it is working fine. As someone else suggested, let FBSD pick the geometry and you should be OK. It worked for me. surely this is a bug with the installer ( or whatever front-end to fdisk the installer uses )? i can run 'fdisk -f parfile ad3' and specify a geometry of 116301/16/63 and things work fine - so apparently this geometry is not 'incorrect'. ( this is reflecting dmesg - does this come from the bios? i have my disk set to auto detect in the bios since it's in a caddy so i never actually see what the bios thinks it has ). i like to be able to script my entire disk configuration so i always have fdisk and disklabel parameter files for all my disks which makes it much easier and quicker to rebuild/reconfigure as required. but this 'feature' means whenever i use the installer it screws up my geometry ( since i can't seem to skip this step ). is there any real reason why i shouldn't use 116301/16/63 ? regards, siegfried. regards, siegfried. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
