Date: Tue, 30 May 2000 09:41:36 +0800 (TSD) From: Victor Sudakov <sudakov@sibptus.tomsk.ru> To: questions@FreeBSD.ORG Subject: Anyone using dump(8) Message-ID: <200005300141.e4U1faK17051@sibptus.tomsk.ru> In-Reply-To: <bulk.84899.20000529133509@hub.freebsd.org> from "questions-digest" at "May 29, 2000 1:35: 9 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. I wonder if anyone uses dump(8) nowadays in a production environment. It seems the best backup tool as it preserves hard links, sparce files etc. However, there are some practical questions I need enlightment on. 1. You are supposed to mount a filesystem readonly before you dump it, right? Then dump cannot write /etc/dumpdates and aborts. Moreover, I cannot stop the services every time I need to dump a filesystem. How do you deal with that? 2. The tape drive is only on one host, so I need to dump filesystems over the network. I can boot in single user mode, mount the filesystems readonly, but then I have to do all the ifconfig, route etc. stuff (to see the tape server) by hand which is annoying. 3. Is dump really so vulnerable to modifications of filesystems during dump? Then how is it supposed to work on non-stop systems? Surely there must be some know-how. People seem to have been using dump(8) for years, and in huge companies too. I only have to dump 11 boxes, some with very important data updated every 20 minutes or so, to a tape drive on one of the boxes. Dump users, please reply. Any input is greatly appreciated. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/149@fidonet http://vas.tomsk.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200005300141.e4U1faK17051>