Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Exclude dates for individual jobs

Created: 09 Mar 2012 • Updated: 10 Mar 2012 | 50 comments
pkh's picture
53 Agree
0 Disagree
+53 53 Votes
Login to vote

In BE 2012, exclude dates are on a server level, i.e. they apply to all scheduled jobs.  The inability to exclude dates for individual jobs is a serious set-back and would mean that we now CANNOT stop scheduled jobs from running during holidays.

Suppose I have JobA and JobB scheduled to start at 10 p.m. and 2 a.m. respectively.  These are daily backup jobs and I do not want them to run on holidays because there is nobody in the office and no updates are done.  If a holiday falls on 15 Mar., then I have to exclude 15 Mar from JobA's scheduled run and 16 Mar from JobB's scheduled run.  Note the difference in the excluded dates.  JobB's 15 Mar run is to backup data from 14 Mar, hence it should not be stopped.

In previous versions of BE, with exclusion dates for individual jobs, the exclusion dates for the above example can be achieved, but BE 2012, it is not possible to have a good exclusion.  Suppose I exclude 15 Mar.  This means that JobB will only run on 16 Mar to backup data from 14 Mar.  This leaves me exposed.  Suppose my server crashed on mid-day on 15 Mar.  I would have no backup of the 14 Mar data.  This means I am more vulnerable with BE 2012 than with previous versions of BE.  The alternative is to still do backups on holidays which brings its attendant problems of increased storage requirement and operational problems like how to change tapes.

With BE 2012 being server-centric, the number of jobs will increase and some of them will definitely spill over midnight and the above problem would be magnified.

Do bring back exclude dates for individual jobs.

Comments 50 CommentsJump to latest comment

AdminMan's picture

I agree, this is a ridiculous feature to have removed. We have multiple jobs that run on the same server over night. The first starts at around 8:30pm and the last starts at 6:00am. So if I exclude a date, that means that I exclude half of the backups that I actually want to run, leaving me vulnerable should a system failure occurr while it waits 24 hours to run the jobs that run of a morning.

I also back emails up to disk, then duplicate to tape. I'd still like the backup to disk to run and be able to skip the duplicate to tape, as there isn't room on the tape for two lots of email backups each night.

I wish I could vote 10 times for this feature to come back!

-4
Login to vote
StrongmanTech's picture

This is BS. I cannot exclude a specifc date on a particular job!

In my case, I have several jobs... the weekly and incementals, an end of month, and an end of year. The end of month and year write to tape, and the weekly/incremental to disk. For compliance reasons, each job has different media sets for the retention period, i.e. weekly keep for 1 week, monthly keep for 1 year, and yearlys for 10 years. 

So, I cannot exclude the weekly job run on the last day of the month, nor the weekly or end of month at the end of year.

On that last friday, BE now wants to run the: Weekly, End of Month, and End of Year all on the same day!!! BS, I say. 

+1
Login to vote
Johanne1's picture

I just installed BE2012 two days ago and just realized this MAJOR PROBLEM!!!!  I have the same scenario as AdminMan and I can't believe Symantec did this!  Unbelievable!  I'm going to verbally complain to tech support, hoping they can fix this in a service pack!

-4
Login to vote
RvdB-NL's picture

I have upgrade fron 12.0 to 2012 and missing the exclusion from dates on Job level. The only option that I can find is to eclude days for all the jobs.

 

Also have I jobs that must run on days during the year.  That was also possible in 12.0.

 

I WANT THESE OPTIONS BACK!!!   From 12.0 to 2012 is no upgrade but a DOWNGRADE!

 

Best regards,

 

Rex

 

PS.  I thnik I have looked at all options but when so one nows a solution please let me know!!!!

+1
Login to vote
cavman1-4's picture

Where does Symantec come up with their ideas?  It sure doesn't seem like they come from their customers.

