cancel
Showing results for 
Search instead for 
Did you mean: 

Policy automatically started without related schedule time?

Dado
Level 3

Hi all,
few minutes ago a strange thing happened.

I created a new policy around 17:30 to backup a SQL server, I set the schedule to run it on Saturday, from 12pm based on the calendar, in the calendar I selected tomorrow (day 21). 

Today Friday the 20th at 18:00 the policy started!

I double checked every setting to undestand what could have started the policy but really I don't find anything nor I have an idea of what happened.

Does anybody have an idea of what happened here?

I don't want this policy to run randomly when I'm not expecting it

 

thanks

 

1 ACCEPTED SOLUTION

Accepted Solutions

watsons
Level 6

The policy seems to be a new one, see the effective date:

Effective date:      06/20/2014 17:51:14

Very close to the time you said it started by itself (20/06/2014 18.00.00), well.. if this is a Unix master server and somehow you access the GUI from another remote client, check if there is any timezone difference between the master server and the remote client.

View solution in original post

9 REPLIES 9

BTLOMS
Level 5

what is the time zone/region setting on your server? Does it match with where you are?

watsons
Level 6

Timezone is the first I would check, but if it isn't, check admin log or run nbauditreport to see if anyone has manually started it...

Dado
Level 3

the timezone is ok, I have other policies in place and all of them start as expected.

Nobody could have manually run it, I'm the only one here with access to the server and with admin rights.

Mark_Solutions
Level 6
Partner Accredited Certified

Can you show us the tabs of the job itself (screen shots) as they will say either scheduled or immediate

Could we also see bppllist policyname -U so that we can see the exact configuration

Thanks

Dado
Level 3

Here you are the screenshots of the policy

sql_1.png

sql_2.png

sql_3.png

 

sql_4.png

sql_5.png

here the output of the command:

Policy Name:       sql_1_full

  Policy Type:         MS-SQL-Server
  Active:              yes
  Effective date:      06/20/2014 17:51:14
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     4
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           MSL4048_FC
  Volume Pool:         SQL_1
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds
ASC Application and attributes: (none defined)

  Granular Restore Info:  no
  Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
  Use Accelerator:  no
  HW/OS/Client:  Windows-x64   Windows2008   SQLSRV01

  Include:  C:\Program Files\Veritas\NetBackup\DbExt\MsSql\sql_backup_all_full.bch

  Schedule:              Full
    Type:                Automatic Backup
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     3 (1 month)
    Calendar sched: Enabled
      SPECIFIC DATE 0 - 06/21/2014
      SPECIFIC DATE 1 - 07/05/2014
      SPECIFIC DATE 2 - 07/19/2014
      SPECIFIC DATE 3 - 08/02/2014
      SPECIFIC DATE 4 - 08/16/2014
      SPECIFIC DATE 5 - 08/30/2014
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          sabato     12:00:00  -->  domenica   12:00:00

  Schedule:              Default-Application-Backup
    Type:                Application Backup
    Maximum MPX:         1
    Synthetic:           0
    Checksum Change Detection: 0
    PFI Recovery:        0
    Retention Level:     3 (1 month)
    Number Copies:       1
    Fail on Error:       0
    Residence:           (specific storage unit not required)
    Volume Pool:         (same as policy volume pool)
    Server Group:        (same as specified for policy)
    Residence is Storage Lifecycle Policy:         0
    Schedule indexing:     0
    Daily Windows:
          domenica   00:00:00  -->  domenica   24:00:00
          luned∞     00:00:00  -->  luned∞     24:00:00
          marted∞    00:00:00  -->  marted∞    24:00:00
          mercoled∞  00:00:00  -->  mercoled∞  24:00:00
          gioved∞    00:00:00  -->  gioved∞    24:00:00
          venerd∞    00:00:00  -->  venerd∞    24:00:00
          sabato     00:00:00  -->  sabato     24:00:00

 

watsons
Level 6

You forgot to provide the job details (overview & details) screenshot as requested by Mark... 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

The Overview tab of the SQL job will tell us if job ran 'scheduled' or 'immediate'.

It's been 4 days since your original post - if you have not checked yet, chances are that job is already removed from Activity Monitor (default is 3 days).

Dado
Level 3

Sorry, you are right I forgot it, here you are the overview, as you can see is "scheduled" :

sql_6.png

 

In the detail there is nothing interesting, I just paste the first rows where something about schedule appears:

20/06/2014 18.00.00 - Info nbjm(pid=360) starting backup job (jobid=3940) for client xxxxxxx, policy SQL_1_FULL, schedule Full  
20/06/2014 18.00.00 - Info nbjm(pid=360) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=3940, request id:{DC698C72-FEBD-4196-B764-92DD30FBB93B})  
20/06/2014 18.00.00 - requesting resource MSL4048_FC
 

thanks

watsons
Level 6

The policy seems to be a new one, see the effective date:

Effective date:      06/20/2014 17:51:14

Very close to the time you said it started by itself (20/06/2014 18.00.00), well.. if this is a Unix master server and somehow you access the GUI from another remote client, check if there is any timezone difference between the master server and the remote client.