|
|
| Line 8: |
Line 8: |
| * [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ] | | * [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ] |
| * [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] | | * [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list] |
|
| |
| How to copy files from one Domino server to another
| |
| Wednesday, March 21st, 2007
| |
| Recently I needed to make "copies" of some Lotus Notes databases and didn't want to do it from my Notes client. This would have take hours considering the database was 5gb. I knew that there had to be a way to do this and thanks to the assistance of my friend Thomas Gumz, I was able to issue a command line from the Domino server console and presto, the database was instantly copied. Yes, it's not documented nor supported, but has been around for a long time, at least since V4 according to Thomas.
| |
|
| |
| So let's look at what you need to do to enable this feature:
| |
|
| |
| The server console commands are turned off by default, you need to first enable them:
| |
|
| |
| Set this server notes.ini variable, like so:
| |
|
| |
| > set config CLUSTER_ADMIN_ON=1 (even if the server is not a in cluster, doesn't matter).
| |
|
| |
| No need to restart the server, it becomes active immediately.
| |
|
| |
| This enables this new command:
| |
|
| |
| CL COPY sourcedb targetdb
| |
|
| |
| Examples for the CL COPY command:
| |
|
| |
| > CL copy serverA!!db1.nsf serverB!!db2.nsf
| |
| This would create a regular non-replica copy of db1.nsf on serverA as db2.nsf on ServerB
| |
|
| |
| > CL copy serverA!!db1.nsf serverB!!db2.nsf REPLICA
| |
| This would create a replica copy of db1.nsf on serverA as db2.nsf on ServerB
| |
|
| |
| > CL copy serverA!!db1.nsf serverB!!db2.nsf TEMPLATE
| |
| This would create a template copy (only design, no data) of db1.nsf on serverA as db2.nsf on ServerB
| |
|
| |
| > CL copy db1.nsf db2.nsf
| |
| This would create a regular non-replica copy of db1.nsf as db2.nsf on the same local server
| |
