Hi,
Have you got purge your VSS snapshot ?
vssadmin delete shadows all
Best regards,
Yann
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Robert
Ouzen
Envoyé : dimanche 15 septembre 2013 07:08
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TDP
Hi Robert,
You may need to reboot the Exchange Server
if restarting the Information Store does not clear it.
If a reboot does not work, I recommend opening a PMR.
Thanks,
Del
ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 09/15/2013
This is mostly a gripe at IBM..
Why do the Windows clients allow themselves to be installed on
non-supported OS/levels? or at least issue warnings?
My Windows folks (yes, they are being lazy and not reading all the
readme/docs), are constantly installing miss-matched/not supported
I agree it shouldn't be that way.
Anybody ever put in an RFE for that?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: Monday, September 16, 2013 9:34 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Windows Clients and
I guess it must be at 6.4.0.1+ since 6.4.0.0 is what is installed!
On Mon, Sep 16, 2013 at 11:34 AM, Prather, Wanda wanda.prat...@icfi.comwrote:
Thanks Andy!
!Will save me generating another RFE..!.)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
Like I said - they didn't even bother to read the read-me links which would
have told them not to - some of these folks also installed 6.4 clients on
machines that were being backed up to a 5.5 TSM server (now upgraded to
6.3), paying absolutely no attention to my warnings/messages that this
Your users install .0.0 code?!?
On Monday, September 16, 2013, Zoltan Forray wrote:
I guess it must be at 6.4.0.1+ since 6.4.0.0 is what is installed!
I have the same gripe myself. ;-) For that reason APAR IC89603 was opened
to prevent later 6.4 levels from being installable on Windows 2003, and
this is something we will pay more attention to in future.
Best regards,
- Andy
Thanks Andy!
!Will save me generating another RFE..!.)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew
Raibeck
Sent: Monday, September 16, 2013 11:32 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Windows Clients and Non-Supported OS
I solved this problem by publishing install instructions that point to a batch
installer. I control the version in the batch and the batch detects the
Windows version and installs the correct version.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager
Well, now I have the user/administrator asking if they can/should upgrade
the 6.4.0.0 client (and how-high)? Can't really back down since this
server has 21TB / 26M objects in backup. It would require starting all
over from scratch.
Of course, since 6.4.0.1 now detects the OS level and prevents
I can definitely understand the gripe. However, I think I should have
the option of installing something in an unsupported fashion, if I
that's how the risk/reward equation balances out for me.
For those submitting RFEs, please consider also mentioning a
--unsupported or --noprereqcheck for
Easy - tell the Windows Engineers to upgrade the O/S to W2K8-R2 on all the
servers they installed TSM 6.4 on!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: Monday, September 16, 2013 11:57 AM
To: ADSM-L@VM.MARIST.EDU
That is pretty much what I did. This was my response to them:
*Like I said, any client 6.4.0.1 and higher WILL NOT install on a W2K3 box!
You are stuck/screwed. Your choices are:*
*
*
*1. Upgrade the OS to 2008+*
*2. Replace (uninstall/reinstall) client with highest supported client
(6.3.1.2)
14 matches
Mail list logo
