How could I do backups for my packages?

Hi all of you,

Formerly when we ran dts we had DtsBackup2000. So we could to arrange lots of backups around the network in a centralized way. But now how to run backups in groups no individually way?

We've got five sql25k along with its dtsx packages and we'd like have all of them in the same place.

Any tool or idea?

Thanks in advance,

What storage method do you use?

|||

Hi Darren,

Thanks for your answer. We've LEGATO system for our db. in regard packages we save them as .dtb and .dts files.

TIA

|||

I meant how do you store your SSIS packages, as that would impact what I suggest for a backup of them! I know about DTS, you told me you used DTSBackup.|||

Hi again,

Individually, people save them in its own local machines but, of course, that's not very safe.. I mean, VSS is not used at all.

The SSIS packages are stored on the production server and on the development server.

Up to the date the only way for me is do backup one after one.

Thanks Darren,

|||

All of them in MSDB.

I don't know if this answer finally clarifies this post.

|||

If the packages are deployed to MSDB as opposed to File System, backing up the SQL database on Production & Dev will effectively back up your packages.

Obvioulsy the "undeployed" latest or working versions on individual machines are at the mercy of the users! At least suggest they are saved on a network drive that is backed up if they cannot or will not use VSS. Local machine saves are madness

|||

Hi Will,

Thanks for your answer. But our main idea is to retrieve as soon as possible a concrete dtsx without have to do a restore when there's an issue or problem.

|||

If that is the case, go overboard... save all packages to a shared drive on the network (make sure that your sql agent user / proxy has access). Back that up nightly and run all imports into your MSDB from this drive. Also, make sure that you are doing full backups of the sql server in test and prod.

//mycomputername/SSISPackages/PackageName(s)

//mycomputername/SSISPackages/ConfigFiles

backup all files in SSISPackages...

|||

enric, if you need to rollback to a working version of a SSIS package then I woudl look to re-deploy that working package from your release management store or source control system.

DTSBackup made sense in DTS because it was very common to change packages on the server, just because the tools worked that way, but with SSIS, you should always have an offline copy with changes made by the developer, and that "should" be under some control, source control, release management etc.