anks,
Del
----
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a job well and doing it cheerfully.
=
> Trying to backup and Exchange IS (sure I've asked this before but I've
have been "Version 1".
The README file was correct, but the book was not.
Sorry for the mix-up. The book has been updated and
will be correct in the next release of the product.
Thanks,
Del
------------
Del Hoobler
IBM Corporation
[EMAIL PROTECT
Just a small correction in the update from Markus.
To start the SQL Server in single-use mode,
use the "-m" (in lower case) option.
Del
> Hi,
> you have to start SQL in single user mode, with the startup parameter -e,
Note:
> -e is small and the TDP Documentation says -E I think, when you use -E
machine and find out if it is picking
that one up first. You could do this by
temporarily renaming all of them EXCEPT the
one that your active Domino Server is using.
Thanks,
Del
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember
ort.
Thanks,
Del
----
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a job well and doing it cheerfully.
==
> When I try
Emil,
Please take a look at your Domino Server Admin help files.
"help\help5_admin.nsf" has information about this.
In there look at the COMPACT command.
The -T option turns on transaction logging if it
can be turned on for that database.
If you have problem getting logging turned on for a DB,
cal
es.
You can turn on tracing for DP for Domino by adding
this to the invocation:
/TRACEFLAG=ALL /TRACEFILE=filename.txt
If you want it examined by support, you will need to
call IBM support.
Thanks,
Del
------------
Del Hoobler
IBM Corporat
rmation on
what Data Protection for Domino thought the error was.
Also, look in the TSM Server activity log for the failing
backup session. It may contain some useful information.
Thanks,
Del
------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Re
o get it to work but
MSDE is not officially supported.
Here is a Microsoft web site that might be of interest:
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b325003
Thanks,
Del
----
Del Hoobler
IBM Corporation
[EMAIL PROT
t you know that there is an open APAR - IC35848
to address this problem. We have seen this happen in a few different
situations for Domino, Oracle, and Exchange.
Thanks,
Del
------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the be
Zoltan,
The platform makes a difference if you specify
directory delimeters only.
The APAR was just opened a week or so ago.
It is still being worked on.
Thanks,
Del
> Sorry about that I did not think the platform made a difference sinc
this message."
Thanks,
Del
----
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a job well and doing it cheerfully.
==
> Hi, we get this mes
Domino 5.1.5
available on the FTP site.
Thanks,
Del
------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a job well and doing it cheerfully.
==
&g
anks,
Del
----
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a job well and doing it cheerfully.
=
> I've been backing up quite a few da
suggest calling IBM Support.
Thanks,
Del
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a job well and doing it cheerfully.
==
>
>
Joe,
Do you mean Domino? (The old Notes client is no longer supported.)
Are you using Data Protection for Domino?
What version of Data Protection for Domino are you running?
What version of the Domino server are you running?
What error are you getting on the restore?
What platform are you running
Richard,
You will have to run the Microsoft Exchange DS/IS
consistency checker when restoring only the IS to
an alternate server.
Thanks,
Del
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a
Mehdi,
Look at the /RELOCATE and /TO options.
(... or the right-mouse click while the
backup to restore is selected.)
This allows you to move the database
to a different physical location.
Thanks,
Del
> SQL Version 7
> TDP Version 2.2.1
>
>
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/agents/domino/
> Is there an ftp site around that contains old fixes for older versions of
> software. I am in the UK.
>
> I'm looking for FIXTEST 1.1.1.01 for TDP D
so, the answer is no...
... unless you decide to install a TSM Server local to your
environment.
If I am not understanding your question correctly,
could you please clarify?
Thanks,
Del
--------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember
er corruption... and even if some "brick-level" solution
could get close, any fairly large Exchange server restored via
"brick-level" would take a very, very long time.
I hope this helps.
Thanks,
Del
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
- Remember that the best job security is
doing a job well and doing it cheerfully.
> Has anyone tried TSM for Exchange together with Exchange 2003? Does it
work?
Niklas,
We are working on Exchange 2003 support right now.
Look for Data Protection for Exchange to support
Exchange 2003 somewhere in the timeframe when it is
officially released from Microsoft or soon after.
As far
Vladimir,
Yes. I know what the problem is.
There is a known situation that you must handle
when restoring very large SQL databases.
Basically, this is what happens:
1. The database is started to be restored.
A small amount of data is restored from the TSM Server.
2. The SQL server looks at
David,
I did not specify because the preformatting and
initialization that the SQL Server is performing
can vary based on the speed of the disk, CPU speed,
and physical file layout.
You may want to bump the COMMTIMEOUT value up high,
run some test restores of your "larger" databases
to get a feel
Zoltan,
Look into the SQL Server logs and the TSM Server
activity log to find out if there is any more
information there.
Thanks,
Del
> Can someone give me some ideas on how to resolve this problem with
> restoring an M$-SQL database ?
>
> H
Richard,
Very good points.
In fact, we also discussed this when we evaluted the requirement.
There are other reasons for customers to want to boost
the COMMTIMEOUTs for certain nodes based upon
communication links etc... and this was termed as
a shorter term solution for this SQL problem
but also
Niklas,
It is looking at the Information Store service.
Sometimes this occurs when you are running under
a Windows userid that does not have Administrator
authority to view the registry. For example, this may
occur when you are running from a scheduler service
that is being run under a different
Bill,
"TDPEXCC BACKUP * FULL" backs up the
Information Store Storage Groups only.
In order to back up the SRS, enter:
TDPEXCC BACKUP "SRS Storage" FULL /EXCAPPLICATION=SRS
Thanks,
Del
> Does the TDP Exchange command:
>
> BACKUP * FULL
Bill,
No. You should not do this.
The meta object in SQL actually contains restorable data
that describes the physical layout of the database.
That data is used for some types of queries and for
the GUI restore tree expansion. So, keeping the meta data
on quicker (available) storage devices is a
Joshua,
You need the "Paid" license file.
The "PTF" versions on the FTP site
have a "dummy" license file that
will not allow them to function at all.
(...thus, the errors you are seeing.)
The "Paid" license file comes on the media when you
purchase it. If you have a Passport Advantage account,
y
Zlatko,
For Exchange, you will not get any benefit by binding
the meta objects to a disk only storage pool because
there is no data stored with the meta object.
In fact, with Exchange, since all of the objects
created during a backup are part of the same
transaction, the objects will need to have
Brad,
The first question that you should ask the potential customer
is if they are referring to storage group (database level)
backup and restore or mailbox/item level backup and restore.
It is a very imporant distiction that should be clarified
with the customer first.
For full storage group (da
Joni,
FYI...
Data Protection for Lotus Domino requires at least Domino 5.
It does not support Domino 4. (Domino 4 did not have the
backup/restore APIs for doing database level online backup/restore.)
Once you get to Domino 5, Data Protection for Lotus Domino will
handle the online backup of the
James,
Take a look at Microsoft Knowledge Base Article - 281413.
It describes how to back up the server using a utility
shipped with SharePoint Portal Server called MSDMBACK.
Thanks,
Del
> Does anyone know if Tivoli is/has intentions of prov
James,
Yes. I understand your point. There is a requirement
already opened for this. We have to prioritize
it with the others that we have. I always tell
customers to call your IBM/Tivoli rep and
remind them how important it is to your organization.
Thanks,
Del
-
Jozef,
This is normal TSM policy management.
If you have VEREXISTS set to 2,
when you take the 3rd full backup, the oldest
inactive copy will be deleted when the
next expiration process is run.
Thanks,
Del
> I have one question about data ex
Eric,
I would have them check again to make sure they
are using the NODENAME they think they are using.
Have them check their DP for SQL logs files as well.
Also, check the TSM Server activity log to see
what messages are being logged for that NODENAME.
DP for SQL will log ending statistics that
s
Dave,
This has to do with the fact that the TSM API for
Windows handles objects as case insensitive
but case preserving. This is an anomaly resulting
from the fact that SQL Server allows case-sensitive
databases names. You can continue to keep things
as they are with the resulting error or change
Pattie,
This is redirected output from the running program.
You would need to write a script to handle the pruning.
Thanks,
Del
> Running TDP 5.1.5, here is the command from the excfull.cmd.
>
> start /B tdpexcc backup * full /tsmoptfile=dsm
again
once the reclamation threshold you have set on the TSM Server
is reached and the reclamation process runs.
Please read the TSM Server Admin Guide for more details.
Del Hoobler
IBM Corporation
Marc,
Data Protection for Domino works at the
database level. That means the entire database
and all its contents are backed up and restored.
As long as the private folder is stored in the
database, it will be backed up and restored.
There are situations where private folder are
not stored in the
LETED was set to something low.
Thanks,
Del
--------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
Brec,
It is not available today.
FYI.. some customers use COMPRESSION to "scramble" the files
and provide a very minimal level of "wandering eyes" security.
If true encryption is a critical need for your business.
please contact your IBM representative.
Thanks,
Del
---
Eric,
What "manual" says that the "Exchange Tracking Log is vital for
Exchange Server recovery"? That isn't true. You do not need
the tracking logs to recover an Exchange Server.
You may still want to back those files up...
Since these files could be changing, you could change
the to copy serial
Larry,
If you are referring to the "Last Backup Start Date/Time:"
on the filespace, it is updated after a successful backup.
Here is an example from my QUERY FILESPACE:
tsm: TSMSERVER1>q file HOOBLER_SQL f=d
Node Name: HOOBLER_SQL
This question is being handled off-line for
further clarification.
Thanks,
Del
> Hi Del,
> Looking further down it appears there has been a table backup:
> Node Name: MSSQLAFS
> Filespace Name: AFSDBMS\data\0001
hem
indicate a DP for SQL version 2 or Version 5 client.
For example: HOOBLER\meta\
HOOBLER\data\0001
Thanks,
Del
--------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
Lawrence Clark
Chris,
Data Protection for SQL does not have a VERIFYONLY function.
You will have to restore the database in order to verify it.
You could restore it to an alternate name or stand-by server
if you do not want to interrupt your live database.
Thanks,
Del
-
Bill,
How about using the INCLUDE statement to bind the
log backups to a management class with different policies?
For example:
INCLUDE S*.TXN MGMT_CLASS_7_DAYS
where MGMT_CLASS_7_DAYS has settings of
VERE=NOLIM, VERD=NOLIM, RETE=7 RETO=7
Thanks,
Del
-
Bill,
The logs are uniquely named based on the log name
and logger id. You are correct, they won't be
"inactivated" (forced inactive) until you run the
INACTIVATELOGS command.
When you run the INACTIVATELOGS command, DP for Domino
will determine what logs are necessary for the
current list of *ac
Kent,
The normal procedure is to run the INACTIVATELOGS command
after a full backup so that only the logs necessary
to restore the active full backups, remain active.
It will only "break" the PIT restores if you do not have
your policy settings correct. If your policy settings
are set up so that
There are two *guaranteed* ways to get a consistent
Domino database backup.
1.) Shut down the Domino server and back up the files.
(For example, use the BA client.)
2.) Use Data Protection for Domino, which uses the
Domino backup and restore APIs.
This can be done while the Domino Ser
passwords are encypted using
a different method and could be getting out of sync.
If you are running one of them in a clustered configuration,
you should use different NODENAMEs for them.
Thanks,
Del
Hi there,
This is something Del Hoobler can
Pattie,
What messages are in the Data Protection for Domino log file
for the same time stamp? (the default filename is domdsm.log)
If there are entries in the Data Protection for Domino log file
it will tell you more details on the failure.
If there are no entries in the log file, then check the
Yi,
>From the Data Protection for SQL 5.1.5 READSQL.TXT file.
Data Protection for SQL 5.1.5 requires
the following MINIMUM software levels:
- Windows NT Server 4.0 SP4 or
Windows 2000 SP1 (Server, Advanced Server or DataCenter Server)
- Microsoft SQL Server 7.0 SP3 or
Microsoft
Zenghui,
Did you run the dominstall program after installation?
It sets up all the necessary links and creates
.profile entries etc., needed for proper operation.
This was tested with Domino 6 on AIX 5.1, so it is
most likely a setup/configuration issue.
Check the User's Guide for details on runn
Chris,
I am assuming you are using the same NODENAME when logging
into the TSM Server. If so, have you succesfully generated
and stored the password for that node on the machine that
you are doing your restore on?
I suggest getting the the following command
to work before even attempting a restor
Mehdi,
When you restore the master database, after the restore
is completed, the SQL server is shutdown and you will
get the error message. That is documented in the User's Guide.
Please read the Appendix carefully about restoring the master database.
(It is under "Advanced Restore Procedures".)
Y
Matt,
Did you change the base TSM installation directory?
Were these shortcuts that you made manually?
Take a closer look at this since the executable names
(TDPEXC.EXE and TDPEXCC.EXE)did not change,
and the "TDPExchange" sub-directory did not change.
Thanks,
Del
--
Matt,
This change came along with the product name change.
If you created manual shorcuts, you will need to update them.
Thanks,
Del
> The shortcut was made manually to the "All Users" desktop by going
> C:\Documents and Settings\All Users\S
Lisa,
It should be detecting those new databases.
Each time a "DOMDSMC INCREMENTAL" backup is run
it should be picking up "new" databases (as well as
logged databases that the DBIID has changed or
non-logged databases that the internal time stamp
has changed on.)
Something else must be wrong in y
Bill,
You are correct. It also "inactivates" databases
that no longer exist on the Domino server.
If a customer only runs archivelog and selective backups,
the databases that have been "removed" from their
Domino Server will remain active and never expire.
The bigger problem I see with only runn
Abdulaziz,
Take a look at the IBM knowledge base for IBM TSM for Mail.
(The knowledge base is getting filled with more articles every day.)
Here is the direct URL for IBM TSM for Mail:
http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforMail.html
Put the word "Perfo
Matt,
A "format error" normally means that a backlevel
"client" is trying to access data backed up
from a later level of the "client".
A client here can be an "API client".
It looks like you backleveled the TSM API version...
... or you connected with a later version of the
API from another machin
Eddie,
DP for Domino writes summary information in the form of
ANE4991I messages. Try something this:
SELECT * FROM ACTLOG WHERE MSGNO=4991
Thanks,
Del
> I am running tdp for domino and I am looking for the table that this
> indormation
and enter "1083052" in the search area.
Thanks,
Del
----
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
Sandra,
You need to find out where the .EDB, .STM, and .LOG files are
being stored for each Exchange storage group and EXCLUDE those
directories. By default, those files are stored under a
directory under: C:\Program Files\Exchsrvr\
However... the files are typically placed into different locati
David,
If you set up your management classes correctly, this is something
you can do. Keep in mind that you will need a log backup to go
along with the set backup in order for the SQL Server to properly
recover the database after a restore. Because of that, you will
need to make sure your log and
Adam,
If you haven't already done so... go to this URL:
http://www.ibm.com
and search for:
ACN5238E
There is one article that discusses the permission issue
and how to resolve... as well as hotlinks to Microsoft
support pages to describe this.
Thanks,
Del
--
Zoltan,
You need to examine the log file or output of Data Protection for SQL.
RC=1912 means a VDS creation error. This happens when
Data Protection for SQL has asked to create a VDI connection
to the SQL Server in order to perform a backup or restore,
and the creation failed. The VDI error log an
Luc,
This is a known requirement that has been submitted and being
prioritized for a future release, i.e. allowing you to
"exclude" certain databases from a command.
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 11/30/200
ski - Partner
> Infinity Network Solutions Inc.
> Phone: 416-235-0931 x26
> Fax: 416-235-0265
> Web: www.infinitynetwork.com
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Del Hoobler
> Sent: Tuesday, Novem
Mladen,
One way to do this is to create a separate NODENAME with
different policy settings and use that NODENAME to perform
a full back up of your SQL Server databases once per month.
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
t; 12/01/2004 11:43:08 Elapsed processing time: 0.02 Secs
> 12/01/2004 11:43:08 ACO0151E Errors occurred while processing the
request.
>
>
>
>
> Del Hoobler <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Luc,
I have this in my DSM.OPT file:
EXCLUDE "\...\master\...\log*"
Here is the output when I try to back up the log of master:
-
C:\Program Files\Tivoli\TSM\TDPSql>tdpsqlc backup master log
IBM Tivoli Storage Manager for Databases:
Data Protection for
Kjell,
No. This is not possible.
You can have one TSM NODENAME and back it up with
two separate invocations of "tdpsqlc". For example:
tdpsqlc backup * full /sqlserver=.\D01 ...etc...
tdpsqlc backup * full /sqlserver=.\BD1 ...etc...
However, I don't recommend this. I recommend that you
Eric,
Have you tried the different hints and tips that I
have given previous ADSM-L members about addressing this error?
It usually boils down to a permissions issue or if running in a cluster,
you forgot to use "/EXCSERVER=virtual-exch-server-name" option.
Go to:
http://search.adsm.org
Search
Fred,
Data Protection for SQL requires SYSADMIN role for the ID that
runs the backups and restores. Data Protection for SQL uses the
specialized SQL Server VDI (Virtual Device Interface) API
in order to get the additional speed and function for performing
backup and restores. In order to utilize t
Robert,
You need to make sure that you have enough space on your volumes that
contain the transaction logs for each Exchange storage group.
With Exchange differentials, the transaction logs are not truncated
until the next full backup. And so, you will need to make sure there
is enough space to ho
Sam,
There is an IBM technote (1105967) that explains this.
Go to:
http://www.ibm.com
and search for:
"Restoring SQL database to an alternate database"
or
"1105967"
Make sure you include the quotation marks to help limit the search.
Thanks,
Del
--
Sam,
There is no "set access" function for Data Protection for SQL
so you need to connect with the TSM Server as the NODENAME that
originally performed the backup.
Did you try the IBM Tech note (1105967)that I pointed you to
on 12/21 in this list? What happened when you tried it?
Go to:
htt
e read these and now for a random unknown reason is
> refusing!
>
> Is there any way someone could cut and paste this for me or is it a big
> document?
>
> Thanks for your help,
>
> Sam
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL
Norman,
This looks like a direct hit. This is an "issue" with the
Exchange Server 2003 SP1 new optimization feature.
It applies to any backup application that uses the
Exchange Server backup and restore API for performing online backup.
That is why Microsoft put out a hotfix for Exchange Server fo
Robert,
It looks like you did something incorrectly when performing the
alternate machine restore.
Did you choose "Run Recovery" and "Replay restored logs ONLY"?
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 01/16/2005
12:41:17 AM:
> Hi t
Yiannakis
Go to:
http://www.ibm.com/us/
and search for:
+DP +SQL +ANS1017E
You will find that when restoring large databases,
Data Protection for SQL will restore a small amount of data.
At that point, the SQL Server formats the large files that will eventually
hold all of the restored dat
> This suits what we want, we only want the incremental restore points in
> between our full backups for the last couple of days.
>
> Thanks,
>
> Tim Rushforth
> City of Winnipeg
>
> -Original Message-
> From: Del Hoobler [mailto:[EMAIL PROTECTED]
> Sent: Wed
Hi Tim,
It does not support it today... but we know that people are
starting to ask for it... so stay tuned to this channel.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 01/25/2005
05:20:04 PM:
> Does Data Protection for Exchange support
Kevin,
If you want to restore a specific inactive backup first you should
query all the backups for the specific database, for example:
tdpsqlc query tsm dbname /all
This will show you all active and inactive the backups for the
specific database.
Then... you should perform the restore spe
rds
>
> Robert Ouzen
> E-mail: [EMAIL PROTECTED]
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
> Behalf Of Del Hoobler
> Sent: Wednesday, January 26, 2005 7:52 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: MSSQL single database r
would be great.
> Thanks Again,
> Kevin
> Kevin M. Lipscomb
> Dan River Inc.
> Systems Engineering
> [EMAIL PROTECTED]
> 434-799-4823
>
>
>
> Del Hoobler <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager"
> 01/26/2005 12:52 PM
> Pl
Bill,
Microsoft Exchange has a restriction that you cannot restore an Exchange
5.5
database into an Exchange 2000 server (let alone into an Exchange 2003
server.)
See this URL for the statement from Microsoft:
http://www.microsoft.com/resources/documentation/exchange/2000/all/reskit/en-us/resguid
If you want to perform multi-session (STRIPES) backup and restore,
you should set COLLOCATION by filespace turned on so when the data
is migrated or sent to tape, the striped data will remain on
separate tapes. This is discussed in the User's Guide.
Thanks,
Del
--
"ADSM: Dist Stor Manager" wrote on 02/11/2005
10:44:25 AM:
> Hello,
>
> Simple question;
>
> Can we backup MySQL database with TDP for MS SQL
>
> Regards,
>
> Joe Crnjanski
Joe,
No.
Del
John,
Are you excluding databases from backup?
Are all of your database backing up successfully?
Are the databases being backed up to the correct management classes?
These are some of the things you should check. If you are still
having trouble understanding the messages or are unsure if
your data
Fred,
Normally, a Data Protection for SQL schedule is an ACTION=COMMAND
type of schedule... which actually calls a batch file that launches
the Data Protection for SQL command to run the back up.
Did you update the Data Protection for SQL options files (DSM.OPT)
to point to the new TSM Server?
Ar
Richard,
A quick glance at the Microsoft ESEBKMSG.H file shows this:
//
// MessageId: hrInvalidBackup
//
// MessageText:
//
// An incremental backup cannot be performed when circular logging is
enabled.
//
#define hrInvalidBackup ((HRESULT)0xC800020EL)
A
Ho Richard,
That sounds like the problem. This return code is coming
from the Exchange Server. Data Protection for Exchange
couldn't do an incremental backup even if it tried
because the Exchange Server is preventing it.
Do I really need to say that I have seen cases where there
is "stale" config
Hi Joe,
These files are a part of the Microsoft SDKs.
I am not at liberty to "distribute" them myself, but I am sure
you can obtain them somewhere on the web (as a few have pointed out)
or by obtaining the Microsoft SDKs yourself.
Thanks,
Del
Data Protection for Domino does not have multiple session
support within a single instance at this time.
You will need to start two separate instances of Data Protection for
Domino.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 03/05/2005
Matt,
Data Protection for Lotus Domino 5.3.0 is the latest version...
http://www-306.ibm.com/software/tivoli/products/storage-mgr-mail/platforms.html
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 03/07/2005
04:31:46 PM:
> Can someone con
401 - 500 of 1716 matches
Mail list logo