This is just one of many bad development decisions they have made with this new version, and I haven’t even begun to dig very deep yet.  I’m just not seeing the value of going this direction; we need flexibility in our products. 

I would love an explanation from the Executive in charge of Backup Exec development.  It seems like a waste of development time to code changes like this when they have never addressed the DST time change issue that plagues us all twice a year.

“If it’s not broken, don’t fix it”

-5
Login to vote
Johanne1's picture

Out of the blue, I received a call from an Escalation engineer, in response to a support ticket during the initial installation of the upgrade.  He wanted to know if everything and been resolved and wanted my opinion and comments, positive or negative, about the new software.  I asked him if he had read the forum lately!!

We had a lengthy discussion about many issues and I conveyed my disappointment with how they had changed certain aspects in the operation of the software, particularly, this issue.  He conveyed that they are VERY busy with fixing all the issues that have arisen.

Hopefully, there will be a patch soon!  cheeky

-6
Login to vote
Jason Lee's picture

The stupidity of leaving this function out is beyond comprehension.  Everytime I turn my head 2012 is forcing me work what I want around the software instead of the software allowing me to customize for my needs.

Seriously this is feeling like dealing with v1.0 of a product that failed to go through any customer regression testing.  I don't know one admin in our environment that does not require exception on certain jobs at certain dates/times.  The more of these threads I come across the more frustrated and serious I am at looking to other software.

I stumbled upon a cached version of KB 179148 (I couldn't get to it directly)  where it states the reason of this was basically because it became possible for a job to become too complex so sometimes a specific job would not run or fail..

"A combination of these different options could be used offering the possibility to define complex schedule. To bring this flexibility, some aspects of schedule periods were based on a schedule window, a period of 24 hours not necessarily starting at 0:00 or finishing at 23:59. This brought undesired side effects where exclusion dates would slide from the day they were defined to the following day or, as another example, for jobs not to run on expected days with a "missed" completion status."

... so basically, rather than fixing the bug, they removed exclusions and even specific day selection (i.e. now you can only do daily, not Mon - Fri, skip Sat/Sun) within a job, but force you to set on the media

"- Provision of exclude dates are defined at media server level as opposed to job level. The exclusion period now coincide with the 24 hour duration of the exclusion date."

which basically forces you to have a seperate server for each job if you wish to try to get the old functionality back (set exclude date under Default Job Settings | Exclude dates, which effect all jobs on that server).

This causes way more trouble than the potential of prevention of possibly undesired effects.  We've been using exclusion dates for over 8years on v10, 11 and 12 w/o a problem and to much success in reigning in jobs that overlap that would cause high server load, prolonged jobs, inconvience with the need to physically intervene, etc.

A basic full/inc with a full at one time, because it will take longer and the incr at a different time will cause them both to run on the same day.  Want a monthly diff and a incr daily... now you have to have 2 seperate jobs for the same data where it's possible for the Diff's Full, the Diff itself, the Incr Full and the Incr iteslf will all occur on the same day.  So instead of having a simple Full -> Diff -> Incr and exclude the laters from occuring on the days the priors occur on, you have to work out some complex overlap scenario, using a ton more space and longer backup windows or sacrifice levels of point-in-time recovery.

-4
Login to vote
Jason Lee's picture

Per another thread, I was directed to https://www-secure.symantec.com/connect/forums/backup-exec-2012-single-backup-multiple-servers for Elizbeth's post regarding scheduled changes.  She is offering to  to do a Webex session so you can see possible changes to scheduling options on a beta version of a yet-to-be realeased update to 2012. She asks for you to directly message her to set this up... https://www-secure.symantec.com/connect/user/elizabeth-teffner

-1
Login to vote
Jason Lee's picture

Correction.  You can specify a job to be weekdays, so you can have the FULL designated to run on a Weekend and the Inc/Diff to run on a Weekday to ensure they do not overlap.  As long as your "weekday" corresponds to M-F you are good... and don't mind the Diff/Incr missing one of the days of the weekend.

-4
Login to vote
Keith1867's picture

I Agree the fact that each server has it own job should mean that you should be able to exclude one server from a nights backup. But it does not work like that when you click on a date it excludes the lot. It is not flexible as you may want to not run a backup as the server is being upgraded. The only way to do it is knock the day off the list where as in the older versions you could exclude a date very easily. This version is awful and I can't say I like it at all as it not suitable for a Central Backup Server which backs up many servers. I currently have 17 servers on it and it seems to do weird things like not doing the jobs in the right order. 

I think I prefer to have one job with many servers as it is not so confusing as there is too much. We have Central backup servers and pre 2012 it was easy to schedule and to check for the failures if and when they occurred.  Maybe we should be offered a downgrade to 2010 which would be a upgrade in usability.

 

 

-3
Login to vote
FastEddie's picture

This thread was started in March and others I read were started early in the year as well and here we are 6 months later they still havent come up with a way exclude a single job from a day?  I've been with BE since the "250Mb Jumbo" tape drives were the latest and greatest but I've had it with Symantec and what they have done to previously good products. As soon as my next upgrade opportunity comes around I'm finding something else to backup my data as well as a new network anti-virus product. (you don't even want me to go in to what I went through when I upgraded my AV!)

