It sounds like you're trying to backup to a disk pool, which is supposed to
work with 5.4 and above with Netapp/Nseries and Celerra.
In our case, the TSM server is Linux RH4, V5.4, to SAN attached 3584 with LTO3
drives.
I couldn't get it to work with BlueArc, and I went down the path with their
I think just about every one of my customers is using somewhat different
criteria to decide, depending on
- what particular circumstance they are concerned about,
- what laws apply to their industry, if any
- who is involved in the discussion (tecchies or lawyers or compliance
officers
Yep, assuming your target TSM server has a compatible drive.
EXPORT NODE blah "look up the applicable parameters" devclass=tapedevclass
Will take the .9 TB of data backed up to TSM and put it in a portable format
on n tapes.
You then enter an IMPORT NODE command to load it into the DB and storag
Currently I am migrating servers for a customer. In all instances but one I
am using a combination of mksysb and sysback on uservgs to do this.
One node has .9TB of data, however and would take too long using sysback.
Someone has suggested using TSM. Can the client node be exported to tape and
i
Applicable state and federal laws largely determine the disposability
of media, as previously explored in threads such as
http://www.mail-archive.com/adsm-l@vm.marist.edu/msg74957.html
If media is kept in a secured facility, then the issue is moot, as no
unauthorized persons will gain access to t
When do you-all deem a file / message / whatever "unrecoverable" ?
What legal standards do you bring to the process of deciding what's
discoverable and what's not?
I've got some sentiment on the UF campus that anything which could be
retrieved by a data-recovery house should be deemed not deleted.
I'm trying to get NDMP backups working for a client of ours. This is
my first time playing with NDMP, so I may just be doing something
completely wrong.
What we've got:
TSM 5.4.1.2 on Linux, 3584 library with 4x 3592 drives.
Client has a BlueARC NAS device we're trying to get backed up via NDMP
u
Wow! Quite a setup. I've worked on a couple of engagements with 24 x 3592
tape drives, but 72 drives, 1900 paths, and 200 stg agents must be interesting,
to say the least.
Off the top of my head:
Advantages: 1 scratch pool, "lazy man's load balancing", with all TSM clients
accessing all dri
Throw a dart at the list of Fortune 500, and you'll have better than a 50-50
chance that they use TSM, especially the financials for D/R.
Accounts I know about are: Walmart, AT&T, State Farm, American Express, Mellon
Bank and of course, IBM.
- Original Message -
From: goc <[EMAIL PRO
In fact, on AIX at least, I don't believe you _can_ define multiple
TSM paths to an Atape-based drive. If you try, TSM gives an error.
I suspect that would be the case on other platforms and tape drivers,
as well. The TSM concept of "path" isn't concerned with the physical
link topology used for
Yes, we only define one path per drive. We are NOT defining paths for
every rmt device. So, each library client has 72 drives defined to it,
with mulit-pathing, and we only define a path for one of the rmt devices.
Same holds true for all storage agents as well.
Sean English
"Strand, Neil
If you are using Atape on AIX only the primary path needs to be defined
IF you have enabled alternate pathing.
"chdev -l rmt5 -aalt_pathing=yes"
See IBM "IBM Tape Device Drivers Installation and User's Guide" PG 31,
Pub GC27-2130-02
It works like a champ on AIX. Can't vouch for other platforms.
And how many TSM admins? How many tape/library alerts/pages a night?!?!?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Sean English
Sent: Wednesday, February 06, 2008 4:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Question on TSM environment si
Does one need to define all the drive paths for multipath tape drives?
Or does one only need to define one path and the OS will use the other
paths as needed?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Strand, Neil B.
Sent: Wednesday, February
Oh, something I meant to mention before. If you can NFS mount a
directory, either on the new server, or another Linux Server, you can do
a DB Backup to that, and then mount it on the new server instead of TAPE
(easier to keep up with). What's interesting is that you can use
(depending on your DB
And, if you want the move to be seamless on the client end change the IP
address and host name on the new box to match the old box (this is what
I've done). This will enable you to skip step 5 below. However I must
add that before you run a DB Backup after step 1, empty out your
diskpools and rem
We're a smaller site --
2 frame 3584 with 16 drives (10 LTO4 & 6 LTO2)
64 drive paths
200 LTO4 & 390 LTO2 tapes
1 TSM server at 5.5.0.0
Back up approx. 3 TB per night, copy 2.4 TB to go offsite (the entire
5.4 TB processed between 18:30 and 06:00)
Tom Kauffman
NIBCO, Inc
-Original Message---
Micron Technology. Employs about 15,000 worldwide, has multiple TSM
servers in Idaho, Virginia, California, Italy, Japan, Singapore, Puerto
Rico, China & UK.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
goc
Sent: Thursday, February 07, 2008 6:33
hi, for presentation purposes can someone tell me which BIG companies
are using TSM as their B/A solution, for example big companies with
more than 5000 employees and big money and stuff :-)
i admit this is a strange question but of course i cannot find any
answers on the web
thanks in advance
So far quite well, but you have to have a large MAN ring, (cant remember
the size) but we are using 12Gbs FCIP Link dedicated for the FC Tape
drives, our biggest challenge offsite tape library stability.
The beauty of TSM is its flexible, you could also use Virtual Volumes
(assuming your using the
20 matches
Mail list logo
