We have a python script that parses the mmbackup output log and outputs a number of bits of data, mostly the success/failure of the backup run, and date of last backup, so we can monitor how long it is since the last successful backup and alert us when its more than so many hours since the last backup.
The Script can also pickup the % of progress though the backup, but I've not got around to getting it working quite yet. If people are interested I could look to checking it over and making it available. Peter Childs ITS Research Storage Queen Mary University of London ________________________________________ From: gpfsug-discuss <[email protected]> on behalf of Fosburgh,Jonathan <[email protected]> Sent: 07 September 2023 11:44 AM To: gpfsug main discussion list Subject: Re: [gpfsug-discuss] [EXTERNAL] mmbackup feature request CAUTION: This email originated from outside of QMUL. Do not click links or open attachments unless you recognise the sender and know the content is safe. You might be interested in looking at Ideas GPFS-I-975 and GPFS-I-259. -- Jonathan Fosburgh, MS, CAPM Principal Application Systems Analyst IT Engineering Storage Team The University of Texas MD Anderson Cancer Center (713) 745-9346 [Graphical user interface Description automatically generated with low confidence][A picture containing text, room, gambling house Description automatically generated][Graphical user interface Description automatically generated with medium confidence] From: gpfsug-discuss <[email protected]> on behalf of Jonathan Buzzard <[email protected]> Date: Wednesday, September 6, 2023 at 04:04 To: gpfsug main discussion list <[email protected]> Subject: [EXTERNAL] [gpfsug-discuss] mmbackup feature request THIS EMAIL IS A PHISHING RISK Do you trust the sender? The email address is: [email protected] While this email has passed our filters, we need you to review with caution before taking any action. If the email looks at all suspicious, click the Report a Phish button. Would it be possible to have the mmbackup output display the percentage output progress when backing up files? So at the top we you see something like this Tue Sep 5 23:13:35 2023 mmbackup:changed=747204, expired=427702, unsupported=0 for server [XXXX] Then after it does the expiration you see during the backup lines like Wed Sep 6 02:43:53 2023 mmbackup:Backing up files: 527024 backed up, 426018 expired, 4408 failed. (Backup job exit with 4) It would IMHO be helpful if it looked like Wed Sep 6 02:43:53 2023 mmbackup:Backing up files: 527024 (70.5%) backed up, 426018 (100%) expired, 4408 failed. (Backup job exit with 4) Just based on the number of files. Though as I look at it now I am curious about the discrepancy in the number of files expired, given that the expiration stage allegedly concluded with no errors? Tue Sep 5 23:21:49 2023 mmbackup:Completed policy expiry run with 0 policy errors, 0 files failed, 0 severe errors, returning rc=0. Tue Sep 5 23:21:49 2023 mmbackup:Policy for expiry returned 0 Highest TSM error 0 JAB. -- Jonathan A. Buzzard Tel: +44141-5483420 HPC System Administrator, ARCHIE-WeSt. University of Strathclyde, John Anderson Building, Glasgow. G4 0NG _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org https://urldefense.com/v3/__http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org__;!!PfbeBCCAmug!j_DKizkmTItFp2H_1xckC8hR7VkDw_ec7pvv0K1d3xe-_qXr1n5W8NpNKOwhxWMn62Z0a3v2zoA2hL13tIYXypi_grSBHAgTO1w$<https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss_gpfsug.org__%3B!!PfbeBCCAmug!j_DKizkmTItFp2H_1xckC8hR7VkDw_ec7pvv0K1d3xe-_qXr1n5W8NpNKOwhxWMn62Z0a3v2zoA2hL13tIYXypi_grSBHAgTO1w%24&data=05%7C01%7C%7Cd86cb0b2773c4587af5f08dbaf90347d%7C569df091b01340e386eebd9cb9e25814%7C0%7C0%7C638296806133388970%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000%7C%7C%7C&sdata=64q80xO9d6JUZPUN0ADBWmyaiMeT3Yn8f2TbRJJId48%3D&reserved=0> The information contained in this e-mail message may be privileged, confidential, and/or protected from disclosure. This e-mail message may contain protected health information (PHI); dissemination of PHI should comply with applicable federal and state laws. If you are not the intended recipient, or an authorized representative of the intended recipient, any further review, disclosure, use, dissemination, distribution, or copying of this message or any attachment (or the information contained therein) is strictly prohibited. If you think that you have received this e-mail message in error, please notify the sender by return e-mail and delete all references to it and its contents from your systems. _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
