Network management combat server can not do automatic backup

In the current Internet development, many unit users and even individual users have begun to own their own servers. In order to ensure the security of the data information stored in the server, network administrators often perform regular backup operations on important information in the server to prevent the server from recovering important information in time if the server encounters an accident or the target data is damaged by the virus. When backing up data information in the server, many people use the backup tool built into the Windows server system to directly back up the data. Some people also use professional backup tools to back up important data in the server; this is not The author uses the "task plan" function built into the Windows server system to automatically back up important data information in the server. However, if the backup operation is not properly set, it will often cause the server to fail to perform backup operations on the target data. This is not the case. Recently, after modifying the password of the login server, I found that the server cannot perform automatic backup operations.

The server is installed on the Windows 2003 Server operating system. In order to ensure the security of important information, I log in to the system as the super administrator account Administrator, and then create it through the “Task Schedule” function under the system tool. A new task plan databackup, to let the server system automatically back up all files under the D disk DATA folder every night at 12 o'clock. After creating the mission plan, the author will check the system's running log frequently in the next few days and find that the server can perform backup operations normally. Later, considering the security factors, the author often modified the password of the super administrator Administrator account, but once the password was modified, the author found that the task plan databackup could not be automatically executed; unless the password of the super administrator Administrator account was changed, At the same time, the attribute of the data planup of the task plan is modified, and the password of the Administrator account at the running mode is also changed together to ensure that the data backup of the task plan is executed normally.

Considering that changing the password of the Administrator account will happen frequently, but it is easy to forget to modify the attribute of the task plan databackup together. In view of this, I plan to create a new account name beifen, and the account name belongs to it. Create a password with a higher security level for the Beifen account in the Backup Operators group of the server system. Next, the author opens the system's task plan list window, and right-clicks the task plan databackup icon in it, executes the “Properties” command from the pop-up right-click menu, and then clicks the “Tasks” tab in the pop-up properties window. , open the tab page as shown in Figure 1. In the “Run Mode” section of the page, modify the Administrator account to beifen account; click the “Set Password” button again to change the password of the Administrator account to the password of the Beifen account, and finally click the “OK” button. First, the task plan databackup can be automatically run with the beifen account. In the future, when the author changes the password of the Administrator account again, it is not necessary to modify the attribute of the task plan databackup at the same time. But what surprised me is that since I changed the running identity for the task plan databackup, I found out that the backup operation was not automatically executed from the server system running log. What is going on?


Figure 1 databackup attribute

The author first suspects that the system's mission plan may not be executed on time. The possible causes of this phenomenon are often the attribute setting of the task plan databackup error or the system's Task Scheduler service is not due to unexpected reasons. Normal start. In order to verify your guess, the author first clicks the "Start" /"Run" command, in the pop-up system run dialog box, enter the string command "services.msc", click the "OK" button, open the system Service list interface; find the system service Task Scheduler option from the interface, and then double-click with the left mouse button to open the property setting window of the service, from the "General" tab page of the window (as shown in Figure 2), the author It is found that the startup type of the Task Scheduler service has been set to "automatic", and the service status has also been displayed as "started", which indicates that the above failure has nothing to do with the Task Scheduler service. Next, the author opens the system's task plan list window, and right-clicks the databackup task plan. From the shortcut menu that appears, click the "Properties" option to enter the databackup property settings dialog; in the dialog box At the "running mode", the author confirmed that the running account at this time is indeed beifen (it is worth noting that the account name here must appear in the format of "Server\\beifen", where Server is the computer name of the server); The password of the account should be entered incorrectly. I clicked the "Set Password" button, re-entered the password in the password setting window that appears later, and finally clicked the "OK" button to close the password setting window. Then in the system's task plan list window, right-click on the databackup task plan, and click the "Run" option from the shortcut menu that appears, if there is "Show" in the "Status" column of the interface of Figure 3. If the word "Failed to start" indicates that the property settings of the databackup task plan are still incorrect, you need to re-set it; if you click the "Run" option, "Failed to start" is not displayed in the "Status" column of the interface of Figure 3. The words indicate that the databackup task plan has been successfully started, as shown in Figure 4. However, after excluding the databackup task plan setting error factors, the author found that the system backup operation still can not be carried out normally.

Figure 2 Task Plan Settings


Figure 3 Task Plan Settings
< BR>
Figure 4 Task Schedule Settings

Now that the mission plan can start normally, the only possibility now is that the backup operation itself has a problem. After careful examination and analysis, the author found that the Windows 2003 Server operating system will save the relevant backup information in the personal configuration folder of the corresponding account. For example, if the author logs in to the server with the Administrator account, the related backup information will be saved automatically. Under the "X:\\Documents and Settings\\Administrator\\Local Settings\\Application Data\\Microsoft\\Windows NT\\NTBackup\\data" folder (where X is the installation disk partition where the Windows system is located); go to the "data" folder window In the author, I saw the Backup.bkf backup file and backup log files such as backup01.log, backup02.log, backup03.log, etc. After opening one of the log files, we can easily get the content interface shown in Figure 5. I learned that the backup operation has been done, but these log files are created before the author modifies the task plan databackup attribute, and the backup log file after the task plan databackup attribute is modified should be saved in "X:\\Documents and Settings". \\beifen\\Local Settings\\Application Data\\Microsoft\\Windows NT\\NTBacku Below the p\\data" folder, but when I enter the folder window, I did not find the backup file Backup.bkf, but only the backup log files such as backup01.log, backup02.log, backup03.log, etc. After one of the log files, I found that "skip the file in the "Windows NT\\NTBackup\\data\\Backup.bkf' folder, no folder was found" prompt, it is obvious that when the backup operation is performed with the beifen account, beifen The account does not have access to the Backup.bkf file in the personal configuration folder of the corresponding Administrator account. This will naturally cause the above error message, which affects the automatic execution of the backup operation.

Figure 5 Backup log file

After finding the cause of the failure, the author believes that the backup operation can still be performed automatically, and must be reached in the task plan databackup After specifying the running time, the beifen account has the right to access the Backup.bkf file under the Administrator personal configuration folder. To do this, you can use the following method:

The first method is to enter the X :\\Documents and Settings\\Administrator\\Local Settings\\Application Data\\Microsoft\\Windows NT\\NTBackup" folder window, then right-click the "data" subfolder icon in the window and execute from the pop-up context menu. "Share and Secure" command, and click the "Share" tab in the interface, then select the "Share this folder" option in the tab page, then click the "Permissions" button to open the "data" subfile Folder permissions dialog box, then click the "Add" button in the interface shown in Figure 6, import the beifen account, and select the "read" permission for the account, Beifen can make the kind of access to the Administrator account has the right to personal configuration folder following Backup.bkf file.


Figure 6 Permission Properties

The second method is to enter "X:\\Documents and Settings\\Administrator\\Local Settings\\Application Data\\Microsoft\\Windows NT\\NTBackup\\data" Folder window, then copy a copy of the Backup.bkf file directly into the "X:\\Documents and Settings\\beifen\\Local Settings\\Application Data\\Microsoft\\Windows NT\\NTBackup\\data" folder; then open it again The property setting interface of the databackup task plan, and then modify the Administrator account in the interface to beifen account, so that the ntbackup.exe backup program can automatically access the Backup.bkf file under the beifen personal configuration folder.