Thank you all for the information thus far.
Can any of you provide real world backup times for full tree traversal backups
to TSM using NDMP? I understand my mileage may vary depending on the data and
it's size as well as the hardware configuration but there must be a fairly
standard
This may be a bit off topic but consider this a thread bump
We have about 25TB worth of unstructured data spread across seven windows
servers using DFS. We are using TSM with a monthly image backup as well as
daily journal based backups to collect the data but I'm concerned about restore
We are using an IBM3584 and don't use any kind of collocation. We have found
the migration process from diskpool to tape collocates data by node and
therefore already does a decent job of grouping node data together.
The only time you may see better performance with collocation is with a
Can a normal incremental job run and complete?
If you can run a normal backup then uninstall and reinstall the journal.
If not see if you can run a Windows Backup. If the WB fails then its an OS
problem and not related to TSM.
Okay I can see how that would help keep tabs on whats going where.
Though it does seem odd that you would need more than a handful of retentions
especially defaults.
+--
|This was sent by [EMAIL PROTECTED] via Backup
Why not use the managment class to set retention?
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--
Our CDL is configured for 50GB tapes and 20% reclaim.
In the big sceme of things it doesn't cost us anything. We've been running
like this with about 1000 nodes for three years and haven't had any recl
problems.
We have had CDL fail overs and during those times we set it at 100.
Hmmm I'm not sure about that.
I have only a standard active domain. I do have serveral mgmt classes for
various types of data and various retention requiresments.
A default for 99% of the nodes. then Exchange, SQl, 7_year, 1_year, and
even a No_Limit.
A simple select statement
We have about 300 VMs and back them up via installed client just like any other
physical server.
I've reviewed the V5.5 code and mass proxy backup option but it doesn't seem to
offer enough to warrant new procedures, testing, and configuration changes.
In the event of a large disaster our
I have about 1000 servers with V5.3.4.2 installed on them. I would like to
bring them up to the supported V5.5.0.6 level but I don't want to visit each
one.
I'm not all that handy with scripting or SMS so some hand holding or even an
example script would be greatly appreciated.
I've spent a
10 matches
Mail list logo
