Thanks Del for posting this here, can't wait to get to work with the
'replicate' function in 6.3 and get FCM for VMware running in the lab over
here.
On Tue, Oct 11, 2011 at 10:53 PM, Del Hoobler wrote:
> If you haven't seen them yet, here are some announcements
> about Tivoli Storage Manager 6.
That AUDIT LIBRARY on the library client system worked! Thank you. This
is a hint to file away, as I'm sure this will come up again as we expand
our use of TSM library sharing. It would not have occurred to me to
try that, although it's the first thing the doc for AUDIT LIBRARY says.
Roger Deschne
Still don't have the network in place... going from a state agency in one city
to another state agency down the road a ways. As it usually the case, multiple
segments along the way I'm sure.
Should be able to do PING tests tomorrow.
-Origi
If you haven't seen them yet, here are some announcements
about Tivoli Storage Manager 6.3 and FlashCopy Manager 3.1.
Take a look:
Tivoli Storage Manager V6.3
-
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS211-372&appname=USN
Tivoli Storage FlashCopy
It's not just the bandwidth, if latency is high the backups will be dog
slow.
Whats the ping time to the host?
On 11 October 2011 21:08, Vandeventer, Harold [BS] <
harold.vandeven...@da.ks.gov> wrote:
> Thanks for the advice
>
> My only reason for considering compression is based on the fact
Hi,
Years ago there was some issue with installation cd's/dvd's bing left in the
drive and mounted, because their fs was normal ufs, they were backed up by TSM,
so exclude.fs /mnt/cdrom0/.../* or something was useful about 5 years ago when
I last had Solaris clients in my environment that were
Thanks for the advice
My only reason for considering compression is based on the fact this node is
about 60 miles away over a relativly slow link. I've asked the network team
what they expect for bandwidth, but don't have an answer yet.
Otherwise, I'd planned to leave the "Solaris" option
Welcome to the world of mixed operating systems..
Don't take this the wrong way but what does the OS have to do with things
like compressability? Compressability is based on your data. For
instance, I have dozens of Notes/Domino servers that are both Solaris AND
Windows. Domino databases do
Don't think its relavent now, but the only option I ever had to worry about for
solaris was
Exclude.filesystem /proc
I did just what you envision. Set up a solaris option set for use with those
clients.
Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310
-Or
I need to prepare my TSM environment (running on Windows) for it's first
Solaris client. All 400+ existing clients are Windows-based.
Anyone have suggestions for setting any specialized Option Set values?
My first thought is to have a "Solaris" option set, and leave most of it blank.
Probably
Yepp, but when I pass you on the freeway in my Porsche, your keychain wont be
much help ;)
Regards
Daniel
Daniel Sparrman
Exist i Stockholm AB
Växel: 08-754 98 00
Fax: 08-754 97 30
daniel.sparr...@exist.se
http://www.existgruppen.se
Posthusgatan 1 761 30 NORRTÄLJE
-"ADSM: Dist Stor Manag
Hehe, I wouldn't have to be seen with x86 hardware. I could still have a
power7 keychain if I wanted to.
Regards,
Shawn
Shawn Drew
Internet
daniel.sparr...@exist.se
Sent by: ADSM-L@VM.MARIST.EDU
10/08/2011 03:46 AM
Please respond to
ADSM-L
That would've been me ;)
Since this:
"Specifies the maximum number of parallel processes to use for moving data.
This parameter is optional. You can specify a value from 1–999, inclusive. The
default value is 1. Increasing the number of parallel processes should improve
throughput"
is mention
Am 11.10.2011 13:31, schrieb Richard Sims:
> The TSM documentation fails to say just how Maxprocess is honored in the Move
> Nodedata context. In other commands, such as Backup Stgpool, it is known
> that operation is by "clusters" - a non-grouped node or a collocation group
> of nodes. Wherea
The TSM documentation fails to say just how Maxprocess is honored in the Move
Nodedata context. In other commands, such as Backup Stgpool, it is known that
operation is by "clusters" - a non-grouped node or a collocation group of
nodes. Whereas your task involves a single node, it looks like y
Hi everybody,
after a long absence from this mailing list, I'm back (of course)
because I have a question about some TSM behavior.
We're currently running a TSM 6.2.1.0 on RedHat with (currently) 4 LTO
drives, of which DRIVE1 and 2 are LTO3, DRIVE3 and 4 are LTO4.
I have a BIGNODE for which I'd l
Ha, that's good to know Remco, i didn't know that! :-)
With disk based deduped backup solutions in hot demand it would be just a
matter of time before I would run into this.
I love this mailing list! :-D
On Mon, Oct 10, 2011 at 8:42 PM, Remco Post wrote:
> you may add or remove directories to
17 matches
Mail list logo
