Hi tsmblogger!
In the end of the article, you say "you can include the
-testflags=DISABLEATTRIBUPDATE parameter in a client option set with
FORCE=YES"
Can you tell us the "def clientopt" command to do that?
Regards,
Shawn
PS Great site by the way!
________________________________________________
Shawn Drew
Internet
info AT TSMBLOG DOT ORG
Sent by: ADSM-L AT VM.MARIST DOT EDU
08/25/2008 06:26 PM
Please respond to
ADSM-L AT VM.MARIST DOT EDU
To
ADSM-L
cc
Subject
[ADSM-L] Updated VS Backed Up
The DISABLEATTRIBUPDATE client parameter can be utilized to force the
resend
of a file of which a file system object (for example, file permissions)
were
changed. This is described here:
<
http://tsmblog.org/serendipity/index.php?/archives/101-UPDATED-vs-BACKED-UP
-revisited-how-to-use-DISABLEATTRIBUPDATE-to-force-the-resend-of-a-changed-f
ile-on-AIX.html>
http://tsmblog.org/serendipity/index.php?/archives/101-UPDATED-vs-BACKED-UP-
revisited-how-to-use-DISABLEATTRIBUPDATE-to-force-the-resend-of-a-changed-fi
le-on-AIX.html
An extract of the article:
As a matter of fact, this can be done. But it is not stated in the IBM
documentation, nor in the IBM KB.
----> The permissions of a file are changed:
tsm@face:/home/tsm $ chmod 755 testfile
----> The file is backed up incremental with this parameter:
tsm@face:/home/tsm $ dsmc i -testflags=DISABLEATTRIBUPDATE testfile
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
Client Version 5, Release 4, Level 0.0
Client date/time: 08/25/08 09:19:50
(c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights
Reserved.
Node Name: FACE_TSMCL
Session established with server HANNIBAL: AIX-RS/6000
Server Version 5, Release 4, Level 1.0
Server date/time: 08/25/08 09:19:50 Last access: 08/25/08 09:18:57
Incremental backup of volume 'testfile'
Successful incremental backup of '/home/tsm/testfile'
Total number of objects inspected: 6
Total number of objects backed up: 1
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of bytes transferred: 37 B
Data transfer time: 0.00 sec
Network data transfer rate: 76.22 KB/sec
Aggregate data transfer rate: 0.01 KB/sec
Objects compressed by: 0%
Elapsed processing time: 00:00:02
tsm@face:/home/tsm $
Shell will time out in 60 seconds.
ksh: Timed out waiting for input.
The file is 'backed up' (instead of 'updated'). By using the
-testflags=DISABLEATTRIBUPDATE parameter you're telling the TSM client to
resend the file, instead of updating it. This is what you want; the
previous
version became INACTIVE, and the last one - with the new permission - the
ACTIVE one. Now the behaviour it the same as a Windows Client, which is
not
too bad in this case.
When you want this to work for all your AIX clients, you can include the
-testflags=DISABLEATTRIBUPDATE parameter in a client option set with
FORCE=YES, or add it as a client option to the schedule for your clients.
Hopefully, in a next release of the TSM Client the
-testflags=DISABLEATTRIBUPDATE parameter will become an normal, documented
and supported parameter. It would be nice to have in dsm.sys, for example,
a
client option 'DISABLEATTRIBUPDATE YES'.
This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
|
