Backup Central

Just to make sure I'm not looking in the wrong places....
Is it right that there were no TDP for SQL (32 bit) updates between 5.2.1
and 5.5 ?

My SQL servers don't have all the requirements for the 5.5 client, but I
need that excludedb option to avoid the whole "differential backup of the
master db" issue
http://www.adsm.org/lists/html/ADSM-L/2005-11/msg00258.html

I hate coding the database names explicitly. Is my only option forcing
the sql servers to upgrade?

Regards,
Shawn
________________________________________________
Shawn Drew


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.

Shawn,

If you want the use /excludedb option, you need to install DP for SQL 5.5.0
or higher.

Regards,

Mark L. Yakushev


From: Shawn Drew <shawn.drew < at > AMERICAS.BNPPARIBAS.COM>
To: ADSM-L < at > VM.MARIST.EDU
Date: 07/30/2008 02:48 PM
Subject: [ADSM-L] TDPSQL update



Just to make sure I'm not looking in the wrong places....
Is it right that there were no TDP for SQL (32 bit) updates between 5.2.1.
and 5.5 ?

My SQL servers don't have all the requirements for the 5.5 client, but I
need that excludedb option to avoid the whole "differential backup of the.
master db" issue
http://www.adsm.org/lists/html/ADSM-L/2005-11/msg00258.html

I hate coding the database names explicitly. Is my only option forcing
the sql servers to upgrade?

Regards,
Shawn
________________________________________________
Shawn Drew


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.

The excludedb option is the only way to have "tdpsqlc backup * diff "
ignore the master db, right?

Regards,
Shawn
________________________________________________
Shawn Drew





Internet
barsik < at > US.IBM.COM

Sent by: ADSM-L < at > VM.MARIST.EDU
07/30/2008 06:16 PM
Please respond to
ADSM-L < at > VM.MARIST.EDU


To
ADSM-L
cc

Subject
Re: [ADSM-L] TDPSQL update





Shawn,

If you want the use /excludedb option, you need to install DP for SQL
5.5.0
or higher.

Regards,

Mark L. Yakushev


From: Shawn Drew <shawn.drew < at > AMERICAS.BNPPARIBAS.COM>
To: ADSM-L < at > VM.MARIST.EDU
Date: 07/30/2008 02:48 PM
Subject: [ADSM-L] TDPSQL update



Just to make sure I'm not looking in the wrong places....
Is it right that there were no TDP for SQL (32 bit) updates between 5.2.1.
and 5.5 ?

My SQL servers don't have all the requirements for the 5.5 client, but I
need that excludedb option to avoid the whole "differential backup of the.
master db" issue
http://www.adsm.org/lists/html/ADSM-L/2005-11/msg00258.html

I hate coding the database names explicitly. Is my only option forcing
the sql servers to upgrade?

Regards,
Shawn
________________________________________________
Shawn Drew


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.

Did you try by adding this to the DSM.OPT file?


EXCLUDE "\...\master\...\diff*"


Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU> wrote on 07/31/2008
09:18:24 AM:

[image removed]

Re: TDPSQL update

Shawn Drew

to:

ADSM-L

07/31/2008 09:20 AM

Sent by:

"ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>

Please respond to "ADSM: Dist Stor Manager"

The excludedb option is the only way to have "tdpsqlc backup * diff "
ignore the master db, right?

Clever bugger! Strange that EXCLUDE "\...\master\...\*" didn't work, but
this variation did.

ADSM-L!

Regards,
Shawn
________________________________________________
Shawn Drew





Internet
hoobler < at > US.IBM.COM

Sent by: ADSM-L < at > VM.MARIST.EDU
07/31/2008 09:31 AM
Please respond to
ADSM-L < at > VM.MARIST.EDU


To
ADSM-L
cc

Subject
Re: [ADSM-L] TDPSQL update





Did you try by adding this to the DSM.OPT file?


EXCLUDE "\...\master\...\diff*"


Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU> wrote on 07/31/2008
09:18:24 AM:

[image removed]

Re: TDPSQL update

Shawn Drew

to:

ADSM-L

07/31/2008 09:20 AM

Sent by:

"ADSM: Dist Stor Manager" <ADSM-L < at > VM.MARIST.EDU>

Please respond to "ADSM: Dist Stor Manager"

The excludedb option is the only way to have "tdpsqlc backup * diff "
ignore the master db, right?


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.