Mastering the Windows Backup Strategy and Finding the Shortcut to Success

Many system administrators choose to use the system default backup strategy regardless of any situation when designing the Windows backup strategy, but often do not grasp the essence of the problem, often Some problems have arisen. According to the author's experience, the Windows backup strategy is not very difficult. As long as you master the skills, you can find a path to success. I believe that as long as the system administrator can solve the following four problems, the backup strategy is successful. The specific situation is as follows.

First, how to backup?

When designing a backup strategy, system administrators need to consider not only which data needs to be backed up, but also how to perform it. Backup. This is a relatively core link. Because of the different backup methods, there are different restrictions. It will also be different in the way of operation. Specifically, you need to pay attention to the following.

One is the device that needs to be backed up. The backed up devices are both disk and tape. If you choose a disk backup, you can do it through the ServerBackup component. With this tool, the data determined above can be backed up regularly to the internal connection (mounted on another hard disk in the server or externally connected disk (offsite backup). However, it should be noted that this tool does not support tape. Backup. If the user needs to back up the data to the tape design, it needs to use another Microsoft tool “System Center Data Protection Manager” or use a third-party application software. Obviously, the adopted The backup devices are different, and the technologies they need to use are different. This is a core reason to determine how to back up.

The second is the backup method, which mainly includes full backup and differential backup. Full backup is no matter Whether the data has changed or not, the data is backed up completely. On the contrary, the differential backup needs to judge whether the data has changed before the backup. Only the changed data is backed up. Features. From the performance point of view, differential backup can take up less system resources, The performance impact of the network is relatively small. On the contrary, if the full backup is adopted, it is convenient to manage. However, the negative impact on the performance of the existing system will be relatively large. Generally, the author suggests that the differential backup can be selected according to the actual situation of the enterprise. The combination of full backup, each take the longest. For example, a full backup once a week, the rest of the time is a differential backup.

The third is the backup cycle. Whether it is a full backup or a differential backup, there is a cycle If you perform a differential backup, is it a backup once a day or an 8 hour backup? If you are taking a regular backup, is it a backup once a day or a full backup once a week? When determining this backup cycle, The main thing is the enterprise's consideration of data security. The higher the frequency of backup, the more secure the data, the larger the system resources consumed. The lower the frequency of backup, the lower the performance overhead. Larger.

Second, what data is backed up?

In Windows2008 Server In the operating system, there is a ServerBackup component that can help system administrators to back up related data. Now the first question users need to consider is which data needs to be backed up. In fact, data can be basically divided into three categories. It is the file of the operating system, the second is the file of the application, and the third is the user file.

For the server, it is generally necessary to back up all the files on the server operating system. For the ordinary client. , you need to back up the operating system and application files, and select backups for the user files. After all, there are a lot of files (such as songs, pictures, etc.) on the client that belong to the user's own files. It may not be related to work. From the perspective of improving backup efficiency and saving backup space, it is generally not necessary to back up these files. This is a basic judgment principle. In the actual work, you need to pay attention to the following special files.

One is the application configuration file. For example, the DHCP service or the Oracle database server is implemented on the Windows operating system. These applications often have separate configuration files. Such as Oracle database listening files, network configuration files and so on. For these third-party application profiles, special considerations are needed when making backup strategies. In general, the author's suggestion is to equate these configuration files with operating system files. Sometimes it's even more important than the operating system file itself. Because the operating system fails, you only need to reinstall the operating system. If the configuration file is lost, the workload will be larger when reconfiguring, and the risk will be higher.

Second, the amount of backup data needs to be treated according to different situations. For example, the mail application is used. The storage of corporate mail may take different strategies. If the user can choose whether to save the message locally or on the server. Some companies stipulate that a copy will be kept on the server regardless of whether the user downloads the mail locally. For these two different applications, the data that needs to be backed up is different. As in the previous case, the user can select the mail to be saved on the client and delete the mail on the server. At this time, when selecting the backup data on the client, the user needs to download the mail to the local as the backup object. Conversely, if the message is stored on the server, then the user downloading the message to the local is not necessary for backup. Previous12Next page Total 2 pages