Processing excluded directory

System

Hello all,

We are doing a remotediff deployment between our Sun Solaris staging server (OpenDeploy base server) and Sun Solaris production server (OpenDeploy receiver server). Let's call the directory we deploy /web/prod. Within /web/prod we have a sub-directory (say /web/prod/content/pdf) that exists on both servers and is NFS mounted to the same location on a NFS server. The contents on the NFS Server is hundreds of sub-directories and thousands of PDFs. Since the sub-directory on both servers are NFS mounted to the same location, they of course contain the same content and don't need to be in the deployment for updating. So I've excluded this directory from our deployment by using excludePath subPath on both the source and target.

It does what it's supposed to and not deploy the content, but the problem is that OpenDeploy goes through each sub-directory of the excluded NFS mount and still processes and compares them. When logging is on verbose, the logs say "Processing excluded directory" for each sub-directory of the parent excluded directory. So it knows it is excluded and to not deploy it, but why is it even crawling down this sub-directories when the parent directory is excluded? Since there are so many sub-directories, this is causing our deployment to take forever even when there are only a handful of content changes.

Is there anyway to exclude a directory in OpenDeploy so that it won't crawl the sub-directories?

Thanks.

Migrateduser

Hi kurtmc,

OpenDeploy should not be crawling through the excluded sub-directories if they are excluded on both the source and the target. I tried playing with it a little bit over here and I'm able to get the "Processing excluded directory" messages you mentioned when the directories are excluded on the target, but NOT on the source. You might want to double check your configs to make sure they are correctly excluding the source paths.

Thanks,
Mike

--
Mike Szela
Sr. Member of Technical Staff
Interwoven, inc.