cancel
Showing results for 
Search instead for 
Did you mean: 

Backups running more than once in single day 6.0 MP4

Venkatesh_K
Level 5
Hi All,

Veritas Master : Solaris, NB 6.0 MP4
Clients : Windows 2003 NB 6.0 MP4

Issue:

I have Windows policy which backups around 60 clients, it is file system backup. 58 clients backup runs fine (runs only once) but i have problem with only 2 clients which are run more than once in single day (3-4-5 times a day). my schedules are calender based schedules. backup window is 18:00hrs to 5:00hrs

why is this happening only to 2 clients and not to toher clients in the same policy.

can somebody through any ideas what can be wrong ? or what should i be looking for ?


Thnks,
Venkat
8 REPLIES 8

zippy
Level 6
 make sure its schedual does not cross 12 am

Venkatesh_K
Level 5
Hi Zippy,

same schedule applies to all 60 clients in the policy, why is that only for these 2 clients im having this issue ?

Yasuhisa_Ishika
Level 6
Partner Accredited Certified
Is your policy configured as multi-streamed backup or not? Do all the streams run simulutaneously, or only some of them runs? And I agree with zippy, calendar-based schedule shouldn't across midnight.

zippy
Level 6
when do the two offending one complete?

what time do the kick off and what time to the end in a 24 hour period?

Venkatesh_K
Level 5
Hi Zippy,

below is the start and end time of the client im showing here only for one client. Yes multistreaming is enabled below is single backup window and backup has run 10times.

