Networker

Re: [Networker] NetWorker 7.4 self reporting

2008-08-11 11:40:58
Subject: Re: [Networker] NetWorker 7.4 self reporting
From: Fazil Saiyed <Fazil.Saiyed AT ANIXTER DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 11 Aug 2008 10:34:59 -0500
Hello,
I agree, there is enough information in the notification, Gui to 
accomplish any intervention, unless, you have developed custom scripts  to 
augment networker functionality to take certain actions, i.e automating 
device cleaning, group restarts , cloning etc  based on the failure code 
and you have limited staffing at Night to carry out the interventions when 
most problems with backup occur.
HTH



Bruce Breidall <Bruce.Breidall AT CONCUR DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
08/11/2008 10:08 AM
Please respond to
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>; Please respond 
to
Bruce Breidall <Bruce.Breidall AT CONCUR DOT COM>


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
Re: NetWorker 7.4 self reporting






Why couldn't you just scrap the script and use the native notifications
ability of NW. The group notification seems to work quite well with
smtp, and they include all daemon.log entries.

Then you would have one less thing to worry about in the future.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Fazil Saiyed
Sent: Monday, August 11, 2008 9:20 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NetWorker 7.4 self reporting

Hello,
Have you tried
.type nsr group
show name;last start;last end;status;
print nsr group
HTH



rmumford <networker-forum AT BACKUPCENTRAL DOT COM> 
Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
08/10/2008 05:30 PM
Please respond to
NETWORKER AT LISTSERV.TEMPLE DOT EDU


To
NETWORKER AT LISTSERV.TEMPLE DOT EDU
cc

Subject
NetWorker 7.4 self reporting






Thanks for the reply. Its Windows server 64 bit. After a reboot, a
rename 
of the jobsdb folder and the tmp folder, and on a different group, I am 
now getting a completion line. Believe me I do not understand either.

X:\>nsradmin
NetWorker administration program.
Use the "help" command for help.
nsradmin> . type:NSR Group; name: re-run
Current query set
nsradmin> show
Will show all attributes
nsradmin> print
                        type: NSR group;
                        name: Re-Run;
                     comment: to re-run failed backups;
                    snapshot: False;
                   autostart: Disabled;
                 autorestart: Enabled;
                  start time: "16:00";
                  last start: "Sun Aug 10 14:08:58 2008";
                    last end: "Sun Aug 10 14:14:23 2008";
                    interval: "24:00";
              restart window: "12:00";
           force incremental: Yes;
         savegrp parallelism: 0;
              client retries: 1;
                      clones: No;
                  clone pool: Default Clone;
           success threshold: Warning;
                     options: Manual restart;
                       level: ;
                     printer: ;
                    schedule: ;
               schedule time: ;
             expiration time: ;
          inactivity timeout: 30;
   File inactivity threshold: 30;
File inactivity alert threshold: 30;
                   work list: ;
                  completion: mossext01, All, "failed:incr:save",
"* mossext01:All logfile has no output
     * <SEVERE> :  Connection refused",
                              mossext01, index, "succeeded:9:index",
"  nt2legatok1.emn.com: index:mossext01 level=9,   4289 KB 00:00:01
45 
fi\
les";
                      status: idle;
             Snapshot Policy: Daily;
               Snapshot Pool: Default;
nsradmin>

+----------------------------------------------------------------------
|This was sent by rmumford AT eastman DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and
type 
"signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this

list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type 
"signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER



To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>