Re: POLL: Backing up Windows Systemstate
Zoltan, I just checked my documentation, and have written down the following steps to get rid of VSS writer errors with TSM backups: 1. Stop WMI Services 2. Stop Volume Shadow Copy service 3. Stop Microsoft Software Shadow Copy Provider 4. Stop Cryptographic Services 5. Stop COM+ Event System 6. Start COM+ Event System 7. Start Cryptographic Services 8. Start Microsoft Software Shadow Copy Provider 9. Start Volume Shadow Copy service 10. Start WMI Services Please do check if you have any critical applications depending on these services, stopping some services might be disruptive to your applications. If I recall correctly, stoppping COM+ Event System also stops other services. Do not forget to check if you need to restart more services after starting COM+ service again. To see if you can do a System State backup, try one with the GUI client, it will tell you quite quickly if it can't run. It took me quite a while to figure this out, I hope this will be of help to you and your team. Cheers, Rick On Thu, Jan 9, 2014 at 8:07 PM, Zoltan Forray zfor...@vcu.edu wrote: Rick, Thanks for the offer and yes we would greatly appreciate if you can find your notes on how you fixed it.. Z On Thu, Jan 9, 2014 at 2:00 PM, Rick Harderwijk rick.harderw...@gmail.comwrote: Zoltan, We do succesfully do system state backups on Windows 2003 R2 and 2008 R2 servers. Why we do it? Simple: disaster recovery. Do we occasionally get problems? Yes, we do, and I do recall having an issue with a disappeared System Writer as well. I cannot recall exactly how I fixed it, it might have been something to do with COM+. If you want me to, I can have a look tomorrow, see if I can find documentation on that issue. Cheers, Rick On Thu, Jan 9, 2014 at 7:12 PM, Zoltan Forray zfor...@vcu.edu wrote: 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 zfor...@vcu.edu - 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 -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 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
Re: POLL: Backing up Windows Systemstate
We are backing up Systemstate on all Windows servers because of using TBMR for restoring system images in case of system crash. Sometimes it is painful due to big number of files, problems with VSS, etc. Problems with VSS are resolved by installing hot fixes or involving MS support. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: 09 01 2014 9:12 PM To: ADSM-L@VM.MARIST.EDU 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 zfor...@vcu.edu - 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 Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: POLL: Backing up Windows Systemstate
In our current environment, we've never had a requirement to restore a system state. However, there are engineers that requested the ability to have it available. Instead of using TSM's systemstate backup option, I've excluded it in the dsm.opt and use Microsoft's preferred and recommended method for backing up system state. If you haven't seen this before, this quote is good to note: When performing a VSS backup or restore, the Windows system state is defined as being a collection of several key operating system elements and their files. These elements should always be treated as a unit by backup and restore operations. What this means it is all or nothing when it comes to System State backups and restores. I found that using the built in Microsoft feature is the best, and most accurate method. (2008 Servers) I currently have it part of a scheduled job, but you can just as easily add it as a pre-task in the tsm client as well, this will allow the system state backup to be as close to the tsm disk backup. To enable it in Windows you need to add these Add these features: You will need to add under windows 2008 Features the Windows Server Backup Features which includes Windows Server Backup and Command Line Options. The actual backup commands go something like this :: Decide how many versions to keep Wbadmin delete systemstatebackup -backuptarget:E: -keepversions:1 -quiet :: Take a new system state backup wbadmin start systemstatebackup -backupTarget:d: -quiet The only catch is that is has to back up to a non OS drive. And it will take grow to approx. 12GB+ If you wish to restore a system state backup, you must first reboot the server into Directory Services Restore Mode (DSRM). Once in DSRM, you would open a command prompt with administrator rights and use the following commands to start the restore. C:\Users\adminWBADMIN GET VERSIONS Once we have located the version identifier, we can initiate the restore by using the following command: WBADMIN START SYSTEMSTATERECOVERY -version: version id Hope that helps, -Nick Also check out this Technical Exchange from IBM on the subject. http://www-01.ibm.com/support/docview.wss?uid=swg27023299 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Friday, January 10, 2014 3:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] POLL: Backing up Windows Systemstate We are backing up Systemstate on all Windows servers because of using TBMR for restoring system images in case of system crash. Sometimes it is painful due to big number of files, problems with VSS, etc. Problems with VSS are resolved by installing hot fixes or involving MS support. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: 09 01 2014 9:12 PM To: ADSM-L@VM.MARIST.EDU 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 zfor...@vcu.edu - 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 Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from
Re: POLL: Backing up Windows Systemstate
Thanks for the instructions. Although I'm not sure what simply starting and stopping things versus just rebooting the server would do. I am not the Windows person. I have passed this onto my Windows folks. Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 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 On Jan 10, 2014 3:24 AM, Rick Harderwijk rick.harderw...@gmail.com wrote: Zoltan, I just checked my documentation, and have written down the following steps to get rid of VSS writer errors with TSM backups: 1. Stop WMI Services 2. Stop Volume Shadow Copy service 3. Stop Microsoft Software Shadow Copy Provider 4. Stop Cryptographic Services 5. Stop COM+ Event System 6. Start COM+ Event System 7. Start Cryptographic Services 8. Start Microsoft Software Shadow Copy Provider 9. Start Volume Shadow Copy service 10. Start WMI Services Please do check if you have any critical applications depending on these services, stopping some services might be disruptive to your applications. If I recall correctly, stoppping COM+ Event System also stops other services. Do not forget to check if you need to restart more services after starting COM+ service again. To see if you can do a System State backup, try one with the GUI client, it will tell you quite quickly if it can't run. It took me quite a while to figure this out, I hope this will be of help to you and your team. Cheers, Rick On Thu, Jan 9, 2014 at 8:07 PM, Zoltan Forray zfor...@vcu.edu wrote: Rick, Thanks for the offer and yes we would greatly appreciate if you can find your notes on how you fixed it.. Z On Thu, Jan 9, 2014 at 2:00 PM, Rick Harderwijk rick.harderw...@gmail.comwrote: Zoltan, We do succesfully do system state backups on Windows 2003 R2 and 2008 R2 servers. Why we do it? Simple: disaster recovery. Do we occasionally get problems? Yes, we do, and I do recall having an issue with a disappeared System Writer as well. I cannot recall exactly how I fixed it, it might have been something to do with COM+. If you want me to, I can have a look tomorrow, see if I can find documentation on that issue. Cheers, Rick On Thu, Jan 9, 2014 at 7:12 PM, Zoltan Forray zfor...@vcu.edu wrote: 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 zfor...@vcu.edu - 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 -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 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
Re: POLL: Backing up Windows Systemstate
Zoltan, Sorry I'm late to the discussion. If none of the other things that people have mentioned here help, then consider engaging Microsoft support for assistance. When vssadmin list writers does not show the System Writer, then this is an OS issue not specific to any given backup product. Thus other products that use VSS to back up system state, such as WBADMIN (the Windows backup and recovery command line tool) will not be able to back up the system state either. Best regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2014-01-10 07:13:51: From: Zoltan Forray zfor...@vcu.edu To: ADSM-L@vm.marist.edu, Date: 2014-01-10 07:14 Subject: Re: POLL: Backing up Windows Systemstate Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Thanks for the instructions. Although I'm not sure what simply starting and stopping things versus just rebooting the server would do. I am not the Windows person. I have passed this onto my Windows folks. Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 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 On Jan 10, 2014 3:24 AM, Rick Harderwijk rick.harderw...@gmail.com wrote: Zoltan, I just checked my documentation, and have written down the following steps to get rid of VSS writer errors with TSM backups: 1. Stop WMI Services 2. Stop Volume Shadow Copy service 3. Stop Microsoft Software Shadow Copy Provider 4. Stop Cryptographic Services 5. Stop COM+ Event System 6. Start COM+ Event System 7. Start Cryptographic Services 8. Start Microsoft Software Shadow Copy Provider 9. Start Volume Shadow Copy service 10. Start WMI Services Please do check if you have any critical applications depending on these services, stopping some services might be disruptive to your applications. If I recall correctly, stoppping COM+ Event System also stops other services. Do not forget to check if you need to restart more services after starting COM+ service again. To see if you can do a System State backup, try one with the GUI client, it will tell you quite quickly if it can't run. It took me quite a while to figure this out, I hope this will be of help to you and your team. Cheers, Rick On Thu, Jan 9, 2014 at 8:07 PM, Zoltan Forray zfor...@vcu.edu wrote: Rick, Thanks for the offer and yes we would greatly appreciate if you can find your notes on how you fixed it.. Z On Thu, Jan 9, 2014 at 2:00 PM, Rick Harderwijk rick.harderw...@gmail.comwrote: Zoltan, We do succesfully do system state backups on Windows 2003 R2 and 2008 R2 servers. Why we do it? Simple: disaster recovery. Do we occasionally get problems? Yes, we do, and I do recall having an issue with a disappeared System Writer as well. I cannot recall exactly how I fixed it, it might have been something to do with COM+. If you want me to, I can have a look tomorrow, see if I can find documentation on that issue. Cheers, Rick On Thu, Jan 9, 2014 at 7:12 PM, Zoltan Forray zfor...@vcu.edu wrote: 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
Re: POLL: Backing up Windows Systemstate
Andy, As always, thanks for the response. I too suggested to the Windows person that she contact Microsoft for support. She tried a bunch of suggestions she found via Google (and from here) and system writer suddenly magically reappeared, not knowing what resolved it. I forwarded all of the suggestions/solutions/responses for her to save for the next such problem. To make matters worse, this is one of the Windows 2003 boxes where the 6.4.x client was installed before 6.4.x was patched to not allow installation on 2003 boxes, which of course means they are stuck since they can't go forwards with later 6.4.x patches/updates and don't want to uninstall/downlevel the client and re-backup everything (15M objects). There really should be some kind of workaround for these kinds of situations.. Thanks to everyone for all the responses. On Fri, Jan 10, 2014 at 11:07 AM, Andrew Raibeck stor...@us.ibm.com wrote: Zoltan, Sorry I'm late to the discussion. If none of the other things that people have mentioned here help, then consider engaging Microsoft support for assistance. When vssadmin list writers does not show the System Writer, then this is an OS issue not specific to any given backup product. Thus other products that use VSS to back up system state, such as WBADMIN (the Windows backup and recovery command line tool) will not be able to back up the system state either. Best regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2014-01-10 07:13:51: From: Zoltan Forray zfor...@vcu.edu To: ADSM-L@vm.marist.edu, Date: 2014-01-10 07:14 Subject: Re: POLL: Backing up Windows Systemstate Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Thanks for the instructions. Although I'm not sure what simply starting and stopping things versus just rebooting the server would do. I am not the Windows person. I have passed this onto my Windows folks. Zoltan Forray TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 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 On Jan 10, 2014 3:24 AM, Rick Harderwijk rick.harderw...@gmail.com wrote: Zoltan, I just checked my documentation, and have written down the following steps to get rid of VSS writer errors with TSM backups: 1. Stop WMI Services 2. Stop Volume Shadow Copy service 3. Stop Microsoft Software Shadow Copy Provider 4. Stop Cryptographic Services 5. Stop COM+ Event System 6. Start COM+ Event System 7. Start Cryptographic Services 8. Start Microsoft Software Shadow Copy Provider 9. Start Volume Shadow Copy service 10. Start WMI Services Please do check if you have any critical applications depending on these services, stopping some services might be disruptive to your applications. If I recall correctly, stoppping COM+ Event System also stops other services. Do not forget to check if you need to restart more services after starting COM+ service again. To see if you can do a System State backup, try one with the GUI client, it will tell you quite quickly if it can't run. It took me quite a while to figure this out, I hope this will be of help to you and your team. Cheers, Rick On Thu, Jan 9, 2014 at 8:07 PM, Zoltan Forray zfor...@vcu.edu wrote: Rick, Thanks for the offer and yes we would greatly appreciate if you can find your notes on how you fixed it.. Z On Thu, Jan 9, 2014 at 2:00 PM, Rick Harderwijk rick.harderw...@gmail.comwrote: Zoltan, We do succesfully do system state backups on Windows 2003 R2 and 2008 R2 servers. Why we do it? Simple: disaster recovery. Do we occasionally get problems? Yes, we do, and I do recall having an issue with a disappeared System Writer as well. I cannot recall exactly how I fixed it, it might have been something to do with COM+. If you want me to, I can have a look tomorrow, see if I can find documentation on that issue. Cheers, Rick
Re: POLL: Backing up Windows Systemstate
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:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, January 9, 2014 1:12 PM To: ADSM-L@VM.MARIST.EDU 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 zfor...@vcu.edu - 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.
Re: POLL: Backing up Windows Systemstate
We use TSMVE to do weeekly snapshots of just 'Hard Disk 1' on our ESX virtual machines. On Windows servers, that's the 'system disk'. When a total rebuild of a Windows server is required, a restore from the system disk snapshot is done rather than a file-level and systemstate restore from TSM Extended Edition. We have been advising admins of Windows servers not to backup systemstate to TSM Extended Edition because systemstate would be included in a snapshot restore. (It could be a week out of date.) Is our thinking correct about this, or are we overlooking something? Thank you, Keith Arbogast
Re: POLL: Backing up Windows Systemstate
Reading through the thread an am surprised at the number of people with problems. We backup about 2,000 windows servers from 2000 - 2008r2 and the system state backup (or one of the other names it goes by) rarely fail. We backup the system to allow a quicker restore of the system, without it the applications would have to be re-installed. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, January 09, 2014 12:12 PM To: ADSM-L@VM.MARIST.EDU 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 zfor...@vcu.edu - 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
Who might be running multiple V6 TSM instances on the same LPAR/system???
Would greatly appreciate any input/feedback on what to look out for, tips, hints, etc. in an AIX environment.
