Package Replication and Publishing
Always back up your packages every day or night using package replication and publishing. Because locking information does not travel with packages (or partial packages) when they are replicated, it is recommended that you apply a version to each package according to date. Do not replace or overwrite packages; delete the old package entirely and then install the new package.
Note:
If you do replace or overwrite packages, webMethods Integration Server takes the intersection of elements in the Navigation panel. It will also move the existing package to the replicate\salvage folder of the server instance.
When you replicate and publish a package, the locking information is not preserved. This is expected behavior and is part of the feature's design. You can, however, preserve system locks (read-only file attributes).
Before you publish a package, keep in mind that user locks are not preserved.
When you salvage a deleted package, lock information is not preserved. Before you salvage or delete a package, make sure that all locks are removed from the destination package.
It is not recommended that you use system or user locking on packages that are frequently replicated and/or partially replicated. For example, when sending frequently updated packages to partners.