I thought I'd throw this out there for ideas since I'm just being exposed to
NAS backpus and restores. I believe I got a previous post yesterday figured out
and was finally able to move on to testing a restore. Now I'm getting a
different error but I'm a bit confused as to why. I went through lo
Argh. While I'm glad to know it's not just me, your situation sounds bad. Maybe
it will be fixed in 6.4, coming soon.
Steve
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Neil
Schofield
Sent: Thursday, October 11, 2012 2:20 PM
To: ADSM-L@VM.M
Steve
Yes, we've noticed the same and it's a right pain.
The TSM for VE incremental backup processing need to read the CTL files
stored during previous backups. We store these on primary disk on the TSM
server and back them up to copy storage pools on tape (not collocated).
The VM proxy servers a
Those two lines were the only thing in the dsmj.log file.
--
Brian Kunst
Storage Administrator
Large Scale Storage & Systems
UW Information Technology
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
> Of Zoltan Forray
> Sent: Thursday, October
I noticed on my Operational Reporter that the TSM4VE datamover does a small
amount of RESTORE activity whenever it runs backups. Sure enough, that's what
the TSM SUMMARY table claims. Has anyone else seen this?
Steve
STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) |
stephen.stackw...@
"Size of node" can be misleading. Number of objects (sum of files,
subdirectories, symlinks) is more important than sheer quantity of data.
This is what takes up space in the database. We've got nodes with huge
quantities of data in a relatively small number of files, which are no
problem for TSM.
Excellent advice Zoltan we, too, are in storage occupancy license status.
My consolidation effort is partly driven by the fact the TSM 5.5 servers need
to be replaced due to "age" issues and purchasing a pile of NEW hardware
doesn't fit the budget very well. Thus, the push from mgmt to "con
Anything in your dsmj.log file?
On Wed, Oct 10, 2012 at 1:15 PM, Brian G. Kunst wrote:
> IMBase(Constructor)
--
*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 -
Server is RH Linux 6.2.4.000 (yes, I am aware of the 6.2.4.200 patch but
nothing in the readme/descriptions address anything similar/related).
Client is W2K3 6.3.0.18 client
These errors are becoming a nightly problem. From the server side:
10/11/2012 2:03:48 AM ANR0106E imbkqry.c(1358): Unexpe
You can also license TSM by storage occupancy, which is what we have done,
for 99.9% of our nodes. Our departments "bean counter" determined it came
out cheaper,
We run 7-TSM servers (Red Hat Linux) for 600-nodes with total occupancy (as
of this email) of *1.1PB* and *1.4B objects.*
I define/shif
Harold
Given that TSM is licenced by client and not by server is there really
any need to consolidate? You won't be running as many boxes but in the
greater scheme of things that won't make a lot of difference.
Sure when you replace your hardware you can consolidate. Use Butterfly
to do the con
11 matches
Mail list logo
