-
"ADSM: Dist Stor Manager" wrote on 06/09/2006
05:14:50 PM:
> Well, I think I found my answer. We don't have the latest and greatest
> in-house yet, and I didn't see it available for download either. Here is
> a recent quote from Del Hoobler... "Data Protection
Paul,
In addition to Richard's suggestions, you should also check
the TDPSQL.LOG file as well as the redirected output of the
TDPSQLC command that you do in your command script.
In some cases, when things work correctly while logged in,
but do not work correctly as scheduled, it means that the
"l
ww-1.ibm.com/support/docview.wss?uid=swg21083564
http://www-1.ibm.com/support/docview.wss?uid=swg21105967
http://www-1.ibm.com/support/docview.wss?uid=swg21168550
Thanks,
Del
------------
Del Hoobler
Tivoli Storage Manager Development
IBM
Exchange 2003 support was added in Data Protection for Microsoft Exchange
version 5.2.1.
Here is a web page that shows the "Hardware and software requirements for
IBM Tivoli Storage Manager for Mail version 5.3.3":
http://www-1.ibm.com/support/docview.wss?rs=669&context=SSTG2D&uid=swg21233936&loc
id=swg21105967
http://www-1.ibm.com/support/docview.wss?uid=swg21168550
Thanks,
Del
------------
Del Hoobler
Tivoli Storage Manager Development
IBM Corporation
"ADSM: Dist Stor Manager" wrote on 07/19/2006
01:30:20 AM:
> We ha
Mark,
Return code = 1108 from Data Protection for Domino
means that it could not find any Domino databases.
Please review the error log from the actual run
or the redirected output of the command to find
any additional information that might have been logged.
By default, the error log is "domdsm.
Zoltan,
What is the RETEXTRA setting?
You should have something like this:
VEREXISTS NOLIMIT
VEREXISTS NOLIMIT
RETEXTRA 30
RETONLY 30
This will keep all inactive backups for 30 days.
Also.. if the management class is not the default,
make sure you have coded the INCLUDE statements
c
Hi Eric,
SQL Server 2005 support was added in November of last year,
one day following the official launch of SQL Server 2005 by Microsoft.
You will need to obtain Data Protection for SQL version 5.2.1.03 (or
later)
from the following web site:
Where:
FTP Site:
ftp.software.ibm.com
Di
Hi Eric,
Data Protection clients do not have a "new release" (or even a PTF)
near as often as the BA client does. But, there are still situations
like this where we try to get customers the support they need,
as soon as we can. Sometimes that means, putting this kind of support
into a fix release.
Paul,
Assuming that "SQLDB_COPYPOOL" can be tape...
The only implication that I can think of is that if you have to resort
to using the copy storage pools, there are some DP/SQL queries
(such as querying the TSM Server for SQL database backup file information)
that will require tape mounts, possi
Paul,
Yes. There is an IBM Technote on the exact subject.
Go to:
http://www.ibm.com/us/
Search for (include the double quotes):
"Restoring an SQL database to an alternate database"
Our go to it directly here:
http://www.ibm.com/Search/?q=1105967
Thanks,
Del
---
Hi Stuart,
If you want to keep your backups based on time,
your management classes should look something like this:
VEREXISTS NOLIMIT
VERDELETED NOLIMIT
RETEXTRA30
RETONLY 30
This will make sure all backups are kept for at least
30 days, regardless of how many times the ba
Fred,
Go to:
http://www.ibm.com/us/
Search for:
"Encrypting Data Protection for SQL Backups"
(include the double quotes around the "Search for" text)
Del
"ADSM: Dist Stor Manager" wrote on 08/25/2006
01:07:23 PM:
> Since T
Ku,
Yes... if all of the backups are correctly bound to the "NOTESMC"
management class as you have it defined below, then all backup objects
(logs and databases) will be kept on the TSM Server for 90 days.
Did you try it? Is there a problem?
Thanks,
Del
-
Hi Robert,
I recommend that you check the event logs and other system logs closely.
I think that there must be something else running (like another backup
type,
or a defrag, or something else) that is causing this situation to occur.
I know that you said that the exchange admin told you that the d
Hi Robert,
We are currently investigating a problem where the Data Protection
for Exchange 5.3.3 GUI is loading the restore screen without
clearing a previous query... so you may see duplicate entries.
This should not affect the operations.
Thanks,
Del
--
Yi,
Data Protection for SQL Server does not officially
support SQL Server 2005 Express Edition.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 09/05/2006
09:57:46 AM:
> Hello,
>
> Does TDP for SQL Server support SQL Server 2005 Express Edi
Hi Kelly,
You can encrypt any application that uses the TSM API (v5.3 or later)
using transparent encryption. This include Data Protection for SQL.
Take a look at this IBM technote (1213548) for details
on encrypting Data Protection for SQL backups:
http://www-1.ibm.com/support/docview.wss?uid
Ian,
There is only a 5.3.3 version of Data Protection for SQL for "x64".
It is at the same functional level as Data Protection for SQL 5.2.1
for "x32" and "ia64".
Is there something specific you are looking for?
Thanks,
Del
"ADSM: Dist Stor
Ian,
Data Protection for SQL will use the TSM API at the 5.3 level
for backing up the data. The TSM API is upward compatible.
It is fine to use the latest DP/SQL 5.2.1 version in your enterprise.
That package is included on the "5.3" TSM for Databases CD
which means it will be supported for as lon
Transparent encryption is not currently supported for the BA Client.
It's not quite as simple to support transparent encryption for
the BA Client as it is for the TSM API due to the no query restore
functionality of the BA Client.
Transparent encryption for the BA Client is a known requirement.
T
Mike,
You need to obtain the "x64" version.
This is version DP for SQL 5.3.3.
It is available on Passport Advantage.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 09/21/2006
02:42:37 PM:
> We have the following:
>
> Windows 2003 R2 Server
t;ADSM: Dist Stor Manager" wrote on 09/21/2006
04:52:39 PM:
> Hi Del,
>
> We are only seeing TDP Oracle 5.3.3 on Passport Advantage.
> Did we not look in the right place?
>
> Thanks,
> Yi
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[
Hi Paul,
Data Protection for SQL does not have a direct TSM "archive"
function as you see with the TSM Backup-Archive client.
Many customers accomplish this by creating a second
nodename for archive purposes (for example, SQLSRV42_ARCH),
and have the management class settings for the backups
made
Srinath,
RC=1914 means the SQL Server reported some type of error
to Data Protection for SQL. Examine the the TDPSQL.LOG file
(or appropriate file if you specified a different name)
for details on what the error was.
Thanks,
Del
"ADSM: Dist
Pranav,
The SQL Server is performing the "preformat" of your SQL database files.
The amount of time it will take depends on the types of disks, speed of
disks, and database file layout.
Data Protection for SQL is "blocked" until the SQL Server finishes
the database preformat. I would boost COMMTIM
This is expected behavior. This is documented in the DP/SQL User's Guide:
Note: When restoring large SQL databases, specifying a value of
at least 1 in the commtimeout option will help prevent
a restore operation from ending prematurely. If the restore
operation i
Antonio,
You are on the right track. You may want set up a separate scheduler
instance for each virtual exchange server on each of the machines
that could run that particular virtual exchange server.
This scheduler should be dependant on the virtual exchange server,
so that it follows the virtual
Orin,
By default, Data Protection for Exchange will restore
data back into the live Exchange Server and into the
original storage group and database. The Microsoft
Exchange Server requires that the database be dismounted
for this operation. If that is not what you want,
it would help to understand
Thanks,
Del
--------
Del Hoobler
Tivoli Storage Manager Development
IBM Corporation
"ADSM: Dist Stor Manager" wrote on 10/27/2006
12:19:50 PM:
> I have a very simple question, when adding the name for a SQL database
> in the TDP for SQL's cmd file can the datab
Data Protection for Exchange creates backup objects
not archive objects.
Also.. be careful about deleting Data Protection for Exchange
objects as there are multiple objects per single logical backup.
Unless you know exactly what these are, I would not advise it.
If you cannot wait for retention p
There is not a documented list of Data Protection for Domino
return codes at the current time. 0 means success, non-0 means failure.
You should analyze program output, TSM Server activity log entries,
and/or domdsm.log entries for details on failures.
If you find a case that sufficient information
Zoltan,
For TSM ACTION=COMMAND schedules, the return code of the last
executing program within the script will be the error code
that gets bubbled back up to the scheduler and recorded
in the scheduler log. Make sure your scripts are
trapping that error code and return that code, if there
are othe
Zoltan,
If there is nothing in the domdsm.log file, then
Data Protection for Domino did not launch.
Data Protection for Domino will always write an
entry into the domdsm.log file for each command it runs...
... uUnless you have changed the name of the logfile
by using the "logfile" option in the
Orin,
When you say the IBM experts cannot figure this out,
I assume you meant you have a PMR open with TSM support.
Is that correct? If not, please open a PMR so that the
TSM performance team can figure out where the bottle-neck is.
If so, I would continue to drive the PMR with IBM support.
Resto
Orin,
You can't freeze just "one" particular backup.
Short term, you can solve this by creating a new NODENAME
for your future Data Protection for Exchange backups.
This will keep all of your current active backups "frozen".
In the future, you should look into using Data Protection
for Exchange CO
Orin,
If you delete Exchange logs that Exchange needs for recovery,
you will run into issues. You should shutdown all of your
Exchange services and restart them.
Then try the backup again.
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 11/1
Paul,
No. If you want to create backups that are kept for longer term
than your normal Data Protection for SQL backups, you could
create a separate nodename, for example, SQLSRV10_ARCH,
and back up using that node once a week or once a month,
(or whatever your needs are) and make sure to bind thos
Bill,
You should be able to do this. For example... assume this:
--- "Storage Group B"
--- MailboxDB1
--- MailboxDB2
--- MailboxDB3
--- MailboxDB4
- A FULL backup is done of "Storage Group B".
- An INCREMENTAL backup is done of "Storage Group B"
- An INCREMENTAL backu
Robert,
Try the ideas outlined in this IBM TechNote:
http://www-1.ibm.com/support/docview.wss?uid=swg21200586
Del
---
"ADSM: Dist Stor Manager" wrote on 12/26/2006
02:42:06 AM:
> When trying to backup a Sql server 2000 Sp4 with TDP for Micros
Thanks,
Del
"ADSM: Dist Stor Manager" wrote on 01/03/2007
04:40:29 AM:
> Hi to all
>
> First a thank?s to Del Hoobler with my previous question about the
> ACO5400E error , the suggestion help ??
>
> I tried
David,
Go to:
http://www.ibm.com/us/
and search for:
ACO5423E
You will find your answer.
Bascially, it says you need to obtain Data Protection for SQL 5.2.1.03
or later for SQL Server 2005 support.
Thanks,
Del
"ADSM: Dis
Charles,
DB2 backup to TSM is owned by the DB2 product team.
I did pass this question on to them, this was the response:
> There is a potential for a hang if the online backup had to retrieve
> a log file from the TSM tape pool, but backup is using all of the
> tape drives. IBM DB2 is currently
Gerald,
Version 1.1.1 used a different command-line syntax.
You should just be able to issue the "ADSMQUERYDB" command
and redirect the output to a file.
For example:
EXCDSMC /ADSMQUERYDB:* /ADSMPWD:password > OUTPUT.TXT
Thanks,
Del
>
Bill,
Domino ACL's are not "touched" by DP for Domino.
They are completely managed by Domino.
By the way, the Domino server needs to be
able to open each database, otherwise it
cannot manage (back up, compact, etc.) the database.
I suggest opening a PMR. If this problem
is recreatable, DP for Do
Paul,
Data Protection for Domino tried to read through the database,
and encountered a read error. How did the Notes team
"check this particular DB"? If they simply "open" the
database, it does not read each page of the database
like a backup must do in order to back it up.
So, it may not have rea
ownloadable from the Passport Advantage web site.
Thanks,
Del
------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
t Exchange Server
Installation and User's Guide" is available with this package.
- APAR fixes
The upgrade is available from ftp.software.ibm.com.
Thanks,
Del
------------
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
Thomas,
Take a look at DP for SQL "/STRIPes=numstripes" option.
DP for SQL allows you to send separate streams called stripes.
This is normally done for performance reasons, but could
also be used for splitting the backup into smaller objects.
SQL 2000 allows up to 64 separate striped objects.
For
John,
Yes. I know what the problem is.
The answer can be found in the IBM Knowledge Base.Go here:
http://www-3.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforDatabases.html
and search for "ANS1017E".
It will come up with 1 hit.. reference# 1114216.
In a nutshell... you n
Gerald,
The versions for Data Protection for Exchange
thus far have been:
1.1.0 - 4/1998
1.1.1 - 11/1999
2.2.0 - 3/2001
5.1.5 - 10/2002(VRML aligned with base client)
5.2.1 - 9/2003
The version jumped from 2 to 5 to align with the base TSM products.
Please read the
Gerald,
No. This won't work.
Well, it won't work unless you are using the same TSM NODENAME
for all of your Exchange Servers.. which I don't recommend.
The command below will query all of the Exchange Server backups
that appear under the NODENAME that you have in the DSM.OPT file.
The "/FROMEXC
Bo,
With DP for SQL 5.2.1, it picks up the locale
from the machine setting. You are running in a locale
that is not supported. i.e. Danish, and so it is
giving you the warning and then continuing in English.
The following note is in the README:
Limitation:
If you run Data Protection for
Fabrice,
It depends on the state that the restore was left in.
Data Protection for Exchange will allow you to just
restore an incremental backup assuming the database restore
was successful AND left in a proper state which is uncertain
in the situation that you describe. You can try the increm
Thomas,
The TSM API does not support encryption.
Thanks,
Del
> We may have to start encrypting backups of some files. It is clear
> that we can do this for backups created by the backup/archive client.
> Does the TSM API provide the same enc
Brian,
Data Protection for Domino does not yet "officially" support
Windows 2003 yet. As you know, Lotus is just now adding their
"official" support for Windows 2003. The Data Protection for
Domino test team is in the process of testing this configuration.
If I recall correctly, Lotus is adding "
Bill,
Try this:
1.) On the TSM Server, issue the UPDATE NODE command:
UPDATE NODE nodename password
2.) Make sure PASSWORDACCESS is set to GENERATE.
3.) On the machine running Data Protection for Domino,
issue the following command:
DOMDSMC QUERY ADSMSERVER /ADSMPWD=pass
Bill,
Something sounds amiss here.
Please call IBM support.
Thanks,
Del
> Thanks Del, I tried but same error message. I had been trying domdsmc q
> adsm -adsmpwd=password and getting the same error. I even tried
> capitalization and still
David,
The underlying backup code is identical for the command-line
and GUI for Data Protection for Exchange.
I agree something doesn't sound right. I would take a closer
look at the logs for both Data Protection for Exchange and
the TSM Server to make sure the same data and same amount
of data w
Sebastian,
errno = 10054 is WSAECONNRESET. It means that the TCP/IP connection
was reset and the socket was closed, terminating the backup.
This normally points to some type of network related issue.
While logged on to the same ID that shows the failures,
try using FTP to transfer some files (both
Joni,
I am not quite sure I understand completely since for Domino,
each database is contained in a single .NSF file...
...unless you are talking about groupings of Domino databases
making up a logical database of some sort (like Domino.Doc)
Data Protection for Domino works at the database file l
Sebastian,
We have seen a hang like this recently when service has been applied
to the operating system. The fix for this has been to apply and/or reapply
the latest service packs to SQL Server. In most cases, this has been to
apply SP3 or SP3a to SQL Server 2000. I see that you are on NT4 and SQL
yi,
Microsoft has not yet been able to identify for us what was
changed that caused this. IBM support is still working with
Microsoft to try to identify specifically why this was happening.
It seems that after (re)applying the latest service packs,
this problem is resolved. And for most customers,
Sebastian,
I don't know for sure. I haven't seen the
configuration of your system. It could have
something to do with the default network path
connection to the SQL server... which may be different
when running from a different userid... if you have set
it up that way on your system. Maybe it uses
Zoltan,
I think Remco, Richard, and Ted probably covered the
things that could be wrong... if not.. let me know.
Thanks,
Del
> Back a while ago, when we first started doing Domino TDP backups, due to
> lack of disk space, the backups were di
Pattie,
RC=419 is an "internal error".
If the DP for Exchange log does not provide any further information,
try this:
1. Retry the operation that failed.
2. If the problem occurred during an incremental, differential,
or database copy backup, run a full backup. If the full
backup completes
Ameerul,
Try looking for a possible solution on www.ibm.com.
1. Go to "www.ibm.com"
2. In the upper right part of the screen, there is
a "Search" field. Enter the following in that field
ACD5130E
You will find some articles written that address this symptom.
Thanks,
Del
Tom,
First... I am assuming you are referring to
Data Protection for Exchange version 2 or higher.
Version 2 and higher use standard TSM policy management.
(Version 1 used different policy management.)
These settings basically mean that you will be
able to restore any full backup for that last 90
Tom,
VERExists
Specifies the maximum number of backup versions to retain
for storage groups/databases that are currently on the Exchange Server.
VERDeleted
Specifies the maximum number of backup versions to retain
for storage groups/databases that have been deleted from the
Exchange Ser
Gerald,
There was an old client called ADSMConnect Agent for Lotus Notes.
That worked at the item level, and was only supported on Notes 4.
Lotus introduced a backup API starting with Domino 5.
Data Protection for Lotus Domino supports Domino 5 and Domino 6.
The history of the releases looks like
Gerald,
> 1. Is it possible to restore those restores with the latest TDP for
> Notes (5.1.x)?
Yes.
> 2. Is it possible to restore those restores with the latest TDP for
> Notes (5.1.x) to Notes 6.x?
Yes. If you want to apply logs, you may have to use an alternate
partition to get the
Mehdi,
If you have a paid PD of a previous version 2.2 or 5.1.5,
you can install it first... so that you get the paid license
on your machine.. then install the 5.2.1 PTF package
over the top of it. That will work.
You will then be able to back up your Exchange 2003 server.
Thanks,
Del
Matt,
You are correct, this is an OS/SQL server issue.
You didn't say which SQL Server SP you were running...
We have seen a few problems lately when people have upgraded to
Windows SP4... and then their SQL backups would hang or fail.
This has been fixed by upgrading to SQL 2000 SP3a.
I am sure
John,
Try looking for a possible solution on www.ibm.com.
1. Go to "www.ibm.com"
2. In the upper right part of the screen, there is
a "Search" field. Enter the following in that field
ACO0057E
You will find an article written that address this symptom.
Thanks,
Del
--
Bill,
See my answers below:
>> Have a few TDP Domino questions. 1) Can you install the API, TDP
>> Domino software before Lotus Notes Domino is loaded on to the client?
Yes.
>> 2)reliant on question 1, is will the TSM API TDP agent dynamically add
the
>> Domino databases to its backup?
Data
Michael,
There is not much to go on here... but since the
"TDPEXCC QUERY TSM" command uses the TSM API, it appears
as if there may be a possible problem with the TSM API
installation or pathing. Take a look at the DSIERROR.LOG file.
If it does not give you any ideas on what is wrong, your best bet
Henrik,
The "MH - AddInName =" must be coming from the Domino Server API code.
That is not something Data Protection for Domino displays.
Domino Server 5.0.5 is very old. You should probably get to
the latest maintanence release of the Domino Server. I know they have
fixed quite a few bugs since 5
Mike,
This should work... but be aware that Data Protection for SQL 2.2.1
is an unsupported version of the product. You should obtain
the latest version, 5.2.1. You can go here to get the 5.2.1 version:
Site: ftp.software.ibm.com
Dir:
/storage/tivoli-storage-management/maintenance/tivoli-data
John,
You should be able to modify the scripts so that the call to
DOMDSMC does not use the "start /B" command. So , for example,
... instead of this:
start /B domdsmc selective * /subdir=yes /logfile=domssch.log >>
domsel.log
... use this:
domdsmc selective * /subdir=yes /logfile=domssch.
Paul,
I would upgrade to the latest Data Protection for Domino.
There have been a number of issues similar to this solved.
Go here:
Site: ftp.software.ibm.com
Dir:
/storage/tivoli-storage-management/maintenance/tivoli-data-protection/domino/v515
If the problem still exists, please call IB
Wira,
Go to this URL:
www.ibm.com
In the upper right of the screen,
enter the following near the "Search" entry box:
+informix +onsmsync +expire +logs +tsm
It will lead you to some knowledge base entries that
might help you. There is one called:
"Managing Informix logs that are
David,
There are many factors that could slow a backup down.
You should by trying to find out if this is a slow-down
in the network, TSM Server, tape mount wait, SQL Server, etc.
If you happen to be running Windows 2000 SP4, there is a known
problem that causes SQL Server backups to slow down and
Sal,
You must start the entire backup again.
Del
> We had a Full TDP for Exchange backup that was running since Thursday
(slow WAN link) fail with less than > 1GB to go. The ISP had a
> problem and we lost the WAN connection to the server.
>
Dave,
I find this to be a mix. That is, there are some customers
backing their SQL databases to disk first, then migrating
them to tape. There are other customers backing them up
directly to tape. There is no "correct" answer, because it
depends on your service level agreements, your TSM Server
in
Larry,
Data Protection for SQL 1.1.2 is quite old and out of support.
Normally, upward compatibility should work fine, but...
Without seeing the error messages that you are receiving,
it is hard to know what problem you are encountering.
Can you append the error messages that you see in the
Data P
Yiannakis
One thought... you should send the meta data to a
disk only storage pool. These meta data objects are always
very small (less than 100K)... and to put them to a
tape is not good for performance. You do that by binding
the meta objects to a management class that points to
a disk only stor
Greg,
Go to:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManagerforMail.html
and enter the following in the Search box:
exchange backup performance
There is an article (ID# 1144592) titled:
"Data Protection for Exchange On-line Backup Performance is Slow
that
Richard,
ACO5091E also is displayed when the password stored
is not correct. Try this:
1. Add "CLUSTERNODE YES" to the DSM.OPT file.
2. Reset the password on the TSM Server for the node you
are using for DP for SQL.
3. Issue a command that connects to the TSM Server
specifying the /TSMPASSWO
Hi Joe,
Did you get this straightened out yet?
The data to back up is sent from the SQL server
to Data Protection for SQL. And so, Data Protection
for SQL does not "decide" what data to back up.
The SQL Server determines this.
It is strange that the SQL Enterprise Manager backup tool
is acting dif
Richard,
Like you originally stated... strange.
One more thing to look at...
Go to www.ibm.com. In the upper right Search box enter:
"ACN5087E PASSWORDACCESS"
Make sure you put the double quotes around the search term.
It will show two knowledge base entries that describe the
problem you are
Koen,
There are a few things that can cause this:
Go to www.ibm.com. In the search area enter the following:
+"This database is currently being used by someone else" +backup
You will find some KB articles that discuss possible causes
and solutions to those problems.
Thanks,
Del
-
Douglas,
Once you start using Data Protection for Domino for backing
up your Domino databases, you do not need to back them up with your
TSM backup/archive client like you show in your example.
You should EXCLUDE them in your options file for the
TSM backup/archive client.
However, you will need
Mohan,
Try reinstalling the TSM API Runtime feature from the Version 5.1.5
(or later) TSM Backup Archive client package. If it still fails,
uninstall... then reinstall the TSM Backup Archive client and the
Data Protection for Exchange client.
Thanks,
Del
Henry,
This is not enough information to be able to help you.
The RC=418 indicates a TSM API error.
What appears in the DP for Exchange log file?
What appears in the DSIERROR.LOG file?
Thanks,
Del
> I have exactly the same problem but my env
Henry,
Make sure you have COMMTIMEOUT on the TSM Server set to a
high enough number to accomodate any Exchange activity
that may need to happen during backups. I would try setting
COMMTIMEOUT to 600 to see if that helps.
If that doesn't help... many times, "-50" errors mean there are
network prob
Joni,
The word "agent" is not used in the *real* product titles anymore.
But the legacy term has carried forward.
The Data Protection clients are separated into named categories:
IBM Tivoli Storage Manager for Mail
- Data Protection for Lotus Domino
- Data Protection for Microsoft Exchange
Eric,
You can bind the database backups to any management class
you would like. That is described in the User's Guide.
Here is an example:
INCLUDE \...\db1\...\* MC_9DAYS
INCLUDE \...\db2\...\* MC_14DAYS
INCLUDE \...\db3\...\* MC_28DAYS
INCLUDE \...\db4\...\* MC_168DAYS
Take a lo
Eric,
Actually... to make it easier... I would probably go one
step further.. i.e. to use a new NODENAME with a new
domain and new management classes. That way, the data for
the Version 1 backups stays separated.
But, what you said will work also... you just need to
be careful that when you assig
Yiannakis
RC=418 means there was a TSM API error. The DSIERROR.LOG file
should have something that explains what the TSM API thought
was the problem. Please look there. Also, look in the TSM
Server activity log file to look for a message that might
tell you what went wrong.
RC=402 is the general
Jure,
On Unix, you need to put wildcards in quotes.
So, try this:
domdsmc restore "*" /subdir=yes /into=/tmp/dominotest
Thanks,
Del
> What is the right thing to do?
> Where is an error?
>
> This is what I do.
>
>
> su - notes
> cd /notes
701 - 800 of 1716 matches
Mail list logo
