Skip to main content

Windows Server 2012 Backup System State

How to use task scheduler to back up Windows 2012 server system state

Open Task scheduler on Windows 2012, by opening “Control Panel” and clicking on “Administrative Tools” and selecting “Task Scheduler”.

Or you can just go to the start menu and type “task” to search “Task Scheduler” and click "Task Scheduler" on search result to open.

On “Task Scheduler” window, click on “Create Basic Task” which can be found on the upper right corner of the task scheduler  window.

Upon clicking on “Create Basic Task”, the wizard will open and type the name of the Task.

Since the task is to backup “System State” it would be good to name it “Backup System State”  if you’re backing up multiple servers then you can include the name of the server also.

If you have multiple backups and you don’t have any idea for which server is the system state backup then basically it’s good as nothing.

So naming convention is quite important to avoid confusion.

If you want to be quite specific, you can write something  on the description box.

After typing the task name click on next, the system will ask the backup frequency.

Depends on how critical is your system, you can set it at daily, weekly or monthly.

On my case, weekly basis is good enough.

On selecting the backup frequency, you need to consider also the performance and the resources of the server don’t backup at peak hours or when the server is highly utilized.

Click on next, and set the date and hour when you want to start the backup.

Click on next and select “Start a Program”.

Click on next, here’s the most important part. You will need to set the command and the parameters to back up the system state.

On “Program/Script” text box, type “wbadmin”.

On “Add arguments (optional)”, type this parameters:

 start systemstatebackup  -backupTarget:\\\backup\XServerSysState  -quiet

basically it’s:

wbadmin start systemstatebackup 
        -backupTarget:network: location in UNC path -quiet

It would be wise to place the backup on a network share, anyway the purpose of the backup is to use it to recover or restore  once the system goes south.

So if you just store the system state on the same server (in which the system state is being back up) to another partition, then if the system is corrupted or goes down then your backup also goes down.

Once the command and the parameters has been set, click on next and setting up the task scheduler is done.

Click on “finish” to close the wizard.

If you want to try whether the “task scheduler” is working or not, you can force it to run ahead of the schedule by right clicking on the task and selecting “run”.

If everything  goes fine, this window will appear:


Educational App for Android Kids:


Post a Comment

Popular posts from this blog

Copy a single file using robocopy

Copy a single file using robocopy from a local folder to a shared folder on the network.
A simple rule of thumb before any disaster strike, don't interchange the source and the destination.

If source and destination is mistakenly reverse, files might get overwritten. To avoid any loss of data do a test with a dummy file to ensure things work perfectly.
Robocopy [source][destination]   [file to be copied]
robocopy c:\local_c_folder  \\PC_network\shared_folder   file_to_be_copied_xx.txt
The command will be completed successfully provided the network access right has no issues.

Robocopy works quite good on large files. A simple copy or xcopy command will also work but the speed might vary.

Robocopy is free it can be accessed from command line. No need to install the resource kit tool if the operating system is Windows 7 or newer version.

Copy files with selected file extension using PowerShell and Robocopy:

$extension = ('.pdf', '.jpg', '.txt')
gci d:\WorkFolde…

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username.
WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided.
Why would you need a command line tool if there’s a GUI to check?
If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username.
If you have remote computers, you need to delegate someone in the remote office or location to check.
Or you can just write a batch file or script to automate the task.
Here’s the code below on how get computer model, manufacturer and the username.
Open an elevated command prompt and type:
wmic computersystem get "Model","Manufacturer", "Name", "UserName"
Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name.
A sample output below will be generated if the co…