system services ndmp log start
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
(DEPRECATED)-Start logging for the specified NDMP session
Availability: This command is available to cluster administrators at the advanced privilege level.
Description
This node-scoped NDMP command is deprecated. Node-scoped NDMP functionality may be removed in a future release of Data ONTAP. Use the Vserver-aware "vserver services ndmp log start " command. |
This command is used to start logging on an active NDMP session on a node. You can start logging two different kinds of sessions. The NDMP server
session manages all NDMP tasks on the node. If you want to log information regarding the NDMP server, use server
with the -session-id
parameter to enable logging. If you want to log information about a particular NDMP session, for example a restore operation, then determine the session ID for the session using the "system services ndmp status" command and use that ID with the -session-id
parameter to enable logging.
Parameters
-node {<nodename>|local}
- Node (privilege: advanced)-
This parameter specifies the node.
-session-id {<integer>|server}
- Session Identifier (privilege: advanced)-
This parameter specifies the NDMP session-id on which logging needs to be started. The session-id is associated with a unique NDMP session. Specify
server
to start logging on the NDMP server session. -filter <text>
- Level Filter (privilege: advanced)-
Use this parameter to specify the filter for a particular session ID. This parameter controls the NDMP modules for which logging is to be enabled. This parameter can take five values. They are as follow :
all
,none
,normal
,backend
or"filter-expression"
. The default value for this isnone
.-
all
turns on logging for all modules. -
none
disables logging for all modules. -
normal
is a short cut parameter that enables logging for all modules exceptverbose
andio_loop
. The equivalent filter string isall-verbose-io_loop
-
backend
is a short cut parameter that enables logging for all modules exceptverbose
,io_loop
,ndmps
andndmpd
. The equivalent filter string isall-verbose-io_loop-ndmps-ndmpp
-
(filter-expression)
is a combination of one or more modules for which logs needs to be enabled. Multiple module names can be combined using following operators : -
-
to remove the given module from the list of specified modules in the filter string. For example the filterall-ndmpp
will enable logging for all modules but notndmpp
. -
^
to add the given module or modules to the list of modules specified in the filter string. For example the filterndmppmoverdata
will enable logging forndmpp
,mover
anddata
.
The possible module names and a brief description is given below:
-
+---------------------------------------------------+ | Modules | Description | +---------------------------------------------------+ | verbose | verbose message | | io | I/O process loop | | io_loop | I/O process loop verbose messages | | ndmps | NDMP service | | ndmpp | NDMP Protocol | | rpc | General RPC service | | fdc_rpc | RPC to FC driver service | | auth | Authentication | | mover | NDMP MOVER (tape I/O) | | data | NDMP DATA (backup/restore) | | scsi | NDMP SCSI (robot/tape ops) | | bkup_rpc | RPC to Backup service client | | bkup_rpc_s | RPC to Backup service server | | cleaner | Backup/Mover session cleaner | | conf | Debug configure/reconfigure | | dblade | Dblade specific messages | | timer | NDMP server timeout messages | | vldb | VLDB service | | smf | SMF Gateway messages | | vol | VOL OPS service | | sv | SnapVault NDMP extension | | common | NDMP common state | | ext | NDMP extensions messages | | sm | SnapMirror NDMP extension | | ndmprpc | NDMP Mhost RPC server | +---------------------------------------------------+
Examples
The following example shows how to start logging on a specific NDMP session 33522, running on the node cluster1-01 with filter normal.
cluster1::*> system services ndmp log start -node cluster1-01 -session-id 33522 -filter normal
The following example shows how to start logging on the NDMP server session, on the node cluster1-01 with filter all.
cluster1::*> system services ndmp log start -session-id server -filter all -node cluster1-01