There has been too many bone-headed changes to keep putting up with this BS.

 

Eddie

-5
Login to vote
TenIT's picture

That is ridiculous

WE WANT THESE OPTIONS BACK!!!

 

 

-5
Login to vote
kmoore's picture

This feature being excluded is not ok.  Without these features we are seriously considering droping Symantec and finding another solution.  This "upgrade" is a train wreck!  Between the drastic GUI changes, and the removal of features that we rely on, this is the worst release of BU Exec I have ever seen!  I wish I had never "upgraded" when I was contacted by the Symatec representatives.  Fix this or risk losing long time customers!

-3
Login to vote
AdminMan's picture

So it is now December and this problem, that was first raised here in March, is still an issue. That is just fantastic - thank you so much Symantec. I will now need to work on Christmas Day as well as New Year's Day just to ensure that backups work correctly and so I don't rock in after the holidays to 100s of Backup Exec errors in my Inbox. Thank goodness I've only moved one server to Backup Exec 2012. The others are running 2010R3. There is even one still on version 12 - and it does what we want!

2013, the year I find a new backup solution.

-5
Login to vote
Muhammad Susiwala's picture

I WANT THESE OPTIONS BACK!!!  

WHEN I AM RIGHT NO ONE REMEMBERS

WHEN I AM WRONG NO ONE FORGETS

+1
Login to vote
AdminMan's picture

So I thought I'd be clever, after all, who wants to work Christmas Day and New Year's Day right, even if it is just checking backups? So as you have to do in Backup Exec 2012, I excluded three whole days, 25th and 26th December and 1st January from the backup calendar. The main backups were set to run Christmas Eve and New Year's Eve, the others weren't desperate and could run a day or two late. A small price to pay to enjoy my days off, uninterrupted.

I didn't notice it on the Christmas Eve backup (although I have confirmed it happened there as well), but today I came in to find that New Year Eve's Exchange backup failed - no, sorry, it was cancelled. What? Who did that? Well, I have worked out no one did, Backup Exec did! How you may ask. Well, I have worked out that when you have a backup that starts the night before an "Excluded Date," if that backup doesn't finish until after midnight, Backup Exec 2012 automatically cancels the backup because it is now trying to run on an "Excluded Date." So with 15 minutes left to run on that backup it was cancelled.

So the scenario worked out to be that the Exchange backup to disk that was running, and had been running for an hour and 45 minutes, was cancelled by Backup Exec at midnight, because it was now an "Excluded Date." Yet the duplicate that doesn't start until after the Exchange backup completes, ran fine.

