Hi all,
I think we all agree that backing up this dedup cache fiche is useless and that
it can considered as as a best pratice to exclude it since trying to back it up
generate retries.
Stephan is right when it writes that almost nothing is excluded, except this
.TsmCacheDir directory (and
Ha, I didn't know that! I guess there is one directory excluded by default.
Thanks for pointing that out.
On Mon, Feb 26, 2018 at 10:59 AM, Martin Janosik
wrote:
> Hello,
>
> your presumtion doesn't seems accurate to me (Windows, Linux, AIX clients,
> mostly v7.1):
>
Hello,
your presumtion doesn't seems accurate to me (Windows, Linux, AIX clients,
mostly v7.1):
tsm> q inclexc
*** FILE INCLUDE/EXCLUDE ***
Mode Function Pattern (match from top down) Source File
- -- -
No exclude filespace statements
For as far as I know nothing is excluded by the code itself and I think
this is a policy thing.
Since you can install the software in different locations and you can use
different names for different files (ie log files) IBM can never be 100%
sure that the file it is hardcoded to exclude is the
Hi Rick,
Yes, this is what I always do. But I was wondering why it's not excluded by the
code itself.
--
Best regards / Cordialement / مع تحياتي
Erwann SIMON
- Mail original -
De: "Rick Adamson"
À: ADSM-L@VM.MARIST.EDU
Envoyé: Vendredi 23 Février 2018
Erwann,
I have client option sets defined on the server that I use to globally exclude
it from all file level backups.
-Rick Adamson
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann
SIMON
Sent: Friday, February 23, 2018 1:14 AM
To:
Hi all,
I'm wondering why the dedup cache file (TSMDEDUPDB_servernamenodename.DB,
located in the dedupcachepath directory) is not excluded by default ?
I generally exclude it because it causes somes retries and do think that
there's no need to back it up. But I may be wrong.
So, must we really