Unsolved
This post is more than 5 years old
161 Posts
1
5676
Incremental Index-Backup
Hello together,
I have a separate pool configured within NetWorker to backup the index and bootstrap informations. I always thought that NetWorker would do an incremental/level save of these two backup pieces.
Now I recognized that it is always a FULL
mminfo -avot -q 'pool=INDEX,savetime>24 hours ago' -r level,name,savetime
| full bootstrap | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
| full index:client | 12/14/17 |
The configuration of the INDEX pool is mostly default, just the save set field contains this:
index: *
bootstrap
And of course a dedicated DataDomain device is used.
Is that regular behaviour of NetWorker?
Cheers
Jan
bingo.1
2.4K Posts
1
December 19th, 2017 08:00
Please post the solution later - I am not the only one who would be interested.
ble1
14.3K Posts
1
December 20th, 2017 15:00
This can happen when someone messes up with /etc/hosts and changes order of short and long names (fqdn). I agree that having alias in server's client should make NW smart enough this is the same client, but something somewhere in the code makes it act differently.