vc灾难_灾难规划

vc灾难

A great kickstart of an article on Linux.com (by Brian Jones) got me started on a quick review of the disaster recovery plans I have in place for my own systems as well as those of my clients.

Linux.com上的一篇文章 (由Brian Jones 撰写)的一个很好的开始，让我开始快速回顾了我为自己的系统以及客户系统制定的灾难恢复计划。

Having come from enterprise level IT in financial services, I had a good bit of experience planning — so even in the small and medium environments I operate in now, disaster recovery always becomes part of client conversations.

来自金融服务中的企业级IT部门，我有很多经验计划-因此，即使在我现在所处的中小型环境中，灾难恢复也始终成为客户对话的一部分。

Like most, if not all of us, I perform the traditional backups from the web side of operations (databases, configuration files, data, etc.) both locally as a hot backup and remotely on a daily basis using automation. Once monthly a batch of these backups go to CD or DVD and land in a bank safe deposit box.

与大多数人(如果不是所有人)一样，我从网络操作(数据库，配置文件，数据等)的网络端执行传统备份，既在本地作为热备份，又每天使用自动化进行远程备份。 每月一次，将这些备份的批次放入CD或DVD并放入银行保管箱。

Internally (non-web) the same basic processes occur, daily backups both in local hot copies and a weekly remote backup as well as once monthly archives to CD or DVD.

内部(非Web)发生相同的基本过程，包括本地热拷贝的每日备份和每周的远程备份，以及每月一次将存档归档到CD或DVD。

In many cases I have also begun using small RAID arrays with clients. For example, one customer deals in audio and video daily. They run an external firewire RAID 1 array of two 160 GB drives. In RAID 1 drive A is mirrored by drive B. We also have a drive C that is swapped out once weekly and taken off site. In this scenario we chose hot swappable drives so we could yank and change the mirror drive on demand.

在许多情况下，我也开始在客户端上使用小型RAID阵列。 例如，一位客户每天进行音频和视频交易。 他们运行由两个160 GB驱动器组成的外部火线RAID 1阵列。 在RAID 1中，驱动器A由驱动器B镜像。我们还有一个驱动器C，该驱动器每周更换一次，并移至现场。 在这种情况下，我们选择了热插拔驱动器，因此我们可以按需拉动和更改镜像驱动器。

Recently I have also been testing the use of third-party backup services that offer compressed data transfer and storage over a broadband or higher Internet connection. These vendors utilize encryption to secure the process and store data indefinitely or by parameters set when the service is initialized. I have found one particular service that offers 1 GB of compressed storage for $17.50 monthly (backs up 2 GB of data).

最近，我还测试了第三方备份服务的使用，该服务可通过宽带或更高的Internet连接提供压缩的数据传输和存储。 这些供应商利用加密来保护过程并无限期地存储数据，或者通过初始化服务时设置的参数来存储数据。 我发现一种特殊的服务，它提供1 GB的压缩存储，每月费用为17.50美元(备份2 GB的数据)。

Back to the beginning — one thing I have not done is investigated profiling software such as that in SUSE. SCPM (System Configuration Profile Management) looks to be a candidate for just such an add-on to my plans. SCPM profiles and stores information on your (for example) Apache, firewall and other daemon configuration files and stores them in a text file. So long as these files were included in your backup plan, recovering from a server disaster could be easier.

回到开始-我还没有做过的一件事就是研究诸如SUSE中的分析软件。 SCPM(系统配置档案管理)似乎是我计划中此类附件的候选人。 SCPM概要分析并存储有关(例如)Apache，防火墙和其他守护程序配置文件的信息，并将它们存储在文本文件中。 只要这些文件包含在备份计划中，从服务器灾难中恢复可能会更加容易。

Basically a reinstall of the base OS with your required daemons would be followed with a restoration of the profiles and then SCPM should redeploy the stored configuration data for those critical applications. Not only did you recover from disaster, but you probably did it hours faster.

基本上，使用所需的守护程序重新安装基本操作系统之后，将还原配置文件，然后SCPM应该为那些关键应用程序重新部署存储的配置数据。 您不仅从灾难中恢复了，而且还可能更快地将其恢复了几个小时。

I would look forward to hearing about your disaster recovery plans, goals or questions.

我希望听到您的灾难恢复计划，目标或问题。

翻译自: https://www.sitepoint.com/planning-for-disaster/

vc灾难