R
Rob Fitzpatrick
Guest
We do something similar to what pfred described: archive to a local directory on prod; from there, copy to remote system's input directory; remove from aiarcdir when successfully copied; a cron job on DR rolls forward files from the input directory to the target and moves them to an archive directory. I had a client site where the primary aiarcdir (there were two) was an NFS share to DR and it didn't work well. There was a network disruption, the NFS mount was stale and file copies no longer happened. But the production system could still see the directory, even though it now had no contents, so the daemon didn't switch to the secondary aiarcdir and stopped archiving/switching extents. We couldn't even make it switch directories manually. The daemon got into an unresponsive state, couldn't be shut down or signalled, and eventually we had to restart the DB to recover the situation. So in theory it's nice to archive directly to a remote box but I got burned by an unreliable network. I'd be interested to hear what others do.
Continue reading...
Continue reading...