Backup The Mabs Server - Document Details

This page contains Windows bias

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types

windows_tools

powershell_heavy

windows_first

missing_linux_example

Summary

The documentation is heavily biased toward Windows environments. All backup and recovery procedures rely on Windows-specific tools (e.g., PowerShell, mountvol.exe, diskshadow.exe, psexec.exe, VSS, Windows Explorer), and all example commands and scripts are for Windows. There are no Linux equivalents or cross-platform instructions, and the documentation assumes the use of Windows-based SQL Server and file paths. No mention is made of Linux support, alternative tools, or how to perform these tasks on non-Windows systems.

Recommendations

Clearly state in the prerequisites or introduction if MABS is only supported on Windows. If so, explain why and link to alternatives for Linux users.
If any components (such as SQL Server) can be hosted on Linux, provide equivalent Linux commands and procedures for backup and restore.
For each example using Windows-specific tools (e.g., PowerShell, mountvol.exe, diskshadow.exe), provide Linux equivalents or note their absence.
Where file paths or shares are referenced (e.g., C:\ paths, UNC shares), include Linux path examples if supported.
If VSS (Volume Shadow Copy Service) or Windows Previous Versions are used, mention Linux alternatives (e.g., LVM snapshots, rsync, etc.) or clarify that these features are not available on Linux.
Add a section explicitly addressing cross-platform support and limitations, so Linux administrators know what is and isn't possible.
If MABS is strictly Windows-only, suggest alternative backup solutions for Linux environments (e.g., Azure Backup for Linux, third-party tools).

Create Pull Request

Scan History

Date	Scan	Status	Result
2026-01-12 00:00	#99	completed	Biased
2026-01-11 06:20	#98	completed	Biased
2026-01-10 00:00	#92	completed	Clean
2026-01-06 22:28	#78	completed	Clean
2025-12-29 18:00	#48	cancelled	Biased
2025-12-15 00:00	#7	completed	Clean
2025-12-14 05:05	#6	completed	Clean

Flagged Code Snippets

    OSQL -E -S localhost\SQL_INSTANCE_NAME -Q "BACKUP DATABASE DPMDB_NAME TO DISK='C:\DPMBACKUP\dpmdb.bak' WITH FORMAT"

    <?xml version="1.0" encoding="utf-8"?>
    <ScriptConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns="https://schemas.microsoft.com/2003/dls/ScriptingConfig.xsd">
    <DatasourceScriptConfig DataSourceName="C:">
    <PreBackupScript>C:\MABSDBBACKUP\bkupdb.cmd</PreBackupScript>
    <TimeOut>120</TimeOut>
    </DatasourceScriptConfig>
    </ScriptConfiguration>

        Net Share MABSSERVERNAME-dpmdb="C:\Program Files\Microsoft System Center\DPM\DPM\Volumes\Replica\File System\vol_c9aea05f-31e6-45e5-880c-92ce5fba0a58\454d81a0-0d9d-4e07-9617-d49e3f2aa5de\Full\DPMBACKUP"

    Select ag.NetbiosName as
    ServerName,ds.DataSourceName,vol.MountPointPath,vol.GuidName
    from tbl_IM_DataSource as ds
    join tbl_PRM_LogicalReplica as lr on ds.DataSourceId=lr.DataSourceId
    join tbl_AM_Server as ag on ds.ServerId=ag.ServerId
    join tbl_SPM_Volume as vol on lr.PhysicalReplicaId=vol.VolumeSetID
    and vol.Usage =1
    and lr.Validity in (1,2)
    where ds.datasourcename like '%C:\%' -- volume drive letter for DPMBACKUP
    and servername like '%dpmsqlservername%' --netbios name of server hosting DPMDB

        net share SERVERNAME-DPMDB="X:\454d81a0-0d9d-4e07-9617-d49e3f2aa5de\Full\DPMBACKUP"

DpmSync –RestoreDb -DbLoc G:\DPM\Backups\2005\November\DPMDB.bak

DpmSync -Sync

DpmSync -ReallocateReplica

DpmSync –RestoreDb -DbLoc G:\DPM\Backups\2005\November\DPMDB.bak –InstanceName contoso\ms$dpm

DpmSync -Sync

DpmSync -ReallocateReplica