Dear Zoltan,
there is no need to net use the UNC shares. Just define the share in the
domain statement and in the objects field in the schedule. Don´t forget to
exclude the paths for snapshots! The TSM scheduler must run on an account
with priviledges of backup operator and manage security logs,
Hi Del,
I'd like to echo that appreciation as well.
Many thanks.
Ruth S. Mitchell
Oxford University Computing Services
www.oucs.ox.ac.uk/hfs
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Prather, Wanda
Sent: 07 June 2010 17:28
To:
Hi Timothy,
Right or wrong this works for us:
1. Create a TSM Node for every Cluster volume
2. Define a different webport for each ie. 1582, 1583 etc
3. We copied the dsmcad.nlm file to dsmcad1.nlm and dsmcad2.nlm so we
could run unique instances of the client that can get unloaded when the
Thanks for the confirmation.
From:
Prather, Wanda wprat...@icfi.com
To:
ADSM-L@VM.MARIST.EDU
Date:
06/07/2010 11:10 AM
Subject:
Re: [ADSM-L] EMC Celerra CIFS backups
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Got multiple customers doing that.
Domain all-local
Domain
Thanks for the info and guidance...
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
Hi to all
I implant today the new TDP for Microsoft Exchange server 2010 version 6.1.2.0
on an OS Windows server 2008 R2 Enterprise 64Bit, succeed to install and
configure correctly with the new configuration like:
Grant proxynode and new VSS feature (running by the TSM client).
My
Robert,
For VSS backups, the Windows BA Client performs the data transfer.
You must configure the Windows BA Client options file,
(more specifically, the option file for the TSM Remote Client Agent aka
DSMAGENT)
for LANFREE communications.
Thanks,
Del
Hi Del
Thanks for the reply .. I already add the option lines to enable lanfree in the
dsm.opt client (by the way did I need those lines in the dsm.opt on the TDP
side )
But got the error:
Unable to obtain model type for '\\.\Tape4', rc = 46
I think is a driver problem, I install
Robert,
Please read my response carefully again.
It is NOT the DP/Exchange options file that you need to update.
You need to configure the options file for the TSM Remote Client Agent.
Thanks,
Del
ADSM: Dist Stor Manager
Hello
If you use more than one session for backup Domino you can update TDP
to version 5.5.3.0 which resolve very similar problem (and many
others).
--
Efim
Yep ... it's what I did I configure the option file for the Tsm remote client
agent with the enable feature and delete those line for the TDP option.
But still got the error
Thanks Robert
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Del
Is this OES or Netware based cluster?
--
Warm regards,
Michael Green
On Mon, Jun 7, 2010 at 10:57 PM, Timothy Hughes
timothy.hug...@oit.state.nj.us wrote:
Novell cluster
I am trying (attempting) to configure the novell cluster to the client
wants to backup just the cluster according to
We have just purchased a bunch of 3592JB tapes (700GB uncompressed capacity) to
use for some large NDMP backups. My first test last night backing up around
1.8TB of data completely filled two of these tapes. This is only marginally
better than what I was getting on the 3592JA tapes which are
Which drive wrote the initial label?
From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Sheppard, Sam
[sshepp...@sddpc.org]
Sent: Tuesday, June 08, 2010 1:20 PM
To: ADSM-L@vm.marist.edu
Subject: [ADSM-L] 3592JB tapes
We have just purchased
These were labeled in the only drive type we have, TS1120 (3592-E05).
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Fred
Johanson
Sent: Tuesday, June 08, 2010 11:27 AM
To:
Had a similar thing with 3590-e01 and tsm 5.4.2. Had to create a new devclass
specifying compressed. Pain in the rear.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On
As I understood the explanation when we had a similar problem, those volumes
labeled on the E05 would write at that density. If I understood correctly,
what you see looks normal.
From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Sheppard,
What kind of data is it?
How many tape does the data fit on when using the 300gb tapes?
(trying to get some idea of what to expect for compression)
I thought a 3592JA tape was 500gb when used in a 3592-e05.
Sheppard, Sam
sshepp...@sddpc.
ORG
Did they by chance come pre-labeled? This happened to us once -
pre-labeled tapes came labeled wrong and we had to relabel them.
Rick
Fred Johanson
f...@uchicago.ed
U To
Sent by:
What I'm seeing is the JB tapes don't seem to be holding any more data than the
JA tapes, even though their capacity should be twice as much. I've updated the
device class to specify FORMAT=3592-2C and now I'm running a move data to see
what will happen.
Sam Sheppard
San Diego Data Processing
We entered them into the library using the LABEL command with the CHECKIN
option, so they should be labeled correctly.
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Hi Robert,
As far as error:
Unable to obtain model type for '\\.\Tape4', rc = 46
This is not my area of expertise... if the ADSM-L community cannot help,
please open a call with IBM support.
Thanks,
Del
ADSM: Dist Stor Manager
You're right. I believe the 300GB number is for the older J1A drives. Our JA
tapes should be 500GB uncompressed and we're seeing anywhere from 800GB to
1.4T(TDP backups) compressed. I'm not sure, but for this NDMP data, it looks
like the JA tapes were getting around 700GB and the JB are getting
Hi Micheal, Thanks just found out more information
I believe it's a Netware based Cluster the first three consist of
NetWare 6.5 SP8, the fourth server is Suse Linux 10. The Suse Linux
server is (Virtual Server)
administer a Novell Clustered Environment, with multiple resources
running on each
What kind of data? We are getting 750GB - 1.2TB on each tape. The compression
is similar to what the original file servers got when they wrote to a different
library and different drives.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On
Well, I've done this in OES env only. Our setup on OES seems to be
very is similar to what the prev poster has described for Netware.
--
Warm regards,
Michael Green
On Tue, Jun 8, 2010 at 10:20 PM, Timothy Hughes
timothy.hug...@oit.state.nj.us wrote:
Hi Micheal, Thanks just found out more
It's windows file and print data. Looks like our results are similar to yours.
Coming from the original servers to JA tapes, we were getting between 575 and
675GB per tape. So far on the JBs coming from CIFS, it looks like 820 to 900GB
per tape. I think my main problem was I was using the
27 matches
Mail list logo
