谁能推荐一个好的备份“系统"?对于开发者? [英] Can anyone recommend a good backup "system" for a developer?

问题描述

我在办公室周围被称为后援".作为开发人员，我经常在项目之间来回跳动，结果，我并不总是确切地记得当我返回到每个项目时，每个项目中都存在什么变化.通常，我必须将本地更改与源代码控制系统中的更改进行比较，然后最终我将全部记住.事实是，我并不总是那么做.有时，我必须快速为客户端构建一些东西，因此我要备份工作目录，这样我就可以从源代码管理中获取最新文件，并快速构建DLL-同时又要知道另一个(在内部-进度)更改是安全的.

I'm known around the office as "the backup guy". As a developer, I often jump back and forth between projects, and as a result I don't always remember exactly what changes were present in each when I return to them. I usually have to compare my local changes versus those in our source control system, and then I'll eventually remember it all. Thing is, I don't always have the luxury of doing this. Sometimes I have to build something for a client quickly, and so I make a backup of the working directory, and that way I can get the latest files from source control, and build the DLL quickly - all while knowing that the other (in-progress) changes are safe.

问题在于，我现在在每个项目目录中都积累了一堆备份文件夹，这使得查找我正在寻找的特定更改变得更加困难.虽然我的做法已经发展到我总是花时间给每个备份文件夹起信息性的名称，但我开始认为我最好编写自己的工具.

The problem is that I've now accumulated a bunch of backup folders in each project directory, which makes it harder to find the specific change I was looking for. while my practices have evolved to the point that I always take the time to give each backup folder an informative name, I'm starting to think I'd be better off writing my own tool.

例如:如果我在Windows资源管理器中选择了几个文件夹，我希望有自己的上下文菜单项来触发我自己的备份应用程序.该应用程序将提示我输入备份名称和说明.然后，它将选择的文件夹移动到特定的集中式备份目录-还会在其中生成"readme.txt"文件，其中概述了备份详细信息.同样，备份也将按日期/时间进行组织.我觉得这将完善我的备份过程，并方便将来的查找.

For example: If I select a few folders in windows explorer, I'd like to have my own context menu item that triggers my own backup application. This application would prompt me for a backup name, and description. It would then move the selected folders to a specific, centralized backup directory - where it would also generate a 'readme.txt' file, outlining the backup details. Also, the backups would also be organized by date/time. I feel this would refine my backup procedure, and facilitate future lookups.

但是，我不禁想知道这些工具是否已经存在.当然，在备份方面，一定有人像我一样痴迷.

But yet, I can't help but wonder if such tools already exist. Surely, someone must be as obsessive as me when it comes to backups.

您知道有什么工具可以帮助我改善备份吗?

Do you know of any tools that could help me improve my backups?

我知道了这篇文章，但不完全是与我想要的保持一致.我希望将备份保留在同一台计算机上-我将自己处理将备份转移到其他计算机上.

I'm aware of this post, but isn't exactly aligned with what I want. I'd prefer to keep the backups on the same machine - I'll handle moving them over to other machines myself.

更新

澄清一下:如果我正在处理任务A，突然间我需要为客户端构建一些东西(任务B)，则必须备份到目前为止为任务A所拥有的内容，并从源代码管理中获取最新信息.工作目录.然后，我启动并完成任务B，然后还原任务A.这是一个理想的整洁方案.但是有时候，我只回到线下一周的任务A，或者更进一步-因为我被任务C，任务D等击中-所有这些都会影响同一个项目.现在，如果计划将这些更改检入，那么我可能会在进行过程中从检入中受益(但是，老实说，我们通常会等到完成后再在这家公司进行检入-这意味着更少未完成代码的签到).因此，我不确定我的每个备份是否应等于一个分支-因为有时我的备份过多.

To clarify: If I'm working on Task A, and suddenly I need build something for a client (Task B), I have to backup what I have so far for Task A, and get the latest from source control into the working directory. I then start and finish Task B, and then restore Task A. This is an ideal, neat scenario. But sometimes, I only get back to Task A a week down the line, or further - because I get hit with Task C, Task D, etc - all of which affect the same project. Now, if these changes are scheduled to be checked in, then I would probably benefit from checking them in as I progress (but to be honest, we usually wait until it is complete before we check it in, at this company - that means less checkins of unfinished code). So I'm not sure if each of my backups should equal a branch - because I'm sometimes excessive with my backups.

推荐答案

我认为您想要的是分布式版本控制系统，例如git.

I think what you want is a distributed version control system, such as git.

这篇关于谁能推荐一个好的备份“系统"?对于开发者?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！