How would I set up weekly backups of specific files in Windows Server 2008?

I recently upgraded a server from windows server 2003 to windows server 2008.
The user interface now only allows daily backups.
How would I set up weekly backups (every Thursday 23:00) of specific files on  C:/
saved to E:/

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott CSenior EngineerCommented:
Take a look at this.

Basically what you do is create your backup job, then create a weekly task to kick off the job.

This shows how to do it for Exchange, but the same principle will apply.

And here's a blog from MS that pretty much says the same thing.

Use the task scheduler.
Scott CSenior EngineerCommented:
I just re-read your question.  if the above won't fit your needs, how about calling a batch file that will copy the specific files from one drive to the other using  the Task Scheduler?

Or run a robocopy using Task Scheduler.
Sounds like you are wanting to use Windows Server Backup.  If this is the case and you have Windows Server 2008R2, then your choices in this matter would be to use a scheduled task to kick off a command line.  Something like:
wbadmin start backup -backupTarget:E:\ -include:c:\folder1\file1.txt,c:\folder2\*.log,c:\folder3\*.* -quiet

Open in new window

Or use a scheduled task to kick off a script that moves files to a specified location that can then be backed up (this method can be used regardless on both Server 2008 and Server 2008R2).

The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

If it is just a few files and you don't need something like Backup Exec you could try Karen Kenworthy's Replicator.
I use that to make an additional copy onto an external USB device in case my BE dies.
Karen has passed away (bless her) and her site is being rebuilt, but since it is such a popular program you can download it from MajorGeeks at:
BiopsychAuthor Commented:
Thanks for your feedback.  Unfortunately, this issue is with Server 2008 not 2008 R2. As you know, 2008 R2 has many more options.

You sent me the link below. Not completely clear from reading this link exactly how to write the batch file for my weekly backup.  If you don't mind could you send me an example of the code to enter into the batch file for a backup of C:\ (similar to what you did if had been 2008 R2). I can take care of configuring the scheduler.  
I actually would like to back up about 95 % of the files weekly but looks like can only run scheduled backups in 2008 for complete drives. So for now I'll back up the entire drive. Prefer to not have to buy additional software right now.

Thanks again

"Or use a scheduled task to kick off a script that moves files to a specified location that can then be backed up (this method can be used regardless on both Server 2008 and Server 2008R2)."
Scott CSenior EngineerCommented:
Using RoboCopy would suit your needs I believe.

You can backup what you want, where you want, when you want.
I kind of figured that you were in the 2008 boat.  Now that I have had more time to reflect on the recommendation that I originally made, which, if I am honest, is a really bad recommendation.

Why is it bad?

1.  It's inefficient (you have to move the files from their original volume to a new volume that is used for backup).
2.  At the same time, you have to take permissions into account (you will want to maintain the permissions between the original files, the copied files and the files that are backed up or else users may find that they cannot access restored files).
3.  Are any of the folders you copy shared?  If so, will you have to reshare them in case of a restoration.  Does this mean that you want to maintain share permissions?

I could go on but I think you get the gist.  In reality it takes something that is supposed to be easy; straight-forward; simple (from an Administrative point of view), and perverts it into a complex; convoluted; baffling, mess.  For that I apologize.

Probably the best recommendations are:
A. Use a third-party utility or full-fledged backup solution that can take the permission and share issues into account.  Ideally something that has logging so that you can know whether it is successful or not.  Something that also has some sort of support path in case of a problem.
B. If feasible, upgrade the OS to Server 2008R2 so that the incorporated backup solution can be used in the way you want to use it.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Scott CSenior EngineerCommented:
And, of course, it_saige is correct.  A true backup solution would be best.  Data is the heart of any business and should be treated as such.

As it appears you are backing up a good bit of data and not just a few files, a 3rd party solution would be best.
BiopsychAuthor Commented:

Not clear why #1 below is inefficient. Makes no sense to backup files on the same volume on which they currently live.
Or did I misunderstand your point?  However, considering all your points together it looks like Windows 2008 offers
a very limited backup within its GUI. This was a bad surprise as we have a couple servers that run 2008 R2, which offer OK backup options.
Can not upgrade this server to R2 as it is only 32-bit.
Maybe ScottCha's Robocopy  suggestion would be a good simple free  solution. I'll give that a try when I have some time.

1.  It's inefficient (you have to move the files from their original volume to a new volume that is used for backup).
It is inefficient because the task relies on an intermediate volume.

Essentially, you would need to copy (using Xcopy or Robocopy) the files you want to backup to a different volume (the intermediary), then you would schedule your backup job to backup the intermediate volume.  As I said, it's inefficient.  Also you would only need to do this if you were planning to use Windows Server Backup to backup certain file(s)/folder(s) on a Windows Server 2008 OS (not Windows Server 2008 R2).

BiopsychAuthor Commented:
Thanks for your suggestions. I did not have time to test the solutions last week.
Will test this week as soon as I can and will award points after that. Thanks for your patience.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.