Start time End time   Start time End time   Start time End time   Start time End time  
7/20/2009 21:20 7/20/2009 21:22   7/20/2009 21:41 7/20/2009 21:43   7/20/2009 22:03 7/20/2009 22:03   7/20/2009 22:25 7/20/2009 22:41  
7/20/2009 21:20 7/20/2009 21:21   7/20/2009 21:41 7/20/2009 21:44   7/20/2009 22:03 7/20/2009 22:15   7/20/2009 22:25 7/20/2009 22:25  
7/20/2009 21:20 7/20/2009 21:22   7/20/2009 21:41 7/20/2009 21:43   7/20/2009 22:03 7/20/2009 22:05   7/20/2009 22:25 7/20/2009 22:26  
7/20/2009 21:20 7/20/2009 21:22   7/20/2009 21:41 7/20/2009 21:43   7/20/2009 22:03 7/20/2009 22:08   7/20/2009 22:25 7/20/2009 22:25  
7/20/2009 21:20 7/20/2009 21:31   7/20/2009 21:41 7/20/2009 21:44   7/20/2009 22:03 7/20/2009 22:03   7/20/2009 22:25 7/20/2009 22:26  
7/20/2009 21:20 7/20/2009 21:22   7/20/2009 21:41 7/20/2009 21:44   7/20/2009 22:03 7/20/2009 22:03   7/20/2009 22:25 7/20/2009 22:33  
7/20/2009 21:20 7/20/2009 21:26   7/20/2009 21:41 7/20/2009 21:48   7/20/2009 22:03 7/20/2009 22:03   7/20/2009 22:25 7/20/2009 22:25  
7/20/2009 21:20 7/20/2009 21:22   7/20/2009 21:41 7/20/2009 21:53   7/20/2009 22:03 7/20/2009 22:03   7/20/2009 22:25 7/20/2009 22:25  
7/20/2009 21:07 7/20/2009 21:31 Parent job 7/20/2009 21:41 7/20/2009 21:53 Parent job 7/20/2009 22:03 7/20/2009 22:15 Parent job 7/20/2009 22:25 7/20/2009 22:41 Parent job
                       
                       
                       
                       
Start time End time   Start time End time   Start time End time   Start time End time  
7/20/2009 22:51 7/20/2009 22:54   7/20/2009 23:13 7/20/2009 23:13   7/20/2009 23:32 7/20/2009 23:33   7/20/2009 23:54 7/20/2009 23:56  
7/20/2009 22:51 7/20/2009 22:53   7/20/2009 23:13 7/20/2009 23:22   7/20/2009 23:32 7/20/2009 23:38   7/20/2009 23:54 7/21/2009 0:06  
7/20/2009 22:51 7/20/2009 22:54   7/20/2009 23:13 7/20/2009 23:13   7/20/2009 23:32 7/20/2009 23:33   7/20/2009 23:54 7/20/2009 23:56  
7/20/2009 22:51 7/20/2009 22:54   7/20/2009 23:13 7/20/2009 23:13   7/20/2009 23:32 7/20/2009 23:33   7/20/2009 23:54 7/20/2009 23:56  
7/20/2009 22:51 7/20/2009 22:53   7/20/2009 23:13 7/20/2009 23:15   7/20/2009 23:32 7/20/2009 23:43   7/20/2009 23:54 7/20/2009 23:57  
7/20/2009 22:51 7/20/2009 22:54   7/20/2009 23:13 7/20/2009 23:13   7/20/2009 23:32 7/20/2009 23:33   7/20/2009 23:54 7/20/2009 23:57  
7/20/2009 22:51 7/20/2009 22:57   7/20/2009 23:13 7/20/2009 23:13   7/20/2009 23:32 7/20/2009 23:33   7/20/2009 23:54 7/21/2009 0:01  
7/20/2009 22:51 7/20/2009 23:03   7/20/2009 23:13 7/20/2009 23:17   7/20/2009 23:32 7/20/2009 23:33   7/20/2009 23:54 7/20/2009 23:56  
7/20/2009 22:51 7/20/2009 23:03 Parent job 7/20/2009 23:13 7/20/2009 23:22 Parent job 7/20/2009 23:32 7/20/2009 23:44 Parent job 7/20/2009 23:53 7/21/2009 0:06 Parent job
                       
                       
Start time End time   Start time End time   Start time End time        
7/21/2009 0:16 7/21/2009 0:19   7/21/2009 0:39 7/21/2009 0:41   7/21/2009 0:59 7/21/2009 1:00        
7/21/2009 0:16 7/21/2009 0:20   7/21/2009 0:39 7/21/2009 0:49   7/21/2009 0:59 7/21/2009 1:00        
7/21/2009 0:16 7/21/2009 0:29   7/21/2009 0:39 7/21/2009 0:39   7/21/2009 0:59 7/21/2009 1:00        
7/21/2009 0:16 7/21/2009 0:20   7/21/2009 0:39 7/21/2009 0:39   7/21/2009 0:59 7/21/2009 1:00        
7/21/2009 0:16 7/21/2009 0:23   7/21/2009 0:39 7/21/2009 0:39   7/21/2009 0:59 7/21/2009 1:05        
7/21/2009 0:16 7/21/2009 0:20   7/21/2009 0:39 7/21/2009 0:43   7/21/2009 0:59 7/21/2009 1:00        
7/21/2009 0:16 7/21/2009 0:20   7/21/2009 0:39 7/21/2009 0:40   7/21/2009 0:59 7/21/2009 1:00        
7/21/2009 0:16 7/21/2009 0:19   7/21/2009 0:39 7/21/2009 0:39   7/21/2009 0:59 7/21/2009 1:09        
7/21/2009 0:16 7/21/2009 0:29 Parent job 7/21/2009 0:39 7/21/2009 0:49 Parent job 7/21/2009 0:59 7/21/2009 1:09 Parent job      
                       


I agree with you people that Calender based should not cross 12:00AM but nont of my other 58 cliets are affected with policy attributes, is there some thing that inned to check from client side.


thnks,
Venkat

Venkatesh_K
Level 5
Hi All,

i added these two affected clients to new test policy and  backup is perfact  i.e it is running only ones in a backup window.


can somebody throgh some light here please.......

Andy_Welburn
Level 6
& may show different effects e.g. not running at all etc.

In some instances the only way around this is to create a brand new policy - by that I do mean brand new & not copied from the original as that can tend to copy the 'corruption' with it.

It appears that that may be what you've got & creating a new policy has 'solved' the problem.

You might just have to live with what you've got (i.e. two policies) or 'migrate' the other clients from the old one ........ unfortunately it does happen sometimes :(

Venkatesh_K
Level 5
Thanks Andy,

yes your right, but what seems mysterious is why netbackup is behaving this way  only for  2 clients out of 60 (58 clients run fine in the same policy) .

im suspecting problem with scheduler, can someone through some ideas on netbackup scheduler, does it happen from master or client and some more ideas on schedular can help me getting closer to my solution.



thnks,
Venkat