Backup Monitor PowerShell Script

Purpose

The Backup Monitor PowerShell script is designed to monitor backup sets and ensure that they meet certain criteria, such as backup frequency and backup size. It can be used to keep track of the status of backup operations for critical data.

Copyright & License

This script is distributed under the terms of the GNU General Public License (GPL) version 3. You can find a copy of the license in the LICENSE file.

Checks Performed

The script performs the following checks on each backup set:

1. Minimum Backup Sets: Ensures that there are a minimum number of backup sets available in the specified path. If a number smaller than minBackupSets is found and the last backup is not older than 25 hours, no alarm is generated because it is assumed that it is a new archive and needs to be filled with enough backups first.

2. Backup Frequency: Detects the backup frequency pattern based on timestamps and checks if the latest backup aligns with the determined pattern.

3. Backup Size: Checks if the size of the latest backup is within an acceptable range based on the sizes of previous backups.

Configuration and Parameters

The script can be configured using a configuration file. The following parameters can be specified in the configuration file:

• minBackupSets: Minimum number of backup sets required.
• emailSender: Email address of the sender for notification emails.
• notificationEmail: Email address to which notification emails will be sent.
• notifyType: Notification type, with valid values: off, alarm, always, alarmonlastbackup.
  • off: No mails will be sent.
  • alarm: A mail will be sent when an alarm was raised.
  • always: A mail will always be sent with a summary after a run of the script
  • alarmonlastbackup: A mail will be sent only when an alarm, concerning the newest backup in the list, was raised.
• smtpServer: SMTP server address for sending notification emails.
• backupPaths: An array of backup paths to monitor. Each path is assumed to contain the backup sets of one individual application or system. It doesn't matter if a backup set consits of a file or a folder holding multiple files. A path can locate any resource on local drives or on a SMB share.

Emails will only be sent if specified parameters emailSender, notificationEmail, notifyType and smtpServer are provided with valid values.

Example Configuration File

minBackupSets = 5
emailSender = backup-monitor@yourdomain.com
notificationEmail = your@email.com
notifyType = alarmonlastbackup
smtpServer = smtp.yourmailserver.com

[Paths]
C:\Backups\BackupApp1
\\Server\Backup\BackupApp2

Calling the PowerShell Script

You can call the PowerShell script from a batch file or directly using the following command:

powershell.exe -ExecutionPolicy Bypass -File "backupmon.ps1" -config "config.txt" > backupmon.log

Replace config.txt with the path to your configuration file. All output will be logged to the file backupmon.log

Usage

1. Create a configuration file as described in the example above.

2. Save the PowerShell script and the configuration file in the same directory.

3. Run the script using the command provided above, either manually or as part of an automated backup monitoring process.

For more information and detailed usage instructions, please refer to the comments within the script itself.

Feel free to customize the script and configuration to meet your specific backup monitoring needs.