Date: Mon, 19 Jan 2015 11:08:51 -0800 From: Michael Sierchio <kudzu@tenebras.com> To: Chris Maness <chris@chrismaness.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Dump/Restore for system migration Message-ID: <CAHu1Y71VxMtj8TKrnmZYOay0KKvEtAum5mwi%2BeSDad4vUMZLrw@mail.gmail.com> In-Reply-To: <CANnsUMESEWsEXyyKwqyrnTMiEEYuExTgD0Z4NBuJF0cYSWDChQ@mail.gmail.com> References: <CANnsUMESEWsEXyyKwqyrnTMiEEYuExTgD0Z4NBuJF0cYSWDChQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
If you're using a filesystem that supports snapshots, do the dump against the snapshot, or use dump with the -L option, to indicate that you're taking a dump of a live filesystem. - M On Mon, Jan 19, 2015 at 10:50 AM, Chris Maness <chris@chrismaness.com> wrote: > I have used dump/restore for system migration a couple of time and noticed > it is pretty good, but every once in a while it will miss or corrupt a > file. Is there a better way to do this? I would imagine having a system > mounted r/o would help, but this is not always possible. Is there a way to > check the deltas between systems manually after migration to see if any > files need to be merged or copied. I would imagine the files that are in > jeopardy are ones that are being written to while the dump is taking > place. I had a file the keeps track of rss feeds end up missing on the > target system. > > Any advice here? > > Thanks, > Chris > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y71VxMtj8TKrnmZYOay0KKvEtAum5mwi%2BeSDad4vUMZLrw>