Hello.
We are thinking about doing a thorough clean-up of our CORE server to get rid of stuff that are no longer in use or outdated.
I've via SQL identified which packages we have that are currently not assigned to a task in any way (preliminary, main or final) and would like to establish a procedure for archiving those packages before deleting them so I have them as a backup in case they're still needed in near future.
The initial thought of what I'd like to end up with is having the package exported to a folder as an .ldms file with all it's settings as well as all the files (primary file and any eventual additional files) in the correct folder structure. This could then be zipped for easy storage.
Depending on the complexity of the package, this could be anything from a 2 minutes job to a hour long job per package if the package contains a lot of additional files from multiple separate folders. Knowing that this potentially needs to be done for several hundreds of packages, this could be a very time consuming task.
Does anybody have a better idea or perhaps a (semi)automated way of archiving a package? I'm aware of package.porter.exe but that doesn't work for individual packages.
Thanks in advance.
/Michael