Backing up Orion

Hi guys,

Just a quite now just to let you know that I've been off testing disaster recovery on sql and iis for orion, my tests have showed that Backup Exec, a product provided by Symantec (no longer Vertias) has shown the most promise in this, I've intentionally killed over 30 servers and restored all of the data.

Has anyone got any other solutions that are worth investigating ?

Find more posts tagged with

sql_express_2005

backup

orion

orion_backups

sql_2005

backup_exec

Accepted answers

All comments

cchinfosys

Are you using the DB Manager to run a scheduled backup from Orion, then writing that backup to disk/tape using BackupExec? If so, does that get all of your Alerts (basic and advanced), along with Custom Pollers, Web site configuration, etc? Or do those configuration pieces have to be grabbed seperately?

Thanks!

tglass

An excellent quesition! We also are interested in the answer! Anyone?

cchinfosys

Based on some other threads here, and on some SQL Express 2005 research, I ended up doing the following...

Used SQL Server Management Studio Express to define a backup job and media set
Selected Script Action to File and saved it as backupscript.sql
Created a CMD file to run the script
sqlcmd -S servername\SQLEXPRESS -t "C:\scriptpath\backupscript.sql" -o "C:\logpath\logfile.txt"
Created a scheduled task to execute the CMD file
Added this resulting .bak file and the Custom Pollers folder to the tape backup job

I'm still not sure I'm getting everything (Alerts, IIS udpates, etc), but it feels like a good start. The curveball here was that Orion wants to setup a backup job automatically, but SQL Express 2005 no longer supports the SQL Agent, so it bombs out.

*I fixed the script above to remove an extranneous space. Note that the "-S" is case-sensitive.

ubnet

Thank you. This worked great for me after overcoming some issues. So for others like me who are completely new to SQL Express, here's what I found.

I couldn't connect with servername\instancename. I had to use 127.0.0.1\instancename, then make sure TCP/IP was enabled in the configuration manager. Its not by default.

Also the -t option in the script prompts for a timeout value. I looked around and found the -i option that worked instead.

All is working great now. Thanks to people like who who post this stuff so new guys like me can actually learn and get something accomplished.