I also use Windows Backup for system state backups and let TSM pick up the files. You can fool Windows into using a local disk by creating a share and using the share name. I haven't tried it with 2012 but it works fine in 2008.
From: "Storer, Raymond" <[email protected]> To: [email protected] Date: 01/10/2014 09:10 AM Subject: Re: POLL: Backing up Windows Systemstate Sent by: "ADSM: Dist Stor Manager" <[email protected]> Zoltan, I prefer to use the built-in Windows Backup for System State backups and then let TSM backup the files to tape during the normal file system backups. In this way, I know I have a Microsoft supported recovery mechanism if I need it. Nowadays, with the advent of virtualization, there are very few instances where a server actually needs a system state backup. Off the top of my head, I would recommend it for a couple of scenarios for maximum support from Microsoft in case of a restore: - Windows Domain Controller with global catalog - Enterprise Windows Certificate Authority server If you have Domain Controllers with a global catalog at several remote sites perhaps you'll decide you don't need a system state backup of any of your Domain Controllers. I do have them, and I still perform a system state backup of one of them. If you choose not to do system state backups you probably should consider a remote site for "delayed replication"--just in case you need your Active Directory to "go back in time". Ray Storer NIBCO INC. 574.295.3457 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Zoltan Forray Sent: Thursday, January 9, 2014 1:12 PM To: [email protected] Subject: [ADSM-L] POLL: Backing up Windows Systemstate A question about backing up systemstate, which seems to give us numerous headaches. Do you backup systemsstate on your Windows servers and WHY? My Windows folks constantly contact me about errors backup up and getting failures related to the systemstate files/process or VSS. For example, today's headache is a 2008 box failing with *"System Writers 'system writer' do not exist * and yes, doing a "vssadmin list writers" does not list "system writers". They have been fighting this since November, with no solution to fixing this problem. All hits/suggested solutions from Google searches have been tried, to no avail. I don't thing the server owners are willing to do a complete rebuild. The simple solution would be to NOT backups systemstate. For a simple 2008 server, what do we lose by not backing up systemstate? -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html ________________________________ CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
