DC System State

Quick question concerning Windows Server 2003 DC's and System State Backups.

Microsoft KB articles always said that when preforming a system state of a domain controller, to also include the SYSVOL folder in the same backup to ensure that you won't have a broken SYSVOL if you every needed to restore the DC.

I just added my first Win2k3 DC to my domain, setup the backup job as usual, but ntbackup doesn't see any files in the SYSVOL folder. It backs the system state up just fine, and it does backup the SYSVOL folder, but doesn't save any of the scripts/folders under that structure?

What gives?
LVL 4
jschwegAsked:
Who is Participating?

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

x
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.

theruckCommented:
try to change the user the ntbackup is running as to administrator then try to run the backup job
jschwegAuthor Commented:
It already is running as administrator
Tony MassaCommented:
Make sure that the Administrator is also a member of the "Backup Operators" group.
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

markpalinuxCommented:

How do you know if doesn't back up the files, where are you looking for that information?
When you go to restore, I believe all you see is SystemState.

If you are looking at the detailed backup job report compare it to what I see, I am also running a system state job on one of my windows 2003 dcs:

I see the scripts from the NetLogon share backed up as
"Folder System State\SYSVOL\c:\windows\SYSVOL\domain\scripts" when I have detailed logging for the backup job turned on.

If you have scheduled the backup job look at the job details and make sure the /l parameter is set to "/l:f", for reference "/l:s" is summary only.

This technote gives some details including notes that you shouldn't try to restore or manually copy to from SysVol, I would cut and paste the text into a new file, if you ever need to "restore" a script as it doesn't sound like you want to cut and paste a file.

Best Practices for Sysvol Maintenance
http://support.microsoft.com/kb/324175/en-us

If you have more please let us know where you are looking to review if the files are in fact backed up.

also now that you are using Windows 2003, get the Group Policy Management Console, it includes command line tools to backup and restore group policy and scripts.

Mark

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
jschwegAuthor Commented:
Concerning the SYSVOL, the reason why I was doing this was becuase of the section labeled "How to Back Up the System State on a Domain Controller" in the below article where it says to include this folder. It is for Windows 2000, but I was assuming those operations haven't changed.

http://support.microsoft.com/kb/240363/en-us
markpalinuxCommented:


The technote says those items "are included" meaning that those items are included - you do not have to select anything other then system state. Once you select SystemState you are not able to select nor de-select the sub-items. (at least that is what I see, on both Windows 2000 and Windows 2003 DCs.)

Mark
TheCleanerCommented:
This is by design.  Best I can do is link you to here:  http://www.mcse.ms/archive44-2005-5-1639348.html

Just like you posted in your last post with :  http://support.microsoft.com/kb/240363/en-us

That's how you do it, hasn't changed in 2003.

Basically, like markpalinux said, you just select "System State".  The backup of a the C drive by itself will show a backup of SYSVOL without anything in it, which is why you NEED TO select "System State".

I believe it has something to do with the idea that the sysvol uses Junction Points and how those junction points are backed up.
jschwegAuthor Commented:
I'm beating a dead horse here, but... the statement below says that the components inside the system state can't be individually seleced, which means that it would be impossible to NOT backup the SYSVOL when choosing system state. So why then do they specifically mention the winnt/sysvol folder?

I'm probably looking WAY to far into this :)

Click to select the System State check box. (All of the components to be backed up are listed in the right pane. You cannot individually select each item.)

NOTE: During the system state backup, you must select to back up the Winnt\Sysvol folder. You must also select this option during the restore operation to have a working sysvol after the recovery.
TheCleanerCommented:
I will make the assumption this is because the System State backup is the components needed inside the SYSVOL folder, but the folder itself is NTFS, so you need to backup the folder and restore the folder so that the folder is in the correct location and with the right permissions during a System State restore.
TheCleanerCommented:
Thank you for the points!
jschwegAuthor Commented:
No problem. Sorry for the delay.
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 2003

From novice to tech pro — start learning today.