将数据库移动到另一个文件夹
在服务器运行时，如何将数据库从同一服务器上的一个文件夹重新定位到另一个文件夹？
How can I relocate database from one folder to another on the same server while the server is running?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Domino 管理员可以选择在后台移动数据库。
我从未使用过它，我认为它会创建原始数据库的副本，然后删除源。
我总是在操作系统级别上移动：停止多米诺骨牌，mv 文件，启动多米诺骨牌。如果在同一分区上，则需要更少的时间和空间。
HTH。
The Domino Administrator has an option to move a database in background.
I never used it and i think it will create a copy of the original database and then delete the orgin.
I always move on os level: stop domino, mv file, start domino. It takes much more less time and space if on the same partition.
HTH.
您可以在不停止服务器的情况下执行此操作。确保所有用户都在数据库之外。
首先，转到控制台并输入 drop users （这会断开用户与服务器的所有连接。听起来很糟糕，但这就像中断他们的网络连接，而且他们的 Notes 工作站足够智能，可以重新连接） 。
接下来输入dbcache刷新。这会清除服务器对特定 NSF 文件的所有缓存锁定。
现在（快速）转到操作系统级别的文件（Windows 资源管理器，或服务器上的任何等效项）并将文件移动到新文件夹。如果不起作用，您可能需要重复几次 dbcache 刷新功能。有时，服务器会立即再次收回控制权，尤其是当有人重新连接到该 NSF 文件时。
You can do this without stopping the server. Make sure all users are out of the database.
First, go to the console and type drop users (which drops all connections users have to the server. Sounds bad, but it is like interrupting their network connections, and their Notes workstations are smart enough to reconnect).
Next type dbcache flush. This clears any cache locks the server has on the specific NSF file.
Now (quickly) go to the file at the OS level (Windows Explorer, or whatever the equivalent is on your server) and move the file to the new folder. If it doesn't work, you may need to repeat the dbcache flush feature a few times. Sometimes the server takes control back again immediately, especially if someone reconnects to that NSF file.
在新文件夹中创建数据库的新副本，然后一旦您对所有内容都已复制感到满意，就会将所有人锁定在旧文件夹之外，禁止在 ACL 中进行访问。几天后，您可以删除第一个副本，您可以通过在服务器控制台上执行一系列 drop all 来强制每个人都转移到新副本。
如果用户位于数据库中，则不会有任何区别，但当他们注销并尝试返回服务器时，只会将他们重定向到新文件夹中的副本，这可能意味着轻微的延迟，因此最好进行切换下班时间。
小心不要将自己和其他系统管理员锁在外面，也不要选中同步 acl 选项！在服务器上拥有同一数据库的多个副本也不再是问题，尽管出于习惯，我不会将旧数据库放置太久。
Create a new replica of the database in the new folder then once your happy that everything has replicated lock everyone out of the old one disallowing access in the ACL. In a few days you can remove the first replica, you can force everyone over to the new replica by doing a series of drop all's on the server console.
If users are in the database it won't make any difference but when they log out and try to get back in the server will simply redirect them to the replica in the new folder, it may mean a slight delay so switch over is best done out of hours.
Be careful to not lock yourself and other system admins out, and do not check the syncronise acl option!! It's also no longer a problem having multiple replicas of the same database on a server although out of habit I wouldn't leave the old one around to long.