As opposed to full backups, what files should I backup on Windows Server?

Question

I am partly responsible for the uptime of a Windows Server at work. We have only been assigned a small amount of space for backups (50gb or so). This is no way near enough space for backing up .VHDs of the actual server. Instead, the sysadmin says we should just back up important files. I am not sure if he means important system or user files, but either way, this is not really a robust backup strategy. No strategy in terms of media rotation, etc, nothing. I see no value in this - at all.

The server is AD/DNS server, so it has some special considerations. Also, how should I backup AD when there is also a secondary AD on a VM on ESX?

Note: I am a developer but for various reasons (skills gaps, politics), I have the majority of responsibility for doing these sysadmin tasks. I don't mind as I learn a lot, but I have very little support from other people (the sysadmins are very unapproachable so I rely on SE and my trusty books). I am like a semi-professinal system admin and I am an experienced developer. Because I run HyperV at home, this gives me some basic grounding in system administration for Windows Server, thus I am the favourite for all of this.

Thanks

Thanks

Answer 1

It sounds like you are doing the backups to some small part of a hard drive, possibly a shared drive. That's not a backup, it's a disaster waiting to bite you where it hurts.

You really should be looking at a proper backup system. i.e. Something that will backup everything you need and allow you to take that away from the thing being backed up, with my preference always being tape. If the company can't or won't pay for such a system at least try to convince them to let you buy a couple of external hard drives for the purpose (rotating them and not relying on any one copy). While I abhor hard drives for backup they are a whole lot better than nothing and if they are external you can at least meet the requirement to separate them from the source.

Above all else, test your backups, regardless of what method to choose to do them.

Answer 2

Is the server in question a production server? Is it in fact one of the AD\DNS servers for the company? If so, I find it highly irregular that the sysadmins would have so little concern for it. If that's the case then I have to say that personally, I find it shameful that you're in the position they've left you in.

At the very least, if you have no other recourse, find a way to perform a daily System State backup.

All that being said, if your AD DNS zone(s) are AD integrated and if both servers are also GC's, and this server is not the single point of failure for any other service or application, then technically you could tolerate the failure of this server. You could simply sieze the FSMO roles if neccessary, build a new DC, and be happily on your way.