On Sun, Sep 30, 2012 at 12:32:17AM +0000, Kervin L. Pierre wrote:
> Hi,
>
> I have a diskllist with 2 folders
> /a/b
> /d/c
>
> The current schedule works perfectly except for one thing.
> Whenever 'b' gets a full, level '0' dump then folder 'c' should
> as well. Having a situation where I have a full dump to restore
> for folder 'b' but not of folder 'c' would be a very bad thing.
>
I'm not sure I understand your situation. Do you have so few
tapes that your only level 0 dump might be overwritten by an
incremental dump? I try to have multiple dumpcycles of tapes
so this doesn't happen.
Recovery can be done as a "give me the files as of date xyz".
Depending on when the level 0 before date xyz was done, it
may require just one tape (the level 0) or several tapes,
the level 0 and one or more incrementals.
> Is there a way I could make sure the config does the same
> level backup on all the folders in the disklist?
>
I don't know of a way to specify synchronize these DLE.
But here are two possible workarounds.
Schedule the level 0's yourself. Have your dumptype specify
no full dumps and periodically use "amadmin force" to cause
a full dump. This can be from the command line or from cron.
The other way is to combine them in a single DLE. The entry
would look something like:
ClientHostName ANameForThisEntry <FullPathToACommonDir>
HostName EntryName StartDir {
dumptype
<other options>
include file "a/b"
include file append "d/c"
}
HostName is the client's
EntryName is what to call this entry in reports etc.
StartDir is a the full path to a directory in common
to both /a/b and /d/c, "/" in this example.
HTH,
Jon
--
Jon H. LaBadie [email protected]
11226 South Shore Rd. (703) 787-0688 (H)
Reston, VA 20190 (609) 477-8330 (C)
