on 04-02-2012 11:56 PM
Why do you recommend $ConfirmPreference="None"? Is it better?
Quotes doesn't works for me:
Start-BEJob -In '"Job1"'
Post the full command and how do you use it, whether in a Powershell console, as a script or as a pre-/post -command, as a discussion in the forum section and I will take it from there.
An alternative to creating the script described in the article above is to do the following:-
1) Suppose you have a file called c:\jobs.txt with the following contents
Job1
Once you chain a job using the cmd line tools does it show this fact anywhere in the BE GUI?
cheers
John
No.
Oh dear... This is terrible. What was Symantec thinking? Definately going to downgrade to 2010 R3.
Good lick with that. as if you go up to 2012, it changes the schema on the database, and down grading is difficult, I didnt investigate the downgrade a lot, but tried to reinstall on a differnet Database, and the result was the same I kept getitng a "Schem has been modifed Error" ;0(
A week on I am liking the new product, though it is confusing and makes normal tasks much harder than in the past. Seems quicker though, and has lots more information on the front view.
This version seems to be like a "Small Business" version for only 1 server
If you need to backup 20 servers you will get 20 jobs this is not acceptable
or is the same are individual jobs, between each job they lose about 15 min. everytime a new job starts?
Hi!
In my case the backup jobs habe the names:
Name
----
SCOM - Daily-Full
CTMDomino - Daily-Full
DOG02 - Daily-Full
SAP_PRD - Daily-Full
SAP_DEV - Monthly-Backup
WorkFlow - Daily-Full
SAP_CONT - Daily-Full
Exhange - Daily-Full
as they extracted from the command
[ Get-BEJob | Where-Object {($_.JobType -eq "Backup") -and ($_.Status -eq "Scheduled")} | Select-Object name > c:\jobs.txt ]
I tried to schedule some jobs following your instructions but didn't work.
When I tried the command Start-BEJob -In '"WorkFlow - Daily-Full"' -Confirm:$False
direct in a Powershel, I got this result:
Start-BEJob : Cannot bind parameter 'InputObject'. Cannot convert value ""WorkFlow - Daily-Full"" to type "BackupExec.Management.CLI.BEJob". Error: "Cannot find any Job objects with the name "WorkFlow - Daily-Full"."
At line:1 char:16
+ Start-BEJob -In <<<< '"WorkFlow - Daily-Full"' $ConfirmPreference="None"
+ CategoryInfo : InvalidArgument: (:) [Start-BEJob], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,BackupExec.Management.CLI.Commands.StartBEJobCommand
Could you be so kind to give a hand please?
Thnak you
Vassilis
Try Start-BeJob -Name "NameofJob"
I'm having a problem with the methods described here. If you have a job on hold and you start the job, when the job is completed it is no longer on hold. If I'm chaining 20-30 jobs together there's a chance that a prior job in the chain could be run by the BE scheduler.
I'm getting around this by changing the schedules to two years in the future and placing all jobs on hold at the end of the script. Is there a more elegant solution?
pkh,
I really like your solution on chaining.
I have a similar need but would also like to introduce a 10 minute delay in between 2 jobs.
For example job1 runs, then would like 10 minute delay for cleanup actions to complete, then run job2 in that order.
Any suggestions? Your command sequentially starts next chained job within seconds of the first completing.
LOL - you can go through this nightmare of a Job Chaining procedure using command line, OR use the simple GUI in the previous version of Backup Exec 2010. My choice is stick with the previous version and save myself hours of frustration. Maybe they can make BE2014 like BE2010???
I'm testing BE2014 and it makes its job like 2010 (single job for multiple server to tape).
Sounds good. As we migrated successfully to 2014, I had just left the Jobs alone, as I got so used to the new interface. I do like the way you can navigate around 2014 better, and that you can clear down notifications easier. Must say though for my regular server backups I bought a Dell Appassure device, so I can stop worrying about BE all together ;0)
Can you tell me how to list the server name the job is attached to as well? sometimes the job name doesn't indicate this. I can see a field called "Server" when building a custom report through the gui report builder but I don't see this field in the BEMCLI under get-jobhistory.
Thanks :)