Tom
That rings a bell. These backups use VSS so you need to stagger them by 10
minutes or so to allow VSS to do its thing, and yes, you need separate logs for
each process for them to be useful but that’s just flags to the commands.
I did get a sample script from someone internal to IBM who
Couldn't I just set up multiple schedulers that all start up at about the
same time to make it parallel. That way I don't need to try and extract
the errorlevels for each process and try to combine them somehow.
I tried adding a START command in front of the FULL backup at the beginning
of my
Tom
It is a failing of TSM/SP that a basic function is deemed "good enough" by the
people who decide such things within IBM and the real-world implementation is
left to users. Your problem is not uncommon and a solution should be a standard
part of the marketed offering.
You will need some
Remco:
I appreciate all feedback, blunt or not. I am relatively new to TSM but I
only work on windows client issues. A separate team works on the TSM
storage servers and they are very experienced
The servers are loafing, they have 4 cores with 32 processors, and 384GB of
ram, not of which is
No, they tried VM's once and the performance was poor. They had to switch
back to physical servers which have 4 cores (32 processors) and 384GB of
ram each.
On Sun, Feb 18, 2018 at 10:37 AM, Stefan Folkerts wrote:
> Hi Tom, are the Exchange servers virtualized on
Hoi Tom,
this might sound a bit blunt, but from what you’re asking I get the strong
impression that this the first time you’re working with TSM. So I’m a bit
anxious to give you any advise, fearing that it might lead to more problems.
In general with performance issues I would look into the
Hi Tom, are the Exchange servers virtualized on vSphere?
On Sat, Feb 17, 2018 at 12:55 AM, Tom Alverson
wrote:
> >
> >
> > We are trying to speed up our Exchange backups that are currently only
> using about 15% of the network bandwidth. Our servers are running Windows