Good morning!
TSM Server 6.3.3.0
TSM Client 6.4.0.0 running on Windows 2008 R2 Standard SP1 64bit
So, we're finally transitioning from Windows 2003 to Windows 2008 in my shop. Historically, I've excluded SystemState on the vast majority of my servers unless there was a specific need for it (It's bloated, slow and prone to recurring failures). I continued this practice on Windows 2008, but ran into a well-known "feature" where executables that run as Services may only be backed up as part of SystemState. They're not even selectable for a file-system backup. I'm sure this is well known to most of you, but I'm a few years behind on this one. :D
I tested recovery of these files by performing a SystemState restore on a test box. It restored the missing files successfully, but it also required a reboot.
If a single executable file is corrupted or missing on a system, are people restoring SystemState (including a reboot!) to get the single file back? Or are you referring your customers to their install media to restore the file?
I found an article describing how to retrieve a single file from SystemState on the CLI. Very useful info, but it seems a bit onerous as a work-around.
http://www.tsmblog.org/step-by-step-...nate-location/
I also found a thread on this issue from way back in 2009 that showed an option that can be used to skip these system excludes: "TESTFLAG SKIPSYSTEMEXCLUDE"
I tested it, and it works wonderfully. Files may be successfully backed up at the filesystem level. However, as "purdon" points out in the following thread, it's probably not a defensible practice to use a "TESTFLAG" option in production.
http://adsm.org/forum/showthread.php...er-2008-backup
So what are you guys doing?
1.) Total SystemState restore to recover a single file (followed by a reboot)
2.) Referring your customers to their install media to recover the missing/corrupted file(s)
3.) Using an option like "TESTFLAG SKIPSYSTEMEXCLUDE" to bypass this issue altogether
Thanks!
TSM Server 6.3.3.0
TSM Client 6.4.0.0 running on Windows 2008 R2 Standard SP1 64bit
So, we're finally transitioning from Windows 2003 to Windows 2008 in my shop. Historically, I've excluded SystemState on the vast majority of my servers unless there was a specific need for it (It's bloated, slow and prone to recurring failures). I continued this practice on Windows 2008, but ran into a well-known "feature" where executables that run as Services may only be backed up as part of SystemState. They're not even selectable for a file-system backup. I'm sure this is well known to most of you, but I'm a few years behind on this one. :D
I tested recovery of these files by performing a SystemState restore on a test box. It restored the missing files successfully, but it also required a reboot.
If a single executable file is corrupted or missing on a system, are people restoring SystemState (including a reboot!) to get the single file back? Or are you referring your customers to their install media to restore the file?
I found an article describing how to retrieve a single file from SystemState on the CLI. Very useful info, but it seems a bit onerous as a work-around.
http://www.tsmblog.org/step-by-step-...nate-location/
I also found a thread on this issue from way back in 2009 that showed an option that can be used to skip these system excludes: "TESTFLAG SKIPSYSTEMEXCLUDE"
I tested it, and it works wonderfully. Files may be successfully backed up at the filesystem level. However, as "purdon" points out in the following thread, it's probably not a defensible practice to use a "TESTFLAG" option in production.
http://adsm.org/forum/showthread.php...er-2008-backup
So what are you guys doing?
1.) Total SystemState restore to recover a single file (followed by a reboot)
2.) Referring your customers to their install media to recover the missing/corrupted file(s)
3.) Using an option like "TESTFLAG SKIPSYSTEMEXCLUDE" to bypass this issue altogether
Thanks!