Hi David
My favourite way to restart on AIX (ksh) is
chitab $(lsitab autosrvr | sed -e "s/once/respawn/")
and then after it has started
chitab $(lsitab autosrvr | sed -e "s/respawn/once/")
but one site I worked the guy who had set up TSM was a serious AIX nerd -
CATE and all that - and had
Hi Curtis,
Unfortunately, this was already the case when I came, client encryption is the
only option and the tapes are needed to be sent to offsite.
I think we need to consider this - enabling/disabling client encryption and see
how - in the test case on the upcoming POC with a de-dupe vendor.
James R Owen wrote:
>
> I'm also looking for advice: how best to make an inoperative AUTOSRVR
> entry in /etc/inittab? We leave the tiny default TSM service in the
> installation directory for upgrade processing, and never want it to
> start up automatically, but the upgrade process recreates the
>> On Wed, 23 Jan 2008 13:36:55 -0600, Howard Coles <[EMAIL PROTECTED]> said:
> I have an interesting query:
> We're going to be upgrading to TSM 5.5 (hopefully unless serious
> problems are revealed) in the near future, and then adding a secondary
> server to offload some of the backups, restores
Folks:
Our group has been approached by a customer who asked if we could
backup/archive 50 petabytes of data. And yes, they are serious.
We've begun building questions for the customer, but as this is roughly 1000
times the current amount of data we backup, we are
on unfamiliar turf here.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
James R Owen
Sent: Wednesday, January 23, 2008 1:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Upgrading TSM on an AIX server running multiple
TSM instances
Orville,
Can you clarify exactly wha
I've been on ADSM.ORG for some time, just not on the list.
I have an interesting query:
We're going to be upgrading to TSM 5.5 (hopefully unless serious
problems are revealed) in the near future, and then adding a secondary
server to offload some of the backups, restores, and admin processes
etc.
Orville,
Can you clarify exactly what is the problem with multiple TSM service instances
running from a shared dsmserv binary? AFAIK, IBM/Tivoli does not suggest to
copy and run a separate executable for each TSM instance. We have not seen any
problems sharing the same executable among sever
The other posters are correct. You will get 1:1. Dedupe works by
finding patterns. There are no patterns in encrypted data.
One question would be why would you do that? Most people are encrypting
data as it leaves their site. The best way to do that is hardware
encryption (tape drive or SAN-
Hmm, I was going to say I'd expect almost none, because the eencryption
wouldn't generate the same data each time through.
But maybe It depends on encyption scheme, on how keys are managed (I would
expect the same data to encrypt the same way if the same keys are used -
although I am no cryptologi
True as well as any files that are already "Compressed" We have SQL DB's
doing Flat File Dumps to Disk with compression and we see 1.7:1 Ick.
Also TDP RMAN backups can use Files per set function which if set to
more than 1 RMAN will "multiplex" each file set differently so you see
different da
The reason to have separate binaries for each instance is that the process in
AIX is tied to the binary file and holds it open.
Orville L. Lantto
From: ADSM: Dist Stor Manager on behalf of Loon, E.J. van - SPLXM
Sent: Tue 1/22/2008 02:55
To: ADSM-L@VM.MARIST.ED
I agree about client encryption wrecking dedup ratios.
FWIW however, if you turn on both COMPRESSION and ENCRYPTION on the client,
the client is also smart enough to compress first, then encrypt, so you get
the compression benefits.
However, that of course takes a lot of cycles on the client, and
You are right, if client compression is turned on, you will get next to
no compression.
In the DataDomain best practices for TSM documentation, they say
to have client compression turned off for the DD appliance to do its
thing.
We don't have client compression turned on because w
Oooh, what a great question!
I'd guess if client encryption is on and working, the dedup ratio should be
about 1:1; because the data should never encrypt the same way twice.
On 1/23/08, lamont <[EMAIL PROTECTED]> wrote:
>
> Hi,
> What would likely be the de-dupe ratio if tsm clients do archive
>
Encryption might have a DRAMATIC effect, completely eliminating the
benefits of either deduplication or compression. I predict 1:1. i.e. NO
savings for dedupliaction, with TSM client encryption.
This is why encryption at the tape drive is a very popular option with
LTO4. You can both encrypt and c
thanks,
I'll follow that up, post how it goes.
Matt.
Internet
[EMAIL PROTECTED]
To
ADSM-L
Sent
As with all questions like this, the answer is "it depends".
It depends on the make-up of your data (# of DB full dumps, % of DB
dumps to filesystem data, % of change on the client, etc)
It depends on the vendor of DeDupe you are using.
FWIW, I am about to replace a 100TB of LTO tape with a Data
Hi, Matthew -
I haven't run into that before, but my guess would be that the TSM
client is having trouble identifying the peer, probably because the
10.x.x.x private net address is not DNS reverse-lookupable into a
host/node name. TSM 5.2 changed IP address handling a bit, in
concert with the DN
Hi *SM'ers,
A customer has recently upgraded client versions on AIX machines running
AIX 4.3 and 5.3.
TSM server is v5.3.2 on z/OS 1.7
After upgrading the AIX 5.3 servers to the TSM 5.4.1 or 5.5 client, trying
to logon to the client using the web interface gives;
ANS2622S Invalid ID or Pass
Paul,
If you need to restore from the new node name, you would launch
the CLI or GUI specifying the alternate options file name.
For example, in the example below:
GUI: TDPSQL /TSMOPTFILE=DSMARCH.OPT
CLI: TDPSQLC RESTORE dbname full /TSMOPTFILE=DSMARCH.OPT
This will tell Data Protection for
On Jan 23, 2008, at 4:28 AM, Angus Macdonald wrote:
So I'm right to think the "dsmc delete backup" command will remove
the TSM backup files and leave the archived copies alone?
Yes.
So I'm right to think the "dsmc delete backup" command will remove the TSM
backup files and leave the archived copies alone?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Richard Sims
Sent: 22 January 2008 23:56
To: ADSM-L@VM.MARIST.EDU
Subject: Re:
Hi,
What would likely be the de-dupe ratio if tsm clients do archive processing
daily (file level, no tdps) with encryption enabled?
Thanks.
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PRO
24 matches
Mail list logo
