On 6 nov 2009, at 19:53, Andrew Raibeck wrote:

It should be getting obvious to development that this architecture is
doomed, and not gonna work for folks in the long term.  Benefits we
pick

up

with the DB performance improvements in 6.1 (yes, it does run really

really

fast!), will be immediately swallowed up by Win2008 system state....

We want to make sure your TSM databases are fully utilized. :-)

This has never been a problem ;-) And even less so with large files in
a 6.1 dedup pool :P

Actually the first sentence above is spot on: We understand the
impact of
system state backup for Windows, especially post-Windows 2003 (Vista
and
up) and are actively seeking a solution. At this time I do not have
any
target timeframe for this, but we do consider it a high priority.

What we've been doing at SARA is that we only keep one version of the
systemstate backup, since (if I'm not misinformed), reverting back any
further would most likely be most undesirable. Also, for most domain
member systems, there is no use at all in backing up the system state,
since the only valuable data in there is the domain membership, and
that is easily recreated. That leaves only the AD servers that require
a systemstate backup. Of course, maybe you'd want multiple versions of
your user database....

Best regards,

Andy

--
Met vriendelijke groeten,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622