On 17/10/2019 19:37, Simon Thompson wrote:
> Mmbackup uses tsbuhelper internally. This is effectively a diff of
> the previous and current policy scan. Objects inspected is the count
> of these files that are changed since the last time and these are the
> candidates sent to the TSM server.
>
>
Mmbackup uses tsbuhelper internally. This is effectively a diff of the previous
and current policy scan. Objects inspected is the count of these files that are
changed since the last time and these are the candidates sent to the TSM server.
You mention not being able to upgrade a DSS-G, I
On 17/10/2019 15:26, Skylar Thompson wrote:
> On Thu, Oct 17, 2019 at 10:26:45AM +, Jonathan Buzzard wrote:
>> I have been looking to give mmbackup another go (a very long history
>> with it being a pile of steaming dinosaur droppings last time I tried,
>> but that was seven years ago).
>>
>>
On Thu, Oct 17, 2019 at 10:26:45AM +, Jonathan Buzzard wrote:
> I have been looking to give mmbackup another go (a very long history
> with it being a pile of steaming dinosaur droppings last time I tried,
> but that was seven years ago).
>
> Anyway having done a backup last night I am
From: "Frederick Stock"
To: gpfsug-discuss@spectrumscale.org
Cc: gpfsug-discuss@spectrumscale.org
Date: 10/17/2019 08:43 AM
Subject:[EXTERNAL] Re: [gpfsug-discuss] mmbackup questions
Sent by:gpfsug-discuss-boun...@spectrumscale.org
Jonathan the "ob
Jonathan the "objects inspected" refers to the number of file system objects that matched the policy rules used for the backup. These rules are influenced by TSM server and client settings, e.g. the dsm.sys file. So not all objects in the file system are actually inspected.
As for tuning I
I have been looking to give mmbackup another go (a very long history
with it being a pile of steaming dinosaur droppings last time I tried,
but that was seven years ago).
Anyway having done a backup last night I am curious about something
that does not appear to be explained in the documentation.
