I do not mean to be disagreeable, but my testing has indicated that you
cannot exclude a drive in Windows with an exclude or exclude.dir
command. I use the domain -z: and that works.
This may also have to do with versions and other stuff.
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Michal Mertl
Sent: Friday, April 28, 2006 2:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] dsm.opt not fully effective for server induced
backups
Thanks for the fast answer.
Andrew Raibeck wrote:
> As with any issue like this, it would help to see the detail, such as
the
> specific logs you are looking at, options file, server-side client
option
> set (if you have it), etc.
Here are some more details:
BA Client version 5.1.5.0
dsm.opt:
-------
COMMMETHOD TCPIP
NODENAME S-EU-VIE01DB01
TCPServeraddress s-at-vie-prdb
TCPPORT 1500
TCPBUFFSIZE 512
TCPNODELAY NO
TCPWINDOWSIZE 512
TXNBYTELIMIT 2097152
*TXNBYTELIMIT 20480
MEMORYEFFICIENTBACKUP NO
LARGECOMMBUFFERS YES
USEUNICODEFILENAME YES
COMPRESSION NO
SUBDIR YES
REPLACE ALL
SCHEDMODE PROMPTED
SCHEDLOGNAME "C:\Program Files\Tivoli\Tsm\TSMSched.log"
ERRORLOGNAME "C:\Program Files\Tivoli\Tsm\TSMError.log"
SCHEDLOGRETENTION 14 D
ERRORLOGRETENTION 14 D
LANGUAGE AMENG
PASSWORDACCESS GENERATE
DATEFORMAT 4
NUMBERFORMAT 5
QUIET
BACKUPREGISTRY YES
DOMAIN all-local
EXCLUDE "*:\_inst\...\*"
EXCLUDE "*:\_inst\...\*.*"
EXCLUDE "*:\...\Content IE5\...\*"
EXCLUDE "*:\...\Content IE5\...\*.*"
EXCLUDE "*:\...\RECYCLED\*"
EXCLUDE "*:\...\RECYCLED\*.*"
EXCLUDE "*:\...\cache\*"
EXCLUDE "*:\...\cache\*.*"
EXCLUDE "*:\microsoft uam volume\...\*.*"
EXCLUDE "*:\microsoft uam volume\...\*"
EXCLUDE "*:\...\ea data. sf"
EXCLUDE "*:\...\pagefile.sys"
EXCLUDE "*:\...\ibmbio.com"
EXCLUDE "*:\ibmdos.com"
EXCLUDE "*:\msdos.sys"
EXCLUDE "*:io.sys"
EXCLUDE.DIR "c:\MSSQL7"
EXCLUDE.DIR "*:\recycled"
EXCLUDE.DIR "*:\recycler"
EXCLUDE.DIR "*:\...\system32\wins"
EXCLUDE.DIR "*:\...\system32\LServer"
EXCLUDE.DIR "*:\...\system32\dhcp"
EXCLUDE.DIR "*:\...\system32\config"
EXCLUDE.DIR "*:\system volume information"
EXCLUDE "*:\...\system32\perflib*.dat"
EXCLUDE.DIR "*:\...\temporary internet files"
EXCLUDE "*:\Documents and Settings\...\ntuser.dat.LOG"
EXCLUDE "*:\Documents and Settings\...\NTUSER.DAT"
EXCLUDE "*:\Documents and Settings\...\usrclass.dat.LOG"
EXCLUDE "*:\Documents and Settings\...\usrclass.dat"
EXCLUDE "*:\Documents and Settings\...\ntuser.ini"
EXCLUDE "*:\Allgemein\install\...\*"
EXCLUDE "*:\Allgemein\install\...\*.*"
EXCLUDE "*:\...\sqldata\...\*"
EXCLUDE "*:\...\sqldata\...\*.*"
Exclude.Dir "e:\...\*"
-------
I believe that dsm.opt shouldn't need to contain these double lines
(with '*' and '*.*').
This is the Client Option Set on the server (5.1.9.5):
-------
Option Sequence Override Option Value
number
------------------------- -------- --------
---------------------------------------------------------
DOMAIN 0 Yes all-local
INCLEXCL 0 Yes EXCLUDE *:\_inst
\...\*
INCLEXCL 1 Yes EXCLUDE *:\_inst
\...\*.*
INCLEXCL 2 No exclude "*:
\...\Content IE5\...\*"
INCLEXCL 3 No exclude "*:
\...\Content IE5\...\*.*"
INCLEXCL 4 Yes EXCLUDE *:
\...\RECYCLED\*
INCLEXCL 5 Yes EXCLUDE *:
\...\RECYCLED\*.*
INCLEXCL 6 Yes EXCLUDE *:
\...\cache\*
INCLEXCL 7 Yes EXCLUDE *:
\...\cache\*.*
INCLEXCL 8 No exclude "*:
\microsoft uam volume\...\*.*"
INCLEXCL 9 No exclude "*:
\microsoft uam volume\...\*"
INCLEXCL 10 No exclude "*:
\...\ea data. sf"
INCLEXCL 11 Yes EXCLUDE *:
\...\pagefile.sys
INCLEXCL 12 Yes EXCLUDE *:
\...\ibmbio.com
INCLEXCL 13 Yes EXCLUDE *:
\ibmdos.com
INCLEXCL 14 Yes EXCLUDE *:
\msdos.sys
INCLEXCL 15 Yes EXCLUDE *:io.sys
INCLEXCL 16 Yes EXCLUDE.dir *:
\recycled
INCLEXCL 17 Yes EXCLUDE.dir *:
\recycler
INCLEXCL 18 Yes EXCLUDE.dir *:
\...\system32\wins
INCLEXCL 19 Yes EXCLUDE.dir *:
\...\system32\LServer
INCLEXCL 20 Yes EXCLUDE.dir *:
\...\system32\dhcp
INCLEXCL 21 Yes EXCLUDE.dir *:
\...\system32\config
INCLEXCL 22 No EXCLUDE.dir "*:
\system volume information"
INCLEXCL 23 Yes EXCLUDE *:
\...\system32\perflib*.dat
INCLEXCL 24 No EXCLUDE "*:
\Documents and Settings\...\ntuser.dat.LOG"
INCLEXCL 25 No EXCLUDE "*:
\Documents and Settings\...\ntuser.dat"
INCLEXCL 26 No EXCLUDE "*:
\Documents and Settings\...\usrclass.dat.LOG"
INCLEXCL 27 No EXCLUDE "*:
\Documents and Settings\...\usrclass.dat"
INCLEXCL 28 No EXCLUDE "*:
\Documents and Settings\...\ntuser.ini"
INCLEXCL 29 No
exclude.systemobject
QUIET 0 Yes YES
SCHEDMODE 0 Yes PROMPTED
SUBDIR 0 Yes YES
-------
In the tsmerror.log on the client I see 'Invalid option
'EXCLUDE.SYSTEMOBJECT' found in cloptset and multiple warnings about
duplicate include/exclude entries.
There is again the small error with using '*' and '*.*'. I can clean it
up (someobody else created all the configurations and he isn't available
anymore) if needed.
In the tsmsched.log I see that the scheduler is sending the data from e:
(there is e.g. lines ".. ANS1228E Sending of object '\\s-eu-vie01db01\e
$\...' failed" and ".. ANS4987 Error processing '\\s-eu-vie01db01\e
$...': the object is in use by another process".
The backup which includes e: drive won't fit in my backuppool on the
server and often failed. But that's expected and I don't want to backup
the multiple file backups of the database backups (that's what is on
e:).
> One thing that stands out is that, in and of itself, your exclude.dir
> statement does not prevent the backup of files that reside in the root
of
> the drive.
>
> If you want to exclude all files on a Windows drive with exclude.dir,
here
> is what I recommend:
>
> exclude e:\*
> exclude.dir e:\*
>
> (note that you don't need the \... syntax).
I noticed that I would backup the files in the root of the drive but
there aren't any there. The ... syntax was taken from an example in the
official documentation.
> Alternatively, you can use:
>
> domain -e:
Yes, I did in effect this. I created a new client option set on the
server specifically for this machine which has option "domain all-local
-e:".
>
> This alternative is relatively simple, although this only affects
domain
> incremental backups, i.e.:
>
> dsmc i
>
> Thus you can still do backups that explicitly target this drive, like
> this:
>
> dsmc i e:
> dsmc i e:\mydir\* -subdir=yes
>
> Using the excludes above will prevent *any* backup of the drive.
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager support web page:
>
http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorag
eManager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2006-04-27
> 16:19:17:
>
> > I have "exclude.dir e:\...\*" in a client config to prevent it from
> > backing up the e: drive. When I run BA client, select backup and
local
> > filesystems and run estimate, it looks reasonable (the total cannot
be
> > including e: drive). I am not now completely sure but I also think I
did
> > run it by hand and it didn't backup e:. The backup started by the
> > existing association on the server seems to ignore at least this
setting
> > in dsm.opt. What can be wrong?
> >
> > Thanks
> >
> > Michal
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using, copying
or distributing the information in this e-mail or its attachments. If you have
received this e-mail in error, please notify the sender immediately by return
e-mail and delete all copies of this message and any attachments.
Thank you.
|
