I had my global and custom dumptypes set to dumpcycle 0, but some backups are being
done at level 1 and level 2 is this because I have index set or because I had two
previous configs perform full and incremental backups on the same file systems before?
I used a config "Full" this time while last time I used a config "All" and
"Incremental" which both had indexes set.
The previous "All" config did not have dumpcycle 0 set specially or any strategy set
at all. I just run it with these settings
In "Full" (the current config I am trying to use), I had
define dumptype mytar {
global
program "GNUTAR"
compress server fast
dumpcycle 0
index
priority high
}
In "All" (the previous config), I had
define dumptype mytar {
global
program "GNUTAR"
compress server fast
index
priority high
}
In "Incremental" (another previous config), I had
define dumptype mytar {
global
program "GNUTAR"
compress server fast
index
no full
priority high
}
Now one would think my "Full" config will track records indecently and be able to
perform a dumpcycle 0 (full dump) everytime it is run, but it not only makes level 1
and 2 backups of some file systems, but I also see this messages:
planner: last full dump of myhost1 /export on tape overwritten in 1 run
planner: last full dump of myhost2 /home on tape overwritten in 1 run
planner: last full dump of myhost3 /var on tape overwritten in 1 run
I don't think it is switching to level 1 and 2s because my holding disk is low on
space. I am backing everything to the holding disk since my tape changer has been sent
in for warranty service and won't be back for a few weeks.
Now i read that I should be using this in my crontab with my "amdump Full"
amadmin <config> force <host>
In my case if my amdump runs at 12:10 midnight every sun, I should have
the amadmin I should have
0 0 * * sun amadmin Full force myhost1
0 0 * * sun amadmin Full force myhost2
0 0 * * sun amadmin Full force myhost3
10 0 * * sun amdump Full
Is this correct and why do I have to use amadmin if I already have dumpcycle 0 setup?
Thanks.
