Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ufsdump and UFS logging
0 views
Skip to first unread message
Bob Fillmore
Jun 8, 2001, 3:52:58 AM6/8/01
to
A classic problem with Solaris backup/restore is that ufsdump cannot
accurately
back up a mounted filesystem because the filesystem structures could
change
during the backup. Solaris 7 introduced the new UFS logging feature,
where
filesystem changes are recorded in a transaction log within the
filesystem itself.
This raises a couple of questions:
1) When the filesystem is restored on a new disk, will the captured UFS
transaction log
be processed to at least partially correct the inaccurate
filesystem snapshot on tape?
2) Could ufsdump be modified to temporarily suppress flushing of the
UFS log
during the dump, which would allow ALL inconsistancies to be fixed
after the restore?
accurately
back up a mounted filesystem because the filesystem structures could
change
during the backup. Solaris 7 introduced the new UFS logging feature,
where
filesystem changes are recorded in a transaction log within the
filesystem itself.
This raises a couple of questions:
1) When the filesystem is restored on a new disk, will the captured UFS
transaction log
be processed to at least partially correct the inaccurate
filesystem snapshot on tape?
2) Could ufsdump be modified to temporarily suppress flushing of the
UFS log
during the dump, which would allow ALL inconsistancies to be fixed
after the restore?
Comments?
- Bob Fillmore
Raf LaPietra
Jun 8, 2001, 9:34:46 AM6/8/01
to
In article <3B208459...@home.com>,
Bob Fillmore <fill...@home.com> wrote:
>A classic problem with Solaris backup/restore is that ufsdump cannot
>accurately
>back up a mounted filesystem because the filesystem structures could
>change
>during the backup. Solaris 7 introduced the new UFS logging feature,
>where
>filesystem changes are recorded in a transaction log within the
>filesystem itself.
>This raises a couple of questions:
> 1) When the filesystem is restored on a new disk, will the captured UFS
>transaction log
> be processed to at least partially correct the inaccurate
>filesystem snapshot on tape?
Bob Fillmore <fill...@home.com> wrote:
>A classic problem with Solaris backup/restore is that ufsdump cannot
>accurately
>back up a mounted filesystem because the filesystem structures could
>change
>during the backup. Solaris 7 introduced the new UFS logging feature,
>where
>filesystem changes are recorded in a transaction log within the
>filesystem itself.
>This raises a couple of questions:
> 1) When the filesystem is restored on a new disk, will the captured UFS
>transaction log
> be processed to at least partially correct the inaccurate
>filesystem snapshot on tape?
No.
> 2) Could ufsdump be modified to temporarily suppress flushing of the
>UFS log
> during the dump, which would allow ALL inconsistancies to be fixed
>after the restore?
>
o.
>Comments?
This has a fix/workaround in the latest Soaris 8. You can use fssnap to create
a "backing store" for your file system while you need it to be stable.
>
> - Bob Fillmore
>
>
0 new messages