ADSM-L

Re: Backup completion / BACKUP_END on network FileSpaces?

2004-04-10 09:02:46
Subject: Re: Backup completion / BACKUP_END on network FileSpaces?
From: Bill Boyer <bill.boyer AT VERIZON DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sat, 10 Apr 2004 09:01:54 -0400
Andy,
        Here is some more information on the system Ted had posted about. He was
covering for me while I was out ill this week. The DSM.OPT file for that
node specifies:

DOMAIN C:
DOMAIN D:
DOMAIN M:
DOMAIN Q:
DOMAIN S:

and no other domain statements. When the incremental backup starts you get
these messages. See that the Q: drive is listed differently??

04/03/2004 01:59:12 Incremental backup of volume '\\sgtpepper\c$'
04/03/2004 01:59:12 Incremental backup of volume '\\sgtpepper\d$'
04/03/2004 01:59:12 Incremental backup of volume '\\sgtpepper\m$'
04/03/2004 01:59:12 Incremental backup of volume 'Q:\'
04/03/2004 01:59:12 Incremental backup of volume '\\sgtpepper\s$'

When the incremental on the Q: drive completes, the 5.2.2.5 client now
refers to it as the '\*' filespace.

04/03/2004 02:02:52 Normal File-->     2,167,078,912
\\sgtpepper\q$\MSSQL7\jdedata\jde_PRODUCTIONlog_new.ldf [Sent]
04/03/2004 02:02:52 Successful incremental backup of '\\sgtpepper\q$\*'

 The filespace information on the TSM server shows \\sgtpepper\q$ and hasn't
gotten updated. The drive is mapped as part of a preschedulecmd script that
issues the following command:

"C:\Program Files\SnapDrive\sdcli" snap mount -k f -s
sqlsnap__sgtpepper__recent -d q

Bill Boyer
DSS, Inc.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Andrew Raibeck
Sent: Thursday, April 08, 2004 12:36 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Backup completion / BACKUP_END on network FileSpaces?


Hi Richard,

I don't think include/exclude would really interfere with this. I am
focusing on the messages

04/07/2004 02:07:28 Successful incremental backup of '\\getback\q$\*'
04/08/2004 07:47:50 Successful incremental backup of '\\gwise99\gwise\*'

These indicate that somewhere along the line the file specification is
being made with the '\*' at the end of the file system name. Even if he
excluded every file in those file systems, a successful incremental backup
of \\getback\q$ should cause the file space last backup date to be
updated. However, since an incremental backup of \\getback\q$\* is not
considered a full incremental backup (because of the '\*' qualifier), it
doesn't get updated.

My money (all two cents of it!) says that somewhere there is a DOMAIN
statement or other file specification like this:

   \\getback\q$\*

as opposed to

   \\getback\q$

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[email protected]
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.



Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/08/2004 08:25
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Backup completion / BACKUP_END on network FileSpaces?






>On both of these clients, the filespaces are included using a domain
>statement, and the backups are simply run with a schedule where
>action=incremental, without explicitly specifying any objects.

Ted - Does 'dsmc q inclexcl' show any "interference" with that intention?

  Richard Sims