hi,
i noticed that dump messages were not being recorded in the messages file. i did not have a syslog.conf file so i created one like this:
*.* /etc/messages *.* /dev/console
no change. am i doing something wrong? f760 ontap 5.36r2.
thanks.
hi,
i noticed that dump messages were not being recorded in the messages file. i did not have a syslog.conf file so i created one like this:
*.* /etc/messages *.* /dev/console
no change. am i doing something wrong? f760 ontap 5.36r2.
No. Unfortunately, in current Ontap releases, dump information does not get written to the messages file.
RFE 2345 has been filed on this problem. Currently the bug description is not available on NOW, but is slated to be, soon.
For now, you either want to capture dump logs by running via rsh, or if you use an NDMP client, they generally capture the dump messages in their logs.
Stephen Manley Data Availability and Management Spice Girl
stephen@netapp.com (Stephen Manley) writes: [...]
No. Unfortunately, in current Ontap releases, dump information does not get written to the messages file.
RFE 2345 has been filed on this problem. Currently the bug description is not available on NOW, but is slated to be, soon.
For now, you either want to capture dump logs by running via rsh, or if you use an NDMP client, they generally capture the dump messages in their logs.
Is the proposal to copy (some of) the dump messages to the syslog facility? Always, or as an option?
It's important that the output of a rsh'd "dump" continues to come back down the stdout channel, as post-analysing it is the only way to know whether the dump has worked. [Cue to resume the November 2000 thread about "rsh/ssh return codes"!]
Chris Thompson University of Cambridge Computing Service, Email: cet1@ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.
On Thu, 8 Mar 2001, Chris Thompson wrote:
stephen@netapp.com (Stephen Manley) writes: [...]
No. Unfortunately, in current Ontap releases, dump information does not get written to the messages file.
RFE 2345 has been filed on this problem. Currently the bug description is not available on NOW, but is slated to be, soon.
For now, you either want to capture dump logs by running via rsh, or if you use an NDMP client, they generally capture the dump messages in their logs.
Is the proposal to copy (some of) the dump messages to the syslog facility? Always, or as an option?
It's important that the output of a rsh'd "dump" continues to come back down the stdout channel, as post-analysing it is the only way to know whether the dump has worked. [Cue to resume the November 2000 thread about "rsh/ssh return codes"!]
The plan is actually to record dump events to a log file. The events include when a dump started, when it switched tape, when it finished, whether it completed successfully, etc. It does not intend to log the entire dump message output, and the messages will likely to come down the rsh stdout pipe as usual.
=) Steve
On Thu, Mar 08, 2001 at 04:46:14PM -0800, Yinfung Fong wrote:
The plan is actually to record dump events to a log file. The events include when a dump started, when it switched tape, when it finished, whether it completed successfully, etc. It does not intend to log the entire dump message output, and the messages will likely to come down the rsh stdout pipe as usual.
Would these log messages be stored for manually executed dumps in addition to NDMP executed dumps? That would be extremely handy since some backup products don't do the best job of sorting out the output of the dump command.
It would also be great if the level of detail could be throttled via an option, similar to "ndmpd debug". While the events in a log file would be helpful for normal usage, it would be great to turn up the resolution and recieve all the standard messages that come through dump if we're troubleshooting a problem.
In any case, we're glad this is a priority!
-- Jeff
-- ---------------------------------------------------------------------------- Jeff Krueger, NetApp CA E-Mail: jeff@qualcomm.com Senior Engineer Phone: 858-651-6709 NetApp Filers / UNIX Infrastructure Fax: 858-651-6627 QUALCOMM, Inc. IT Engineering Web: www.qualcomm.com
On Thu, Mar 08, 2001 at 05:20:29PM -0800, Jeffrey Krueger wrote:
Would these log messages be stored for manually executed dumps in addition to NDMP executed dumps? That would be extremely handy since some backup
What I really mean here is, will it work for both "rsh dump/restore" and NDMP dump/restore? We use NDMP and would still like this feature. My original wording was a bit confusing. =)
-- Jeff
On Thu, 8 Mar 2001, Jeffrey Krueger wrote:
On Thu, Mar 08, 2001 at 05:20:29PM -0800, Jeffrey Krueger wrote:
Would these log messages be stored for manually executed dumps in addition to NDMP executed dumps? That would be extremely handy since some backup
What I really mean here is, will it work for both "rsh dump/restore" and NDMP dump/restore? We use NDMP and would still like this feature. My original wording was a bit confusing. =)
I believe it should work for both native and NDMP dumps.
=) Steve
On Thu, Mar 08, 2001 at 05:59:12PM -0800, Yinfung Fong wrote:
On Thu, 8 Mar 2001, Jeffrey Krueger wrote:
On Thu, Mar 08, 2001 at 05:20:29PM -0800, Jeffrey Krueger wrote:
Would these log messages be stored for manually executed dumps in addition to NDMP executed dumps? That would be extremely handy since some backup
What I really mean here is, will it work for both "rsh dump/restore" and NDMP dump/restore? We use NDMP and would still like this feature. My original wording was a bit confusing. =)
I believe it should work for both native and NDMP dumps.
Cool!
How about the ability to turn up the resolution and see full dump output in the file, or turn it down to just see the high-level events?
-- Jeff
Stephen Manley wrote:
For now, you either want to capture dump logs by running via rsh, or if you use an NDMP client, they generally capture the dump messages in their logs.
Does anyone know how to see the NDMP dump output messages from within Legato or Veritas? We have tested both products, but neither allowed us to view the NDMP dump messages like we do in Budtool. We checked all the logs, but maybe there is a logging option that needs to be turned on?
Moshe
-- ----------------------------------------------------------------------------- Moshe Linzer | On the Internet, Unix Systems Manager | National Semiconductor, Israel | nobody knows you're a moron. Phone: 972-9-970-2247 | Fax: 972-9-970-2001 | - Network Magazine Email: moshel@nsc.com | -----------------------------------------------------------------------------
-
Chris Thompson -
Jeffrey Krueger -
Moshe Linzer -
neil lehrer -
Stephen Manley -
Yinfung Fong