: From: dnb@ccs.neu.edu [mailto:dnb@ccs.neu.edu]
: Quick question: once upon a time, machine-gone-kablooey autosupport : mail was only sent when a filer booted. It was the Yoda scenario : ("there is no retry, only do!"). If something went awry in that : sending, the message was just dropped on the floor, no queuing, no : retrying.
Beginning in ONTAP 5.3.4, autosupport that can't be sent is queued and retried periodically, with messages written to /etc/messages describing what's going on.
The autosupport mail eventually gets dropped if the net or NIS (or whatever) situation isn't fixed, and it's dropped if the filer reboots before the mail goes out, but when the filer eventually comes up, we can patch together much of what happened from the message log.
The retry window is 15 minutes in 5.3.4, lengthened to an hour in the "next major release".
- Brian
-- Brian Hackworth hackwort@netapp.com Network Appliance 408.822.6654 Sunnyvale, CA USA
You know, RFC 1183 has some guidelines regarding retries and timeouts during mail delivery. Perhaps Netapp should look at implementing those standards with regards to autosupport. (Or whatever has superceded 1183; I have not checked recently.)
Bruce
Hi,
I would like to hear how other sites do offsite backups using veritas software. The duplication utility in 3.2 appears to be problematic when using NDMP style backups.
Has anyone else had experience using duplications? Any other suggestions other than backing up the data twice, once for onsite and once for offsite?
Any comments will be helpful.
Thanks
Manny