I'm trying to perform a zlmmirror from a primary server in one management zone to a primary server in a different management zone. The catalogs and package bundles were created in the proper folder, but all the patches are being stored in the base folder and not in separate folders like the original primary server.

For example, on the original primary ZLM server:
Bundles/Prod/OS/
-> SLES10-SP3-Updates-patches (Folder)
-> SLES11-Updates-patches (Folder)
-> SLES10-SP3-Updates-bundle (RPM Package Bundle)
-> SLES11-Updates-bundle (RPM Package Bundle)
-> SLES10-SP3-Updates-i586 (Catalog)
-> SLES10-SP3-Updates-x86_64 (Catalog)

On the new primary ZLM server:
Bundle/Prod/OS
-> SLES10-SP3-Updates-bundle (RPM Package Bundle)
-> SLES11-Updates-bundle (RPM Package Bundle)
-> SLES10-SP3-Updates-i586 (Catalog)
-> SLES10-SP3-Updates-x86_64 (Catalog)
-> patch-slesp1-apache2-mod_python-4449_SLES10-SP3-Update (Patch)
-> ....
-> patch-slesp1-rsync-4798_SLES10-SP3-Update (Patch)
-> patch-slesp1-sapinit-4913_SLES10-SP3-Update (Patch)


The patch folders, on the original primary ZLM server, were created from downloading the patches from Novell. They were not manually created. I'm curious why the structure wasn't retained during our internal mirroring?