How do I automatically backup SQL Agent jobs and SSIS packages on the mirror daily?

Question

I have seen this question asked before but I could not find a satisfactory answer. What is the best solution to get your SQL Agent jobs/schedules/etc. and your SSIS packages on the mirror server? Here's the details:
Server A is the principal with 2 DBs mirrored over to server B. Everything is fine and dandy, DBs are synched and all good. In Disaster Recovery testing, we need to bring up server B, which now will serve as the principal. Server A is inaccessible. Now,
we need all our jobs that are setup in server A to be in server B, ready to go, but disabled. We also need all our SSIS packages properly stored. Yes, we store our packages in the MSDB in server A.
Now, I can see a few answers coming my way.
1- Backup the MSDB to server B. When you bring server B up as principal in DR, restore the MSDB. All your jobs,schedules,steps, SSIS packages will be there. Is this possible? Can this be done on server B without rendering it incapable of serving as the principal
for the mirrored DBs? My fear with this option is that there may be information in the MSDB itself about the mirroring state of the DBs? Or is all that in the Master DB? Have you tried this?
2- Right click each job, script them out, re-create them on server B... No, thank you very much. :) I am looking for an AUTOMATED, DAILY backup of the jobs and SSIS packages. Not a manual process. Yes, we do change jobs and packages quite often and doing
the job twice on two servers is not an option.
3- Use PowerShell.. Really? Are we going back to scripting at the command prompt like that, that fast?
Since I fear option number 3 will be the only way to go, any hints on scripts you guys have used that you like that does what I need to do?
Any other options?
Any help GREATLY appreciated. :-) I can be sarcastic but I am a good guy..
Raphael
rferreira

Answer 1

I would go with option number 3. Once  you have a script simple run it....
param([string]$serverName,[string]$outputPath) 
function script-SQLJobs([string]$server,[string]$outputfile) 
    [reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | Out-Null 
    $srv = New-Object Microsoft.SqlServer.Management.Smo.Server("$server") 
    $db = New-Object Microsoft.SqlServer.Management.Smo.Database 
    $scrp = New-Object Microsoft.SqlServer.Management.Smo.Scripter($srv) 
    $scrp.Options.ScriptDrops = $FALSE 
    $scrp.Options.WithDependencies = $TRUE 
    $jobs = $srv.JobServer.get_Jobs() 
    $jobs=$jobs | Where-Object {$_.Name -notlike "sys*"}     
    foreach($job in $jobs) 
        $script=$job.Script() 
        $script >> $outputfile 
        "GO" >> $outputfile 
---script-SQLJobs "SQLSRV12" "C:\Jobs\test.txt" 
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Blog:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance