强制备份问题
为了安全起见,备份perforce服务器目录下的所有文件是否足够?
for safety purpose, is it enough to backup all the files under perforce server directory?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
为了安全起见,备份perforce服务器目录下的所有文件是否足够?
for safety purpose, is it enough to backup all the files under perforce server directory?
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(3)
简短回答:否
长答案:您需要了解的有关 Perforce 数据备份和恢复的所有信息,请参阅 手动。简而言之,对于不耐烦的人:
(验证服务器的完整性)
(做一个检查点;确保这一步成功)
(如果您使用日志文件运行 Perforce,您应该这样做)
(这是实际数据,不要与 Perforce 服务器目录中的 db.* 文件混淆。)
但请务必阅读手册,尤其是有关各种恢复方案的内容。记住:
备份通常工作正常,只是恢复失败。
Short answer: No
Long answer: All you need to know about backup and recovery of Perforce data is detailed in the Manual. In a nutshell for the impatient:
(Verify the integrity of your server)
(Make a checkpoint; make sure that this step is successful)
(if you run Perforce with Journal files, which you should)
(that's the actual data, not to be confused with the db.* files in the Perforce server directory.)
But please do read the manual, especially about the various restore scenarios. Remember:
Backups usually work fine, it's the restore that fails.
除了 p4 手动答案中 jhwist 的正确答案(永久链接)我想添加这是我在使用 Perforce 几年的过程中学到的一些东西。
...
根据存储库的大小,对 p4 数据库执行验证可能需要几个小时,在此期间将被锁定,并且没有人能够执行任何查询。锁定 P4 数据库可能会对用户产生多种流程影响,例如:如果有人在这段时间内使用或尝试使用 P4,P4SCC 插件(即用于 Visual Studio 集成)将会旋转,用户最终会必须强制退出才能重新获得控制权。
解决方案
p4 verify //...
和检查点。另外:由于这很可能是在晚上或周末运行的自动化过程,因此您必须需要彻底阅读检查点日志文件以确保其成功 否则,当您需要执行恢复时,您将陷入困境(请阅读下一点)。备份不应该是一个一劳永逸的过程。
有关 Perforce 备份的更多信息,请参阅 Perforce 白皮书:Perforce 的高可用性和灾难恢复解决方案。
哈特哈,
In addition to jhwist's correct from the p4 manual answer (permalink) I would like to add a few things that I've learnt during using Perforce for several years.
...
Depending on the size of your repository performing a verify on the p4 database can take several hours, which during it will be locked and no one will be able to perform any queries. Locking the P4 database can have several on flow effects to your users, for example: if someone is using or attempts to use P4 during this time a P4SCC plug-in (ie. for visual studio integration) it will spin and the user will eventually have to force quit to regain control.
Solution
p4 verify //...
and checkpoint using p4d_2.Also: As this will be more than likely be an automated process run at night or over the weekend can cannot stress enough that you need to thoroughly read the checkpoint log file to ensure that it was successful otherwise you will be in a difficult spot when you need to perform a restore (read the next point). Backup should not be a set and forget procedure.
Further information about Perforce backup can be found in Perforce whitepaper: High Availability And Disaster Recovery Solutions For Perforce.
HTH,
FWIW 我在自己的开发工作站上使用了额外的备份策略。我有一个 perl 脚本,每天晚上运行,并查找我从给定的工作空间列表中从 Perforce 签出的所有文件。然后,该文件列表将作为我正常工作站备份过程的一部分进行备份。查找已检出文件的 Perl 脚本对我来说看起来相当棘手。它不是我写的,对 Perl 也不是特别熟悉。
如果有人感兴趣,我可以在这里发布脚本以及我如何调用它。
请注意,该脚本是在 Perforce 推出“搁置”功能之前开发的。我现在可能会更好地拥有一个每天晚上“搁置”我的工作的脚本(除了我当前的备份策略之外或代替它)。
这是脚本:
运行:
FWIW I have used an additional backup strategy on my own development workstation. I have a perl script that runs every night and finds all files that I have checked out of Perforce from a given list of workspaces. That list of files is then backed up as part of my normal workstation backup procedure. The Perl script to find the files that are checked out looks pretty tricky to me. I did not write it and am not particularly familiar with Perl.
If anyone is interested, I can post the script here along with how I call it.
Note that this script was developed before Perforce came out with its "shelving" capability. I might be better off now to have a script that "shelves" my work every night (either in addition to my current backup strategy or in place of it).
Here is the script:
To run: