[gpfsug-discuss] mmbackup logging issue

Ashish Thandavan ashish.thandavan at cs.ox.ac.uk
Fri Mar 3 13:05:56 GMT 2017


Hi Jez,

>
>   This is the primary reason for using snapshots for mmbackup ( -S  
> snapname ) and making sure that only mmbackup sends data to backup 
> rather than an oob dsmc:
>
> Tue Jan 17 18:07:31 2017 mmbackup:Audit files /cs/mmbackup.audit.gpfs* 
> contain 0 failed paths but there were 10012 failures.
> Cannot reconcile shadow database.
> Unable to compensate for all TSM errors in new shadow database.
>   Preserving previous shadow database.
>   Run next mmbackup with -q to synchronize shadow database.  exit 12   
> <------------ ick!
>

I was going to send a separate email about this, but as you mention it 
-- I was wondering if the TSM server requires the shadow files to also 
be backed up? And that reconciliation of the shadow database will fail 
if they are not?
(Unless of course, you mean above that the shadow database failure is 
purely on account of the 10012 failures...)

Re the use of snapshots for mmbackup, are you saying dsmc does not get 
involved in sending the files to the TSM server? I haven't used 
snapshots for mmbackup, but will certainly try!

Regards,
Ash

-- 
-------------------------
Ashish Thandavan

UNIX Support Computing Officer
Department of Computer Science
University of Oxford
Wolfson Building
Parks Road
Oxford OX1 3QD

Phone: 01865 610733
Email: ashish.thandavan at cs.ox.ac.uk




More information about the gpfsug-discuss mailing list