1 person found this helpful
This is not a supported or tested scenario.
You should restore from backup. Or clone another publish instance.
OK, but what if you have a single publish instance setup and the backup is inaccessible. You've got a working author and a corrupt publish...
How do you create a a new publish instance from an author instance and a quickstart? Surely creating a publish instance can't be solely based upon already having one. That would be a chicken/egg situation.
I'd say that your infrastucture plan is seriously flawed if you have a single publish instance and no usable backups.
That said, if you have a working author, you can replicate the content from the author instance to a newly created publish instance.
I'd say that I was merely trying to get a reasonable answer to what I feel is a reasonable question.
The answer to how to create something shouldn't be "copy it from another you already have". Restoring the publish instance from backup would mean that it would not contain anything that had been activated since the backup was made, and restoring the author (and losing any work done since the backup was made) simply because your publish instance got corrupted seems like a huge waste.
As to replicating from the author to the new publish, wouldn't you have to replicate all packages, all content, and a large portion of the data stored in the other folders like etc and apps? The replicate tree function does not allow you to just replicate /etc, for example, which could lead to a lot of manual replications being needed.
It just seems difficult.
Another avenue for performing bulk activations is to use a workflow and workflow packages. Add all your content to the workflow package and use it as the payload for a workflow that activates the content. The Request Activation workflow model does this out of the box.