Symantec can't even get their logic consistant!

This has confirmed my New Year's Resolution - new backup software.

+1
Login to vote
Seon Keon's picture

I am in same situation. Hope someone will listen and do something about this.

+1
Login to vote
Support Team RE's picture

I have the same trouble here with this new bad surprise. !! :(

The 1/1/2013 was exclude because of holidays.

Our daily backup job start every week day at 7pm.

So the job start normally on monday 31/12/2012 7pm,

but the active job was atomatically cancelled at 00:00 on 1/1/2013 !!!

BE2012 is really a Great Great downgrade !!!

I didn't understand why Symantec need to change a good backup software like be2010 to a new very bad one !

 

+1
Login to vote
Jayb's picture

If the exclude date is affecting the jobs in Backup Exec 2012,
please Open a Support ticket as the team is working on it.

Thanks
Jay

-2
Login to vote
FastEddie's picture

@ JayB - Don't you think there have been a bunch of tickets already opened due to this problem?

I personally have opened a ticket, but it was immediately closed when the answer was given: "You cannot exclude a single job from a single day, you can only exclude every job from the entire day"

So is there something else we can do besides complaining about the product in a forum where no one is listening? (at least no one who has enough influence to make the changes needed)

+1
Login to vote
mwalker's picture

Same problem here!!!
Have excluded some dates during the holidays at several customer sites.
ALL JOBS FAILS (canceled at midnight).

@ JayB - you guys cannot realize that this is not a problem with specific environments...THIS IS A "FEATURE"

ONCE AGAIN...please remove all mistakes from 2012, as this getting more and more serious.................

-3
Login to vote
harvba's picture

I agree completely.  Bring back the individual job exclusion date option.  PLEASE!!!!!!!

-4
Login to vote
anfaenger's picture

I nedd individual exclusion days for each job. I need furthermore a priority of jobs, namely that the weekly job at last workday of the week is done prior to the dayly job, when the lastr workday of the week ist for example on thursday. The same hat to be when the last workday of the month covers a dayly job or a weekly job.

-6
Login to vote
sgaGC's picture

I agree completely. I also need the individual job exclusion date option.

+1
Login to vote
scoutt's picture

I agree, we need this option. Specifically if a business wants to make quarterly backups that are different from full weekend backup. I have also read it maybe in 2012 R2 that sin Beta,

https://www-secure.symantec.com/connect/forums/how...

Hopefully it comes out soon.

-5
Login to vote
FastEddie's picture

The post/question is titled "How exclude a job for a certain day" I noticed that they maked it is as "Solved".  Really? Where's the solution?!!

The Symantec Employee says "..please see Idea posted by PkH.." and leaves a link back to this thread. What idea?!!  PkH is the person who started this thread with the original problem!

And finally the Symantec Employee says "..you can enroll to beta version of BE2012 r2 to check same."  Check same what?  Does that even make sense? 

I would have posted this statement there but they locked it.

 

Even though I'm ditching all Symantec products, I won't be able to afford the change for a year or 2 so I'm still looking for a solution to hold me over. This thread is over a year old with still no solution to the absence of a basic feature.

-5
Login to vote
PackMatt73's picture

Greetings all.

This issue will be resolved in Backup Exec 2012 SP2 & Backup Exec 2010 SP3

The beta will begin in May with the product release in July

Please don't hesitate to ht me up with any questions, issues or suggestions

+1
Login to vote
RvdB-NL's picture

Hi,

Can you explain where I can find to exclude dates for individual jobs. I have installed SP 2 for 2012 but can't find this option?

 

Best regards,

Rex

 

-4
Login to vote
hmontero's picture

Very good news!!! 

Please don´t close this discussion until the problem is resolved !!!

We have to make pressure!!! jajaja

-5
Login to vote
RvdB-NL's picture

Hi All,

 

Is it solved in SP2?   I have just installed sp2 and when I exclude a date in a job it also eclude this date in the other jobs.

 

Best regards,

Rex

-4
Login to vote
MiJan's picture

Unfortunately not. I think that was forgotten in SP2.

 

Best regards,
Michel

-5
Login to vote
StrongmanTech's picture

Thats a shame. Not that I have many customers on BE anymore anyway!

Just one, and am working on getting them off, though they are a large Fortune 100 corporation. They are talking to me about running a trial of Microsoft DPM.

Once you have a working trial, so much easier for them to drop a little cash for a good, stable, working platform for backups and DR. wink

-3
Login to vote
MiJan's picture

Its really a shame!!!

@Symantec and PackMatt73: Where is your statement? We need the individual job exclusion date option.

 

Best regards,
Michel

-5
Login to vote
PackMatt73's picture

Regrtably, it appears that I was mis-informed this spring when I replied that it would be included in the SPs.  This is a functionality that is set to be included in the next major release.

If anyone has an support case number relevant to this, can you please DM that to me?  That way, I can cross reference your incident with the work going on in engineering to learn more.

I sincerely apologize for posting bad information.  At the time I made my post, it was my understanding that this would be included in the SPs.

Matt

0
Login to vote
RvdB-NL's picture

So when I understand you well this not will be included in a new SP’s and we must buy a new version? Because of this information I was waiting for SP2. I have not renew my maintenance contract and my plan is also to keep it this way and look for other software.

 

Best regards

Rex

-1
Login to vote
TE_Karatay's picture

If it is impossible to add this feature to Backup Exec, maybe this one could be. There could a validation when scheduling a job. This validation could be useful for conditions like this.

For example; suppose there are two seperate jobs in the same server but one of them is daily, the other is monthly. monthly schedule uses last day of month option and daily one is uses every weekday. Ok it is good to decide when job will work, but i can decide when daily job will not work. There is an option more to specify when daily job doesn't work. In this example it will be choosen as last day of the month.

By using this method daily job will work every weekday but it will not work when the last day of the month is one of the weekdays. 

-5
Login to vote
bpeer's picture

So, when is the next major release scheduled?  I'd really like to get this option back.

-1
Login to vote
alex estevez's picture

Went to job properties, under schedule change the "starting on" date to the day after your intended exclusion day. The job re-schedules itself, skipping your intended exclusion day.

-5
Login to vote
Swampy's picture

Any update on adding Exclusion dates to single backup jobs?

-4
Login to vote
Elias AbuGhazaleh's picture

Hi Swampy,

This functionality has been added to the upcoming release, you can sign up here: http://buff.ly/16HENkV

 

-1
Login to vote
RvdB-NL's picture

Hi Elias,

 

I have get SP 3 and there I can't find to exclude dates in individual jobs.

 

What do you mean with the upcoming release?

 

Best regards,

Rex

 

 

0
Login to vote
Juventud's picture

Hi .

 

I've bkup 2012 sp3 and I feel scammed for this release. PLEASE SOLVE THIS, i want exclude dates in individual jobs, backup exec 2010 release worked well !!!

 

 

 

0
Login to vote
CraigV's picture

...the Beta for BE 2014 seems to be open so check it out.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

0
Login to vote
FastEddie's picture

While this message board has turned into a frustration-fest, I have brought you good people some actual positive news.

Nearly every Symantec competitor is scrambling to snag all the B.E. users who are jumping ship and are offering huge discounts to steer clients in their direction.  Over the last few weeks I have gotten quotes or had conference calls with most of these companies and reseached the rest:

ARCserve (CA Associates)
Yosemite (Barracuda)
AppAssure (Dell)
Unitrends  (says it's the #1 replacement for B.E.)
StorOnce (HP)
Acronis Backup & Rocovery
ShadowProtect

While Unitrends and AppAssure are my favorites (incredible features!) I can't afford them.  I'm going with Yosemite for now because I can backup 3 servers, Exchange, SQL, virtual server support, bare metal recovery and still use tape if needed ALL FOR UNDER $700. (20% discount to B.E. users)
I used the 60 day Yosemite trial and tested it. Had to clean up some VSS writer errors my OS had that I never noticed, but once I tuned up my server it ran without issue. And I didn't even have to uninstall B.E. to use it.

Of course there are other options than what I list here, some are even free:
http://en.wikipedia.org/wiki/List_of_backup_software

 

I posted here way back in 2012 that I was getting away from B.E., and I'm just now doing it so clearly Symantec had their chance. I'm out!

Good luck all,

 

Eddie

0
Login to vote
Richard Post's picture

The ability to exclude specific job from running on a specific date while not excluding the whole date is one of those features available in BE 2010 that I assumed would continue when upgrading to BE 2012.  That assumption is not valid. After spending entirely too much time trying to figure out why I can't do this and spending even more time with support who, at first, could not figure out what I wanted to do, I find BE 2012 does not nor ever did support this feature.

We have a weekly backup that we want to run every Friday except the last Friday in a month. We have a second backup we want to run only on the last Friday.  There is no way to prevent - short of doing it manually - the weekly backup from running on that Friday and, thus, you have two jobs that want to run at the same time.

I have used Backup Exec since before it was acquired by Symantec. I know how to use it and have written schedules that worked under previous versions.  And, now they don't. I hate to leave a product that I'm familiar with but, like the gentleman suggests in a previous post, there are other products that might better meet our needs.

0
Login to vote
jwiesemes's picture

To get around the schedule issues, why not set a monthly job (if that is what you want) to run on the first Friday / Saturday / Sunday or whatever day of the month. Then setup your weekly to run on the 2nd / 3rd /4th and last of the month. This works around the issue and gets around the 5 weekend months.

 

The only downside would be this would create alot of duplicate disk to tape jobs. Just a suggestion.

 

Jason

0
Login to vote
RvdB-NL's picture

It's great that everyone is finding work around how to handle the missing option “Exclude dates for individual jobs”. But in the past versions this functionality was included and it saved me a lot of time and since Symantec has removed this option we are not 100 % sure that everything is running error free.
But what I miss is the support from Symantec about this. They have promised servile times that this option would be back with a service pack release.
So Symantec, I have canceled the maintenance contract because I have the feeling that I pay for support I don’t get. We are using BackupExec for years but because Symantec is doing nothing about his situation we are looking for other backup software that can handle Exclude dates for individual jobs.
It would be nice when Symantec is clear about the plans they have about “Exclude dates for individual jobs” in the future. Maybe you can keep us and maybe more users of BackupExec as customer?

0
Login to vote
pkh's picture

Exclude days for individual jobs will be part of BE 2014 which is due to be released in the middle of the year

0
Login to vote
Richard Post's picture

I am pleased to learn that the "exclude date" issue will be resolved with the 2014 release having lost the functionality when we purchased 2012 last year. However, does this mean that I need to go to management - hat in hand - begging for more money for the sole purpose of getting what Symantec took away?  From what I can see, this has been an issue from the time of its release with promised SPs to fix never materializing.  I guess as long as my company is going to have to pay for someting, might as well replace BE altogether.

Thank you, jwiesemes, for the work-around. The only problem I see, other than lots of duplicate jobs, is it will mean a change in policy. Our policy states that a full backup with all files (SDR) will run the last Friday of each month. We have had this policy for close to 10 years, giving us predictable points in time for file recovery. Granted, its a relative point in time and if this work-around solves or, at least, resolves the exclude date issue for monthlies, it may be worth doing.

0
Login to vote
pkh's picture

If you are on a current maintenance contract, then the upgrade to BE 2014 is free.

It is stated in one of the official blogs that Symantec is looking into the upgrade situation for those who do not have a current maintenance contract.

0
Login to vote