Date: Sun, 12 Apr 2020 07:19:00 +0200 From: Andrea Venturoli <ml@netfence.it> To: freebsd-questions@freebsd.org Subject: Re: Restoring and snapshots Message-ID: <2a0ee11a-eb32-7ae2-256f-ad1b00d1e49d@netfence.it> In-Reply-To: <b80878d8-4a37-7f79-e94f-d3c44cb036bc@holgerdanske.com> References: <56b4e678-0e66-e65b-b9d2-a2e79a5b7b6f@netfence.it> <e8fb0530-917a-f259-9238-5306e63b89df@holgerdanske.com> <dbe79517-3d72-3af9-48df-129c7ec89bf7@netfence.it> <b80878d8-4a37-7f79-e94f-d3c44cb036bc@holgerdanske.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-04-12 00:18, David Christensen wrote: > I am confused: > > * What is the type of the filesystem that was the source of the backup? ZFS in the example above, but I've got the same problem with UFS, as I also use snapshot there. > * What tool(s) did you use to backup? Sometimes Bacula, sometimes some custom scripts. > * What is the type of the filesystem that was the destination of the > backup? Could be UFS, bacula volumes, tapes, ZIPs, etc... > * What tool(s) are you using to restore? Again either Bacula or some custom scripts. > * What is the type of the filesystem that is the destination of the > restore? Usually UFS or ZFS; could be something else. > So, the backup source filesystem and the restore destination filesystems > are both ZFS (?). Possibly, but not always. > The upper Unix filesystem path should be an empty directory. Should, but not always is. Sometimes I found "forgotten" files in the directory which is the target of the nullfs mount. Of course those files are usually hidden and probably useless, but must be taken into account. > I believe it is a result of the 'mountpoint' properties of the two ZFS > file systems and how ZFS represents filesystem snapshots in the Unix > file system. No, this can happen with UFS too. bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a0ee11a-eb32-7ae2-256f-ad1b00d1e49d>