Quote:
Originally Posted by 3RiversTechAdmin A good NFS implementation has no issues. |
when do so there can always be an issue. so thats why it would be good to know exactly how the backupscript react under certain circumstances
for example - host can be down - maintainance - usually in the night low traffic time exactly when the backup runs :-)
switch can be dead or down at the worst time - when backup runs
some things get reconfigured or moved to antoher host and the zimbra host isnt the first updated client - so good to know if that can be a desaster
and many other possibilitys special that one we dont even think about (that the one im really afraid of :-)
so its true in the normal world if you do things right nfs is like a rock - ife mine running over a year without connection loss or troubles or even restart or remount anything.
but you cant rely on that an an implementation. so you need a failsave plan/implemantation (or better the backupscript should have) with setups like that - that why im asking if anyone has anyidea in which way that backup is operating
if the script simply fail on connect loss and redoo everything next day its fine - you can write a simple watchdog get an notification that something is missing and make a manual backup if one day is a fail
but what if backupscript dont rewrite last day backup and go ahead only with new piece, so a piece of an incremental backup is missing, you may loose important parts of your backup so thats why i wanna know exactly how the backup script works and do things. to bad that i could not find any documenation about its behaivior in case x