Sal,
The level of granularity for Exchange backups is at the
Storage Group level. That means you can run backups
of separate Storage Groups simultaneously.
For example:
start tdpexcc backup SG1 full
start tdpexcc backup SG2 full
start tdpexcc backup SG3 full
start tdpexcc backup SG4 fu
Jeff,
This looks to be a userid and/or AD issue. It looks like
something changed in your environment that caused the
VDI creation functions to fail due to lack of security.
Have a closer look at the userid being used to run the
backup to see if something has changed recently in
regards to securit
There was one question that I will comment on below.
I don't need to address the others since Mark answered
them brilliantly.
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 08/18/2004
12:07:53 PM:
>.
>.
>
> One document I
Luc,
Is a full backup "enough" for what?
A Data Protection for SQL "FULL" backup can be used to
restore a complete database. When a full backup is
taken it also captures pieces of the log that it needs
to fully recover the database. You do not need a
separate "LOG" backup in order to perform a da
Bill,
It looks like you have not set up the "alternate" server properly.
The message is telling you that the Domino server thinks that
there is a different transaction logger id in effect.
However, when you follow the alternate server restore procedure,
there initially won't be logging at all unti
Luc,
It looks fine... as long as:
- "" is a TSM NODENAME that you
have registered and received a password for.
- "{IP TSM SERVER)" is actually the TCP/IP address
of the TSM Server where the "" NODE is
registered.
Thanks,
Del
--
Bill,
There must be residual data or partial steps that
are causing the Domino logger code to think that
logging is in effect.
My suggestion is to start with a fresh "alternate" server
with clean directories. Follow the steps in the documented
procedure from the beginning. It is difficult to figu
Eric,
Deleted databases do not "automatically" get inactivated.
You must manually inactivate them.
>From the command-line interface, use the TDPSQLC INACTIVATE command.
It is very similar to the RESTORE command.
Enter TDPSQLC HELP INACTIVATE to see the exact syntax.
>From the GUI, go to "View",
Henrik,
As you know, an active log backup will never expire.
The only way for the "35" day countdown to start, is to
inactivate the log backup. A log backup will only be inactivated
if there is no active database backup that requires that log
and then the INACTIVATELOGS command is run.
It sounds l
Jason,
It sounds like you set up the schedule definition incorrectly.
It needs to be an COMMAND type schedule that specifies
a batch file on the Exchange server machine that launches
Data Protection for Exchange. There are sample batch files
shipped with Data Protection for Exchange.
If you look
rc=1837 means you have all objects excluded from backup.
In looking at your DSM.OPT file, you have:
EXCLUDE "*\...\*"
This is the problem.
You don't want to EXCLUDE items in the DSM.OPT file
for Data Protection for Exchange... and if you do.. you need to follow
the example i
Jason,
You don't need to put anything in the DSM.OPT file.
By default, Data Protection for Exchange will back up the
Information Store and Directory under Exchange Server 5.5.
If you want to bind those objects to a special managament
class, then you should add something like this:
INCLUDE * M
Hi Matt,
Have you tried backing the storage groups up in parallel?
For example, assuming you have four storage groups, you can start
a separate instance of the Data Protection for Exchange
command-line interface to back up each storage group at the same time.
Thanks,
Del
---
Matt,
A few things to keep in mind:
* Exchange restore will almost always be slower than backup
because you are writing to disk and more importantly you are
replaying transaction logs.
* If you back up to tape and you run COLLOCATION by filespace,
it will keep the data for your separate st
Moses,
Many of the answers here come from a general
understanding of SQL Server backup/restore strategy.
Here is some very good reading material for you:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_bkprst_4l83.asp
As far as a Data Protection for SQL impact, you
Data Protection for SQL creates a separate TSM Server session
for each stripe and then waits for the SQL Server to send data
to each stripe. The SQL Server determines which data goes
to which stripe, and writes the data to it.
>From what you have put into this append, it appears as if
sending the
James,
Mark is correct that there is no TSM "archive" function
for Data Protection for Exchange. However, there are a
few things that many customers have done:
- Set up a special NODENAME (like EXCHSRV1_ARCHIVE) that
will bind the backup objects to special management classes
that meet your desire
Luc,
Yes. If using the GUI, after selecting the database on the restore tab
use the right-mouse button on the database entry in order
to enter the new database name... and also to choose the
locations for the new database files.
You can also do this from the command-line.
You might find some other
Mark,
This might mean that you are running this under a userid
that does not have enough permission. What userid do you
have the scheduler service running under? Is it the same
userid that you successfully ran the GUI? If not, try changing
the scheduler service to run as a userid that has enough
Bill,
I am not exactly sure what you are trying to do here,
but you can run Data Protection for Domino commands
even when the Domino Server is not running.
As long as there are no problems, the ARCHIVELOGS command
will work and it will back up the logs that are ready.
Again, if there are no intern
Jeff,
I haven't seen this specific HRESULT code before.
I also don't see this message in SQL Server error codes,
(HRESULT converted 55F3 = 55F0 + 3 = 22000 + 3).
This may be a case where the SQL Server hit an unexpected error
and passed that back to Data Protection for SQL (resulting in
the "Messa
David,
It looks like you are seeing APAR IC30018... which is fixed.
That was fixed quite a while ago in version 2.2.1.
You are running 2.2.0. You should obtain Data Protection
for SQL 5.2.1 and try this operation again.
You can also go to www.ibm.com and search for:
+tdp +sql +restore +alternat
Zoltan,
How many stripes were used to back up the database?
How many stripes are you using for the restore?
Data Protection for SQL opens a separate TSM Server session
for each stripe.
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]
Zoltan,
Data Protection for SQL allows you to increase throughput
of your backups and restores my creating multiple streams
via multiple TSM API sessions with the TSM Server.
As Richard noted, you can look at IBM KB article 1145253 for details.
It is also documented in the User's Guide.
The GUI "
Zoltan,
No... there were things added. (See README for details.)
In addition, if you backed up with newer version,
and tried restoring with an older version (like 2.2.1),
there could be problems with meta data alignment,
which might result in weird stripe values.
Bottom line, make sure you are run
Marc,
Sorry, the book is misleading.
Data Protection for Exchange works in both Active/Passive and
Active/Active!
As a rule of thumb, if something supports Active/Active,
it also supports Active/Passive since Active/Passive
is a simplified case of Active/Active.
It works just fine.
Thanks,
De
Zoltan,
I am sorry your "SQL guy" is having trouble.
When restoring to an alternate server with alternate
locations, you need to specify each piece that you
are restoring, including all logical and physical
pieces involved in the backup... this is a SQL Server requirement.
If the IBM KB article c
Tim,
You can also set up different management classes for your
incremental backups. Look in chapter 3 of the 5.2.1 User's Guide
under a section titled:
"Data Protection for Exchange Version 5.2.1 INCLUDE/EXCLUDE Processing"
It explains how to set this up.
Thanks,
Del
Norman,
If this happened by the Storage Group getting renamed, try this
Data Protection for Exchange command:
C:\Program Files\Tivoli\TSM\TDPExchange>tdpexcc help inactivate
IBM Tivoli Storage Manager for Mail:
Data Protection for Microsoft Exchange Server
Version 5, Release 2, Level 1.0
(C) Cop
Lucian,
dsm.sys is the file on UNIX that contains the stanzas.
You would add a new option: "NODENAME domserv1", for example.
For more details on dsm.sys, you can look at:
"IBM Tivoli Storage Manager for UNIX
Backup-Archive Clients Installation and User?s Guide"
Thanks,
Del
-
Jon,
The requirements as noted in the README file for
Data Protection for Exchange 5.2.1 are:
- IBM Tivoli Storage Manager Server 5.1
You do not need to be running a 5.2 TSM Server.
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTE
Moses,
You need to restore the full backup prior to restoring the
differential backup. Try the operation again by restoring
the full backup and differential backup.
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/20/200
Moses,
The relocate dialog box could be empty if the meta
data objects have migrated to tape and you have the
checkbox turned off for waiting for tape mounts for file info.
(The default is off.) If this happens, it may also mean that
you should revisit your management class information.
You should
Joerg,
What other "TSM agents" (also called TDPs) do you think
that you can encrypt with? You can COMPRESS with all of them...
because it is done in the TSM API... which the "TDPs" use.
But, the TSM API does NOT support encryption quite yet. However...
watch this space... because this is a known
Bo,
Go to:
http://www.ibm.com
Under the Search box enter:
+sharepoint +portal +backup
There is a Knowledge Base article titled:
How do I back up Microsoft's SharePoint Portal Server?
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL
Joerg,
The URL you sent is discussing function of the standard file-level client.
This does not apply to the specialized Data Protection clients.
However... nothing "officially" announced yet.. but look for this
in the upcoming release.
Thanks,
Del
--
Sergey,
One (1) TSM node with three (3) schedules is how
you should set this up.
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> wrote on 10/25/2004
05:35:26 AM:
> Hello all!
>
> I want make full + diff + log backup of SQL database
Gerald,
When you say "Full".. do you mean backing up all
databases using "DOMDSMC SELECTIVE"?
And when you say "INCREMENTAL", do you mean using the
"DOMDSMC INCREMENTAL" command?
... or when you say incremental are you referring to
running DOMDSMC ARCHIVELOG to get the logs backed up?
Remember...
Nick,
Was this a restore across different Domino servers?
What was the version of the Domino server that you took
the backup on and what was the version that you are
performing the restore on?
Was this a restore across different OS platforms?
Was this a logged database? Did you apply logs to the
d
Robert,
After verifying that you are performing log backups
with "/TRUNCate=Yes" (the default is Yes), make sure that
the log backups are succeeding by looking at the Data Protection
for SQL Log file. If they are succeeding, then here
are a few other things to look at:
Is the log backup size also
Rachel,
There is not a native TSM BA Client or scheduler for OS/400.
Are you using Data Protection for Lotus Domino to perform your backups?
What tool did you use to set up automated scheduling?
Thanks,
Del
"ADSM: Dist Stor Manager" <[EMAIL
-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Del Hoobler
> Sent: 28 October 2004 13:35
> To: [EMAIL PROTECTED]
> Subject: Re: TSM on AS/400
>
>
> Rachel,
>
> There is not a native TSM BA Client or scheduler for OS/400.
> Are you using Dat
Gerald,
A few points and comments:
- Keep in mind that the Domino transaction log is one large
logical log file (in 64M segments) that contains entries
for each and every logged database. It was built for
not only built for crash recoverability... but also to
enhance performance during st
Rachel,
By default, the log file name is "DOMDSM.LOG".
This log file contains operation parameters and summary statistics.
It does not contain a list of each database processed.
You can obtain that by looking at the redirected command output.
Thanks,
Del
Rachel
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Del Hoobler
> Sent: 29 October 2004 16:17
> To: [EMAIL PROTECTED]
> Subject: Re: TSM on AS/400
>
>
> Rachel,
>
> By default, the log file name is "D
James,
With Exchange 2003 you have a few ways to solve this problem:
1 - Use the Recovery Storage Group feature of Exchange 2003.
Microsoft added this feature specifically for this purpose.
Here is how to get some documentation from Microsoft that explains it.
Go to www.microsoft.com
Moses,
Yes... you have the basic idea. I would recommend adding
a scheduled log backup to this as well. There is a section
in the Data Protection for SQL User's Guide, Chapter 1, called:
"Data Protection for SQL backup strategy considerations"
that explains the different backup strategies and when
Rick,
In regards to Exchange Journaling...
As I understand it, Exchange journaling works by allowing you to
set up a separate mailbox to receive a copy of all email that is sent.
Since that specially-created mailbox is a normal Exchange Server
mailbox, it is eligible for standard backup and restor
Sandra,
With a RC=1 in the scheduler log, I am guessing that the scheduler is
failing to launch the batch file correctly. Search through the
archives of this list as well as through the IBM knowledge base
for reasons for this. A common reason is that the ACTION=COMMAND
schedule has an incorrect OB
Joshua,
Check that the schedule service is running under a userid that
has the proper permissions to back up SQL Server. If it is running
under the standard system account, it probably doesn't have proper
access to the SQL server. The Data Protection for SQL User's Guide
discusses the permissions
Ray,
This return code and message is coming from the Exchange Server itself.
>From the Exchange message file (esebkmsg.h, in the Microsoft API):
//
// MessageId: hrErrorFromESECall
//
// MessageText:
//
// Error returned from an ESE function call (%d).
//
#define hrErrorFromESECall
Hi Eric,
Does the cluster think the machine is down and performs a failover?
If so, you may need adjust the Cluster Heartbeat Settings.
You will see a number of google hits for the same thing with
VMware Exchange DAG cluster snapshots.
Some of the values VMware recommends changing are:
* SameS
Hi Daniel,
> - Is it possible to do Incremental VSS backups of an exchange database?
Yes. When you do this, you get a snapshot of the log LUN.
If you keep them as "LOCAL" persistent snapshots, the logs
are copied from the snapshot to the source drive at restore time.
> - How do I get FCM to backu
Hi Daniel,
I am not sure if this is a mail glitch or you did not see my answer
from yesterday, but here it is:
http://www.mail-archive.com/adsm-l@vm.marist.edu/msg96157.html
Del
"ADSM: Dist Stor Manager" wrote on 01/14/2014
10:23:34 AM:
Hi Daniel,
As usual, it all depends... :-)
If you plan to keep LOCAL snapshot backups and you plan
to leverage hard-based snapshots, then many hardware-based
snapshots support "space-efficient" snapshot LUNs,
where it only requires space for the changes blocks.
And so, you need to look at the har
Hi Daniel,
You are welcome! I am glad I was able to assist.
As for the DAG cluster, there are some good sections
in the User's Guide that discuss the best practices for DAGs.
I recommend looking at the DP/Exchange 7.1 book, even though
you said you were staying at FCM 3.2 or DP/Exchange 6.4
becau
Hi Wanda,
I have a few ideas for you...
--
Are you running in a DAG environment? If so, you could do some
load balancing between DAG Servers:
Most of this in the Exchange book under "Managing Exchange Database
Availability Group members by using a single policy":
http:
Hi Steve,
See if this helps:
http://www-01.ibm.com/support/docview.wss?uid=swg21597023
BTW... this is a known requirement. There are plans to add
this function directly to the launch of the MMC soon.
Thank you,
Del
"ADSM: Dist St
; > to something that promises a brand new approach. Time will tell if
the
> > reality matches the glossies, but this is exactly the sort of reason
why
> > they leave.
> >
> > Spleen vented, submerging again,
> > Steve
> >
> > Steven Harris
> >
ise quality engineering.
> -steve s
>
> -Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Del Hoobler
> Sent: Thursday, February 13, 2014 12:59 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] TDP for SQL 6.4.1 cross-s
Hi Neil,
Please look at the archives of this list from last week.
This exact discussion was raised.
Here is the discussion thread:
http://adsm.org/lists/html/ADSM-L/2014-02/msg00019.html
I mentioned in that thread that a fix for this is targeted
for the DP/SQL 7.1.0.1 iFix. Current estimate i
Hi Remco,
It's difficult to see what might be going on here.
My first suggestion is to open a PMR to get the ball rolling on that.
While that is progressing, you could try to use the RESTOREFILES command:
http://pic.dhe.ibm.com/infocenter/tsminfo/v6r4/topic/com.ibm.itsm.mail.exc.doc/dpe
"ADSM: Dist Stor Manager" wrote on 02/19/2014
07:10:09 PM:
> From: Remco Post
> To: ADSM-L@vm.marist.edu,
> Date: 02/19/2014 07:10 PM
> Subject: Re: exchange 2007 and TSM for mail 6.4
> Sent by: "ADSM: Dist Stor Manager"
>
> Op 19 feb. 2014, om 20:5
No apology needed Neil! These questions are easy to answer! :-)
Del
"ADSM: Dist Stor Manager" wrote on 02/20/2014
11:51:38 AM:
> From: Neil Schofield
> To: ADSM-L@vm.marist.edu,
> Date: 02/20/2014 11:57 AM
> Subject: Re: Pointing FlashCopy
Hello Yann,
If you are using Exchange Server 2013, we recommend that you upgrade to
Data Protection for Exchange 7.1. It has additional capabilities, such as:
- Multi-language support in mailbox restore browser GUI
- Mailbox restore browser restore to Unicode PST files
- Mailbox restore browse
Hi Jerome,
You do not need an extra license. But I do recommend installing
a newer version of Data Protection for Exchange. For example...
version 6.4.1:
ftp://public.dhe.ibm.com/storage/tivoli-storage-management/maintenance/tivoli-data-protection/ntexch/v641/windows/
or
version 7.1.0.1:
f
Hi Wanda,
In case you didn't know... the Data Protection for Exchange
Mailbox Restore Browser gives you the option to leave the
recovery database around for future restores,
so you don't need to restore it each time.
Data Protection for Exchange detects if there is an existing
recovery database. I
Hi David,
That was initially added in Data Protection for Exchange 6.3.
Del
"ADSM: Dist Stor Manager" wrote on 03/10/2014
02:32:36 PM:
> From: "Ehresman,David E."
> To: ADSM-L@vm.marist.edu,
> Date: 03/10/2014 02:33 PM
> Subject: Re: Exch
Hi Geoff,
This looks like an Exchange environment issue.
Google shows a few possibilities, for example:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/77e12e05-9c64-46dd-81a3-167411a6c7f5/the-wsmanagement-service-cannot-process-the-request-the-user-load-quota-of-214748367-requests
Hi Bill,
This is something that is being worked on now.
We are targeting Data Protection for Exchange 7.1.1 later this year.
If you are interested in being a part of the beta program to
test this now, please let your IBM rep know and we can
get you signed up.
Thank you,
Del
Hello Hans Chr.,
RC=1829 means "nothing to back up"... so yes, in this case,
the backup should be performed using one of the passive copies,
assuming you have backups running on the servers with the
passive copies.
The incremental backup can be done from the active copy or
any passive copy.
You
Microsoft does not support restoring VSS backups
into a SQL Server that has a different name.
This is a Microsoft restriction and is
documented in the Data Protection for SQL User's Guide.
Thank you,
Del
"ADSM: Dist Stor Manager" wrote on
Hi Geoff,
This can happen if Windows Management Framework 3.0
is installed, but you haven't upgraded to Microsoft Exchange
Server 2010 Service Pack 3 yet.
Is SP3 installed for Exchange Server 2010?
Thank you,
Del
"ADSM: Dist Stor Manager"
Hi Remco,
Judging from these similar posts...
http://social.technet.microsoft.com/Forums/exchange/en-US/3736df82-e5cb-4665-a97c-eb4a70868271/information-store-database-buffer-paged-during-backup?forum=exchangesvravailabilityandisasterrecoverylegacy
http://www.experts-exchange.com/Software/Serve
Hi Harry,
In the DSM.OPT file... do you really have this?
INCLUDE.VMTSMVSS
or does it actually have the real VM name in there, something like:
INCLUDE.VMTSMVSS MAILSERV15
It needs to be the real VM name.
(I can't tell if you changed the messages to protect the real names
or the messa
Hi Harry,
This looks like a bug that was fixed. It is fixed in the 7.1 client
package.
If you do not want to upgrade to 7.1, it will be fixed in the
6.4.2 PTF coming out this summer.
Del
"ADSM: Dist Stor Manager" wrote on 05/02/2014
04:41
Hi Eric,
No. You should just be able to use legacy style backups.
My guess is that the configuration wizard inadvertently
added some entries causing this.
Check the tdpsql.cfg file.
1. Remove the LOCALDSMAGENTNODE entry (if there is one.)
2. Make sure the BACKUPMETHOD is:
BACKUPMETHOD LEG
rough the wizard the LOCALDSMAGENTNODE
> line is added again... The backup method is set to legacy in the
tdpsql.cfg
> Thank you very much for your help!
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
>
>
> -Original Message-
> From: ADSM: Di
Hi Eric,
I agree. There is a fix for it and it is being tested now.
It is targeted for the 7.1.0.1 interim and will be available
once the testing has completed.
If you decide you need an immediate fix, you can always open
a PMR and ask for a patch.
Del
--
Hi Geoff,
Ray and Wanda are correct. (See their answers.)
As for the "Platform" changing... it has to do with the fact the scheduler
connects
as the "TDP" node and changes it to "WinNT" and then DP/Exchange connects
and
changes it to "TDP MSExchg". This is a known issue which is on the list to
re
Hi Zoltan,
I recommend opening a PMR if you haven't already done so.
Thank you,
Del
"ADSM: Dist Stor Manager" wrote on 05/20/2014
12:55:44 PM:
> From: Zoltan Forray
> To: ADSM-L@vm.marist.edu
> Date: 05/20/2014 12:56 PM
> Subject: compre
Hi Wanda,
Check this out:
http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx
Pay close attention to the text in the yellow box which states:
Update 9/19/13: A side-by-side coexistence of PowerShell 3.0 and
PowerShell
Hi Jerome,
TSM 5.5 (and 6.1) are out of service as of April 30th.
http://www-01.ibm.com/support/docview.wss?uid=swg21635108
unless you purchased a support extension.
The latest version of Data Protection for Exchange with the
most efficient mailbox restore features is Data Protection for
Hi Steve,
This is APAR IT00973:
IT00973: TEMPORARY XML FILES NOT DELETED AFTER 'BACKUP VM'
The fix is not yet available...
Until the fix is available, it is safe to delete these
-vss_manifestsxx.zip_unzip directories and their
contents after the backup is completed.
Thank you,
Del
--
Hi James,
They are not the same product, but have some similar functions.
Fastback for Exchange is for performing IMR (mailbox-level and
item-level restore) from Exchange files (.EDB and .LOG).
Data Protection for Exchange has the ability to perform
database-level backup and restores, and IMR res
You could also consider using FlashCopy Manager Custom Application support
where you can use snapshots and leverage exit points to quiesce/resume
the application.
Here are some example scripts:
http://www-01.ibm.com/support/docview.wss?uid=swg21568342
Thank you,
Del
There is no IBM document for this.
You need to work with your IBM account team to make sure
you are getting the answers you need to stay compliant.
Del
"ADSM: Dist Stor Manager" wrote on 05/29/2014
01:57:41 PM:
> From: Martin Harriss
> T
Hi Hans,
I agree with you. Please open a PMR.
Del
"ADSM: Dist Stor Manager" wrote on 06/05/2014
05:45:50 AM:
> From: Hans Christian Riksheim
> To: ADSM-L@vm.marist.edu
> Date: 06/05/2014 05:46 AM
> Subject: Re: SQL-backup with no config fi
Hi Mike,
Yes. This is possible. There are a number of customers doing it.
This might help you:
http://www-01.ibm.com/support/docview.wss?uid=swg21253263
Thank you,
Del
"ADSM: Dist Stor Manager" wrote on 06/13/2014
09:35:55 AM:
>
Hi Leif,
The .ctl and .dat files are underneath a "group leader" object. The
management class
of the group leader is what defines the policy for all children objects.
Also keep in mind that when you rebind the MC, it will change the policy,
but will not change the copy destination of objects alrea
Hi Neil,
You cannot use the current version. It is not officially supported.
The target is 3Q for SQL Server 2014 support with Data Protection for SQL
7.1.1.
Del
"ADSM: Dist Stor Manager" wrote on 06/24/2014
11:30:34 AM:
> From: Neil Schofi
to the next line?
>
> I did submit the issue in the comment section, but as it is will
> leave many hanging
>
> Thanks
>
> ~Rick
>
>
>
>
> -Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
> Behalf Of Del Hooble
Hi Steve,
Domino and Exchange are different, so don't try to
manage their backups in exactly the same way.
You can certainly have different management classes for
your FULL (database and logs) backups vs.
your INCREMENTAL (logs only) backups.
INCREMENTAL backups will inactivate when a new FULL
ba
Just for clarification...
Yann said this:
"Furthermore, it seems as if the integrity check is not made,
Exchange will not purge its logs."
This is not accurate. Exchange will purge its logs when a
FULL or INCREMENTAL backup completes successfully
(and when the logs have been shipped
>>> Response appended on behalf of Thomas Prause
BRBACKUP thinks that RMAN has not saved all objects:
BR0522E 112 of 108 files / save sets processed by RMAN
If you disagree you may open an incident at SAP. BRBACKUP
belongs to SAP BR*Tools and is not part of TSM for ERP.
(All messages prefixed w
Hello,
This falls into the same install code as
the BA Client and APAR IC92587.
http://www-01.ibm.com/support/docview.wss?uid=swg1IC92587
Del
"ADSM: Dist Stor Manager" wrote on 07/22/2014
09:31:00 PM:
> From: Erwann SIMON
> To: ADSM-
Hi Steve,
You pretty much hit the nail on the head.
For your use case, legacy backup still offers the simplest
and most versatile solution. Since you don't have an
immediate need for leveraging hardware snapshots
or offloadeded backups, you don't need to use VSS.
For SQL Server, legacy backups (VD
Hi Gary,
We are very aware of this requirement.
1. What are your top use cases for this environment?
2. What % of VMware vs. Hyper-V do you have?
3. Are you migrating from one to the other? ... or do you foresee keeping
both?
Thank you,
Del
--
Hi Keith,
FULLvm and FIle are only for VMware.
Details on what they do in a VMware environment can be found here:
http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.doc/c_bac_usingvcb.html
For Hyper-V, as of today, HYPERVFULL is the only option available for
VMBACKUP
Hi Jerome,
I am not an expert on TSM Server rollbacks, but here are
some options that I can think of:
- Restore your TSM database back to before the backup with the shorter
policy.
This has ramifications that I am sure you are aware of.
- If your data is on tape, and the tapes have not been wr
901 - 1000 of 1716 matches
Mail list logo
