On Wed, Aug 03, 2005 at 01:52:13PM +0200, Florian Reitmeir wrote: > On Mit, 03 Aug 2005, Steve Langasek wrote:
> > On Wed, Aug 03, 2005 at 12:36:29PM +0200, Florian Reitmeir wrote:
> > > On Die, 02 Aug 2005, Steve Langasek wrote:
> > > > On Tue, Aug 02, 2005 at 09:10:28PM +0200, Florian Reitmeir wrote:
> > > > > Package: samba
> > > > > Version: 3.0.14a-6
> > > > > Severity: important
> > > > > Tags: patch
> > > > > this also applies to the samba of the stable debian distri.
> > > > > samba uses many .tdb files, and there is a nice small tool within the
> > > > > package to dump those files, or check them.
> > > > > but there is no tool to dump them, rotate them .. if written a small
> > > > > shell script which should included in some cron.
> > > > No, these are not log files that need to be rotated (expired) for space
> > > > reasons, and it's not appropriate for individual packages to attempt to
> > > > impose backup policies for the system.
> > > the manpage of tdbbackup itself claims that the tool should run in the
> > > samba
> > > startup script to verify the tdb files.
> > No, it says that the tool *may* be used at various points to verify the tdb
> > files.
> for example "This tool may also be used to verify the integrity of the .tdb
> files prior to samba startup or during normal operation."
> > > if the tdb files not dumped there is no way of rescue the system.
> > Rescue it from what, exactly? In practice, tdb corruption is not at all
> > common in the absence of a filesystem bug, so I don't see any reason to
> > create such backup files outside of a system backup routine.
> oh the last time, a week a go a system crashed. i had a backup, rsnapshot,
> all file there but the samba had an very long uptime, so there were never any
> complete backups made from the tdb files.
> so all userpasswords were gone
> all domain machine accounts too
> there is a small backup-cron for the smbpasswd files, but in the current
> default config, smbpasswd files aren't used anymore.
> starting/stopping the daemon everytime before backup is an option, but a very
> bad one, because there are tools which do better, and all machines (i speak
> from windows xp clients) have the be rebooted too, so the can logon on the
> domain again (i know, windows has to be rebooted often) and in this special
> case there are some machines with special software on it which run 24h/7days.
Ok, but the manpage also says:
The tdbbackup utility can safely be run at any time. It was designed so
that it can be used at any time to validate the integrity of tdb files,
even during Samba operation.
So why would you want to (or need to) start/stop samba at all for this? It
sounds to me like you should simply be snapshotting the necessary tdb files
as part of your backup routine.
--
Steve Langasek
postmodern programmer
signature.asc
Description: Digital signature
