Schedule isn't followed

Are you sure someone didn't play with it manually (like running the probe)? Because it says groups is disabled and it did run at the time when group is not supposed to run anyway and it looks like a probe to me. Also, the schedule time seems to be correct (reported to be "Thu Jun 1 03:30:00 2006").

If you check mm and daemon.log can you confirm that group really did run? (BTW, there is no need for schedule to be set on both client and group - choose one of them, but have in mind that group setting will override client's one).

Is it possible you simly did a probe for a check? Such things will also update NSR group resource? Check following:

C:\>savegrp -pv Default
hcrvelin:All                              level=incr
05/16/06 07:36:04 savegrp: Group will not limit job parallelism
05/16/06 07:36:04 savegrp: hcrvelin:probe                                started
savefs -s hcrvelin -c hcrvelin -g Default -p -l full -R -v
  savefs hcrvelin: succeeded.
05/16/06 07:36:04 savegrp: hcrvelin:probe succeeded.
--- Probe Summary ---
 
hcrvelin:All                      level=full, dn=-1, mx=0, vers=ssbrowse, p=4
hcrvelin:All            level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006
hcrvelin:ASR:\                     level=full, dn=0, mx=1, vers=ssbrowse, p=4
hcrvelin:ASR:\          level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006
hcrvelin:SYSTEM FILES:\            level=full, dn=1, mx=1, vers=ssbrowse, p=4
hcrvelin:SYSTEM FILES:\ level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006
hcrvelin:SYSTEM DB:\               level=full, dn=2, mx=1, vers=ssbrowse, p=4
hcrvelin:SYSTEM DB:\    level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006
hcrvelin:SYSTEM STATE:\            level=full, dn=3, mx=1, vers=ssbrowse, p=4
hcrvelin:SYSTEM STATE:\ level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006
hcrvelin:C:\                       level=full, dn=4, mx=1, vers=ssbrowse, p=4
hcrvelin:C:\            level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006
hcrvelin:index                    level=full, dn=-1, mx=0, vers=ssbrowse, p=4
hcrvelin:index          level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006
 
C:\>nsradmin
NetWorker administration program.
Use the "help" command for help.
nsradmin> option hidden
Hidden display option turned on
 
Display options:
        Dynamic: Off;
        Hidden: On;
        Resource ID: Off;
nsradmin> option dynamic
Dynamic display option turned on
 
Display options:
        Dynamic: On;
        Hidden: On;
        Resource ID: Off;
nsradmin> show
Will show all attributes
nsradmin> print type: NSR group; name: Default
                        type: NSR group;
                        name: Default;
                     comment: ;
                    snapshot: False;
                   autostart: Disabled;
                 autorestart: Disabled;
                    stop now: False;
                  start time: "3:33";
                  last start: ;
                    last end: ;
                    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: ;
                       level: ;
                     printer: ;
                    schedule: ;
               schedule time: ;
          inactivity timeout: 30;
                   work list: ;
                  completion: hcrvelin, "ASR:\\", "succeeded:full:save",
"hcrvelin:ASR:\\          level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006",
                              hcrvelin, "SYSTEM FILES:\\",
                              "succeeded:full:save",
"hcrvelin:SYSTEM FILES:\\ level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006",
                              hcrvelin, "SYSTEM DB:\\", "succeeded:full:save",
"hcrvelin:SYSTEM DB:\\    level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006",
                              hcrvelin, "SYSTEM STATE:\\",
                              "succeeded:full:save",
"hcrvelin:SYSTEM STATE:\\ level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006",
                              hcrvelin, "C:\\", "succeeded:full:save",
"hcrvelin:C:\\            level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006",
                              hcrvelin, index, "succeeded:full:index",
"hcrvelin:index          level=full, pool=Default, save as of Tue May 16 07:36:05 GMT+0200 2006";
          progress file name: "C:\\Program Files\\Legato\\nsr\\tmp\\sec\\sg\\Default\\pr000002";
                      status: idle;
             Snapshot Policy: Daily;
               Snapshot Pool: Default;
                    hostname: hcrvelin;
               administrator: "group=Administrators,host=hcrvelin",
                              "user=administrator,host=hcrvelin",
                              "user=system,host=hcrvelin",
                              "user=*,host=hcrvelin";
          ONC program number: 390109;
          ONC version number: 2;
               ONC transport: TCP;
nsradmin>

As you can see, it doesn't take backup to create state as you have so I would check daemon.log and media database to confirm if the group run in the first place. I suspect above could be your "issue" as we also do not see time and size saved information so it does look like a probe to me.

I'm quite sure no one played with anything manually. However I did enable and quickly disable the group at that time and it did send another email. I have now disabled the group until this is fixed since the scheduled time under "Group Control" shows as 3:30 am of the next day every time I enable it. I had enabled this group on the weekend and thought it would execute as scheduled, however it wrote to a new tape that was inserted for a different pool since it was waiting for a tape.

Here is a small excerpt from the Daemon.log

05/14/06 05:52:10 nsrd: media critical event: Waiting for 1 writable volumes to backup pool '1st
for OFfsite' tape(s) on fw2.localdomain
05/14/06 06:00:00 nsrexecd: Diagnostic: Reverse DNS lookup failed for address 10.1.1.11
05/14/06 06:00:01 savegrp: Diagnostic: Reverse DNS lookup failed for address 10.1.1.11
05/14/06 06:00:01 nsrd: savegroup info: starting Full 1n15 Diff from Full (with 4 client(s))
05/14/06 06:00:05 nsrd: media warning: /dev/nst0 reading: Success
05/14/06 06:00:05 nsrd: media info: suggest mounting Week.2.Day.7 on fw2.localdomain for writing
 to pool 'Full 1n15 Diff from Full'
05/14/06 06:00:05 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool 'Full
1n15 Diff from Full' tape(s) on fw2.localdomain
05/14/06 06:00:15 nsrmmd #4: Start nsrmmd #4, with PID 11095, at HOST fw2.localdomain
05/14/06 06:00:57 nsrd: media warning: /dev/nst0 reading: Success
05/14/06 06:01:02 nsrd: media info: suggest labeling volume in device /dev/nst0 on fw2.localdomain for writing  to pool '1st for OFfsite'
05/14/06 06:01:02 nsrd: /dev/nst0 Verify label operation in progress
05/14/06 06:01:02 nsrd: media warning: /dev/nst0 reading: Success
05/14/06 06:01:03 nsrd: media warning: /dev/nst0 reading: no tape label found
05/14/06 06:01:03 nsrd: /dev/nst0 Label operation in progress
05/14/06 06:01:03 nsrd: media info: dlt8000 tape  will be over-written
Using volume name `Month-06' for pool `1st for OFfsite'
05/14/06 06:03:06 nsrd: media event cleared: Waiting for 1 writable volumes to backup pool '1st for OFfsite' tape(s) on fw2.localdomain
05/14/06 06:03:06 nsrd: fw2.localdomain:bootstrap saving to pool '1st for OFfsite' (Month-06)

When I noticed this had happened I had to delete the tape from that pool and relabel it and perform the other backup.

Also you mentioned I have a scheduled time as "Thu Jun 1 03:30:00 2006", I had input this information manually.

Could the problem related to the interval of 24 hours? In the email notification I get from a backup it actually shows that no data is backed up except for the backup server bootstrap. What I would like is no request for a tape to occur on days other than the 1st of the month. Will I need to wait and start this schedule on the 1st of the month exactly? Or will I need to run the backup manually via a cron job?

Here is a copy of the email notification:

NetWorker savegroup: (notice) 1st for Offsite completed, total 4 client(s), 0 Hostname(s) Unresolved, 0 Failed, 4 Succeeded. 
Start time:   Sun May 14 03:30:00 2006
End time:     Sun May 14 06:03:07 2006
 
--- Successful Save Sets ---
 
  db1.localdomain: /gtk/backups/dbdumps level=skip,  0 KB 00:00:00      0 files
  db1.localdomain: index:db1.localdomain level=skip, 0 KB 00:00:00      0 files
 
  fw1.localdomain: /gtk/firewall    level=skip,      0 KB 00:00:00      0 files
  fw1.localdomain: index:fw1.localdomain level=skip, 0 KB 00:00:00      0 files
 
  ov1.localdomain: /gtk/overseer    level=skip,      0 KB 00:00:00      0 files
  ov1.localdomain: index:ov1.localdomain level=skip, 0 KB 00:00:00      0 files
 
* fw2.localdomain:bootstrap save: Diagnostic: Reverse DNS lookup failed for address 10.1.1.11
* fw2.localdomain:bootstrap save: Diagnostic: Reverse DNS lookup failed for address 10.1.1.11
  fw2.localdomain: bootstrap        level=full,     59 KB 00:26:00    106 files
* fw2.localdomain:bootstrap lpr: error - no default destination available.
* fw2.localdomain:bootstrap printing bootstrap information failed (reproduced below).
* fw2.localdomain:bootstrap 
* fw2.localdomain:bootstrap 
* fw2.localdomain:bootstrap May 14 06:03 2006  fw2.localdomain's bootstrap information Page 1
* fw2.localdomain:bootstrap 
* fw2.localdomain:bootstrap      date     time      level ssid        file  record   volume
* fw2.localdomain:bootstrap      05/13/06 07:54:57   full 3144017201    14       0   Week.2.Day.7
* fw2.localdomain:bootstrap      05/14/06 05:37:07   full 3110542458     2       0   Month-06

We only see request for tape here - no actual backup.


And that would be probably expected thing; see:
http://forums.emc.com/forums/thread.jspa?forumID=68&threadID=33502


You can do that, but you will need to mess up with other parameters (to avoid index and bootstrap backup).


The only strange thing there is that boostrap backup tales 3 hours. In case of DDS and slow backups (dlt8k) I could understand that tape drive on server is not available, but if it is then... Also, fixing that DNS entry for backup server would be a good idea... NetWorker is name resolution touchy software

Okay well I handled the bootstrap backup as it is now part of another group.

However I do need to make changes so the backup is run only on the 1st of every month. Since this is a manual tape load system I need to ensure it doesn't just write to any tape that is inserted. (i.e. a blank tape meant for another backup)

Will I need to do this via a cron job or can you tell me how to accomplish this within the networker administrator or other tool?

Thank you for all the help thus far

Oh and also the hosts have multiple network adapters which cannot have hostnames associated with them so those will need to stay as is (it still works as it has been running for 2 years with a different backup plan)


Message was edited by:
Cory Thibault

If you put the group into the pool you should not see the issue at all. I believe the problem then is that NW will request tape from same pool on backup server for index and bootstrap (when backup will run on 1st). What I usually do is to disallow bootstrap and index backup after group completion. Instead of that I do manual backup of it (with savegrp -O) and I have pool dedicated for that. That keeps things tidy a bit.