Re: dumping file system subtree (/var)
alternatively - use tar. What I was trying to achieve, which I haven't done yet, was a smallish dump of the core system. By that I mean system + ports, without distfiles, etc. Then a separate dump of user data, which is considerably larger. At this point I am thinking I should do this: make clean distclean ports to remove temporary stuff set /usr/home NODUMP dump /, /var, and /usr unset /usr/home NODUMP dump /usr/home really - use tar. dump is not for that, but to QUICKLY dump a filesystem. on SSD - both are faster than writing to backup target disk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? i really have no idea why you just don't dump it all? restore have -i option that allow you to partially restore files from a dump. I have SSD, single partition and i use dump to backup it to external hard disk. alternatively - use tar. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
On 06/16/12 10:19, Wojciech Puchar wrote: When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? i really have no idea why you just don't dump it all? restore have -i option that allow you to partially restore files from a dump. I have SSD, single partition and i use dump to backup it to external hard disk. alternatively - use tar. What I was trying to achieve, which I haven't done yet, was a smallish dump of the core system. By that I mean system + ports, without distfiles, etc. Then a separate dump of user data, which is considerably larger. At this point I am thinking I should do this: make clean distclean ports to remove temporary stuff set /usr/home NODUMP dump /, /var, and /usr unset /usr/home NODUMP dump /usr/home ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
dumping file system subtree (/var)
When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? Gary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
Would rsync or cpdup from single user mode cover your needs? Should cover everything and then you can just reboot into your newly partitioned system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
2012-06-07 22:05, Gary Aitken skrev: When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/disks.html#NEW-HUGE-DISK ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: dumping file system subtree (/var)
On Thu, 7 Jun 2012, Gary Aitken wrote: When I originally set up my SSD, the stuff I was following indicated there was no need to put anythng on a separate filesystem. I'm now trying to build a backup system on a usb drive and I want a separate /var and /tmp. I had originally set the nodump flag on /tmp and /var, so my snapshot is empty for those. There are several things in /var that are worth keeping, and they are pretty small. I don't think there's any reason to preserve /tmp, but is there any good way to copy /var from the running system on the SSD to another filesystem (and still preserve everything, including flags)? My impression is both mksnap_ffs and dump should only be used on a complete filesystem, not a subtree. Or do I need to unset the nodump flag on /var, make a snapshot of /, take a dump :-), and then split the /var out upon restore? Snapshots don't have to be made separately, dump's -L option does that automatically: http://www.wonkity.com/~wblock/docs/html/backup.html Restoring from a dumpfile is an easy way. net/rsync has a config option to support flags, but I haven't tried it. And would it be wise to repartition the SSD to put /var and /tmp on their own partitions? When I did that recently, I put /var on a small separate partition but used tmpfs(5) for /tmp. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
