Dear Del,
Your are the best thank you for the commitment to the list over the past years.
Your postings on the list got me out of sticky situations more than once.
A big thank you!
Best Regards,
Koen
-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens
I Just solve this issue for another customer.
Search for gpfs.dll on your Windows Server.
Search for GPFS.DLL in your Trace File you created that Stefan talking about.
Verify if the path is the same, if not. Then just copy that file from the path
you find in your DOS windows and copy to the pat
Looks like I won't be going to v7 for a while. I have v5 clients still active
with no end in site.
I am upgrading from 6.2.5 on RHEL 6.1. What is the wisdom of the group, go to
6.3.x or 6.4.x?
We do no dedup here and have no plans for it.
However,we do use tsm for ve.
Thankns for any help.
Just to keep things confusing, IBM includes TSM server v6.3.4 in the v6.4
release. AFAIK there is no true v6.4 server release. v6.3.4.300 has been
working great for us on the server side.
On Mon, Feb 02, 2015 at 05:31:48PM +, Lee, Gary wrote:
> Looks like I won't be going to v7 for a while. I
Roger,
According to my TSM Data Protection for SQL 6.4 manual, servers that run TDP
for SQL require backdelete authority. I don't know how to get around this
problem.
Jim Schneider
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger
Desch
Same goes for Oracle and Notes backups. They manage their own backups so
no way to get around this. Same goes for PASSWORDACCESS GENERATE - AFAIK
can't schedule backups without it
On Mon, Feb 2, 2015 at 12:44 PM, Schneider, Jim
wrote:
> Roger,
>
> According to my TSM Data Protection for SQ
We upgrade everything from 6.3.4.300 to 6.3.5.100 - only complication being
the Linux kernel semaphore issue which is highly aggravated due to the
change in DB2 levels that came in with 6.3.5 - still waiting for RedHat to
patch this. RedHat just released a kernel update with 3-semaphore patches
bu
Can Schedule an admin schedule around the Oracle/Notes backup window to
enable/disable BACKDEL=YES/NO.
It is not an ideal situation, but decreases the risk. And if you configured
these nodes with specific nodenames (like you should) the malware could not
get to those clients.
Or they should scan t
> Op 2 feb. 2015, om 18:44 heeft Schneider, Jim het
> volgende geschreven:
>
> Roger,
>
> According to my TSM Data Protection for SQL 6.4 manual, servers that run TDP
> for SQL require backdelete authority. I don't know how to get around this
> problem.
Mitigated by running the file backup
TSM 6.3.4 on Win2k8-64
Exchange 2010 on Win2k8 64
This is not a show-stopper, just in the "annoying and mysterious" category.
Installed Exchange 7.1.1 TDP for a customer today.
The beautiful FCM interface popped in all the pre-reqs, VSS testing ran, I set
the appropriate passwords and proxy rela
10 matches
Mail list logo