In case the publication process fails to upload a remote publication to an Internet server, one can update the remote server manually by copying database and other files to the server.
This requires that the remote server already has got a first publication, so the target file area is available and that the web application has a definition for the site, to be able to attach to published data.
If there are many and/or large files we recommend that a Zip archive is made for the database file, for image sub folders etc. Copying one file is less time consuming then trying to copy thousand files between computers.
Start in the editor server, by freeing the database files from the SqlServer database engine
When users have least problem with an application stop, replace the database on the Internet server
Synchronize attached image and document files in sub folders, to complete the remote publication with files
One possible path is: D:\Assert\Data\Site1\Publication\Remote\Site2 where:
The target folder is defined during configuration and is stored in file: C:\inetpub\wwwroot\AssertWeb\App_Data\server.config on the Internet server.
Refer to the <RemoteArea> element for current value.
One possible path is: D:\Assert\RemotePublish\Site1 where: Site1 is the name of the remote site as it is defined at the editor server in the publication repository.
|