
Originally Posted by
Brotherbbad
however the DIFF's are still throwing this:
/tmp/restore/store/0/11/msg/0/1040-1703.msg must be removed, but does not match expected type, remove it anyway ? [return = OK | Esc = cancel]
Continuing...
...
Am I missing something or not doinf something correctly?
Here is a forum discussing the issue, including posts from the author of dar:
support requests for DAR - Disk ARchive
The author suggests using the -wa option:
Code:
-wa, --no-warn=all This implies the -w option, and means that over avoiding warning for file overwriting, DAR also avoid signaling a
file about to be removed when its type is not the expected one. File are removed when they have been recorded as
deleted since the archive of reference. At restoration of the differential archive, if a file of the given name
exists, it is remove, but if the type does not match the file that was present at the time of the archive of ref-
erence (directory, plain file, fifo, socket, char or block device, etc.), a warning is normally issued to prevent
the accidental removal of data that was not saved in the backup of reference. (See also -k option) To me, this might be a bug, since obviously the file types should be the same.
- Make sure you have the latest version of dar.
- When you get the message, see if you can compare the file in an older dar, when it still existed, to the file on the failover server. If one is a soft link, e.g., and the other a file, it would give this error.
- The author mentions that if you got this error when restoring from scratch "there may be something wrong in the way dar is used." Are you restoring over the top of any files, or to an empty directory? Obviously, if the dar command in the script is not correct, we'd all like to know. I have done full and diff restores to another server before, and have not gotten this error.
- You might also consider asking on the dar support mailing list, https://lists.sourceforge.net/lists/...fo/dar-support.