Domino控制台指令大全Temporarily pauses the collection of platform statistics. pull (pul) Starts database replication from the specified server to the local server. Typically, a Connection document defines the scheduled replication between servers, and this command is used to manually override it. Syntax pull server [database] Command options server The name of the remote server you wish to pull database changes from to the local server. The remote server name should be the full hierarchical name, and enclosed in quotes if there any spaces in it. database Optionally, the name of the database on the local server into which you wish to pull changes from the server. The database on the other server must be a replica copy (that is, have the same replica ID) in order for replication to occur. If the database parameter is not listed, then the server prepares a list of databases with identical replica IDs on both servers, and then pulls the changes in each from the other server. Examples pul Westline/Alameda pulls changes from the remote server named Westline/Alameda to the local server for all databases having the same replica ID. pul Shoreline/Alameda names.nsf pulls changes from the remote server named Shoreline/Alameda to the local server for the NAMES.NSF database. See Also push, replicate, route push (pus) Starts database replication from the local server to the specified server. Typically, a Connection document defines the scheduled replication between servers, and this command is used to manually override it. Syntax push server [database] Command options server The name of the remote server you wish to push database changes to from the local server. The server name should be the full hierarchical name, and enclosed in quotes if there any spaces in it. database Optionally, the name of the database on the local server out of which you wish to push changes to the remote server. The database on the remote server must be a replica copy (that is, have the same replica ID) in order for replication to occur. If the database parameter is not listed, the server prepares a list of databases with identical replica IDs on both servers, and then pushes the changes in each to the other server. Examples pus Westline/Alameda pushes changes from this local server to the remote server Westline/Alameda for all databases having the same replica ID. pus Shoreline/Alameda names.nsf pushes changes from the local server to the remote server Shoreline/Alameda for the NAMES.NSF database. See Also pull, replicate, route quit (q) Closes down the Domino server. Syntax quit [password] Command options password If the SET SECURE command has been run to provide a password for operation of the Domino server, this password needs to be provided in order to shut down the server. See Also exit, restart server replicate (rep) Starts database replication from this server to/from the specified remote server. Typically, a Connection document defines the scheduled replication between servers, and this command is used to manually override it. The process works in two stages: the local server pulls any changes from the remote server, and then the remote server has the option to pull any changes from the local server. The remote server refers to the replication schedule, and performs a pull now only if this manual replication doesn't fall within the timeframe the server replicates to this server. Syntax replicate server [database] Command options server The name of the remote server you wish to push/pull database changes to or from. The server name should be the full hierarchical name, and enclosed in quotes if there any spaces in it. database An optional parameter specifying which database to replicate. If this parameter is not present, the server attempts to replicate every database that has a common replica ID between the two servers. Examples This example replicates the Domino Directory between the two servers with the command rep Westline/Alameda names.nsf: > rep westline/alameda names.nsf 07/18/99 12:10:43 AM Database Replicator started 07/18/99 12:10:43 AM Starting replication with server westline/alameda 07/18/99 12:10:43 AM Pulling names.nsf from westline/alameda names.nsf 07/18/99 12:10:44 AM Replicator added 1 document(s) to names.nsf from westline/alameda names.nsf 07/18/99 12:10:44 AM Pushing names.nsf to westline/alameda names.nsf 07/18/99 12:10:44 AM Replicator added 1 document(s) to westline/alameda names.nsf from names.nsf 07/18/99 12:10:44 AM Replicator updated 6 document(s) in westline/alameda names.nsf from names.nsf 07/18/99 12:10:44 AM Finished replication with server westline/alameda 07/18/99 12:10:44 AM Database Replicator shutdown See Also pull, push, route restart 上一篇：如何禁止Norton扫描Notes 下一篇：分级 IBM Lotus Domino 邮件服务器 更多相关文章
|
推荐文章
精彩文章
|
