Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+backup\s+is\s+incremented\s+to\s+full\s+backup\s+after\s+a\s+bare\s+metal\s+restore\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+backup\s+is\s+incremented\s+to\s+full\s+backup\s+after\s+a\s+bare\s+metal\s+restore\s*$/: 2 ]

Total 2 documents matching your query.

1. [Bacula-users] backup is incremented to full backup after a bare metal restore (score: 1): Author: morlix <morlix AT morlix DOT de>; Date: Fri, 22 Feb 2013 08:58:02 +0100; Hello bacula users, three days ago one of my servers raid 5 died completly and i had to do a bare metal restore. This restore works fine, except the thing that i got two messages about directories wh; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2013-02/msg00273.html (12,829 bytes)
2. Re: [Bacula-users] backup is incremented to full backup after a bare metal restore (score: 1): Author: Martin Simmons <martin AT lispworks DOT com>; Date: Fri, 22 Feb 2013 16:24:32 GMT; This is normal -- a restore will modify the ctime of every file, so they will appear to be newer than the last full backup. You could fix this by doing a backup with level=full. You could also try u; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2013-02/msg00279.html (13,356 bytes)

Current List: 1 - 2
Page: [1]