Azure DevOps (On-Prem) 备份失败

Azure DevOps (On-Prem) failed backup

尝试在 Prem 安装上备份我的 Azure DevOps 2019 时出现此错误

[Yesterday 9:51 AM] Spike, CBB
TF401002: The SQL Server Database Engine failed to save the database backup to path \servername\TFSBackup.  Please grant SQL service account read/write access to that folder.
[Yesterday 9:52 AM] Spike, CBB
[Error  @09:50:58.458] Backup job Failed: TF400797: Job extension had an unhandled error: System.Data.SqlClient.SqlException (0x80131904): Cannot open backup device '\servername\TFSBackup\Tfs_Tempaad2227d-7d80-4925-aaeb-a8e8f0f82ea6.bak'. Operating system error 1331(This user can't sign in because this account is currently disabled.).
BACKUP DATABASE is terminating abnormally.
       at Microsoft.VisualStudio.Services.Configuration.SqlDatabaseBackupRestoreComponent.Execute(String sqlStatement)
       at Microsoft.VisualStudio.Services.Configuration.SqlDatabaseBackup.Backup(ISqlConnectionInfo connectionInfo)
       at Microsoft.TeamFoundation.Admin.Jobs.DatabaseBackupJob.TakeFullBackupOfSingleDatabase(IVssRequestContext requestContext, String dataSource, String databaseName, String fullFileName, ITFLogger logger)
       at Microsoft.TeamFoundation.Admin.Jobs.VerifyBackupPermissionsJobExtension.Run(IVssRequestContext requestContext, TeamFoundationJobDefinition jobDefinition, DateTime jobQueueTime, String& resultMessage)
       at Microsoft.TeamFoundation.Framework.Server.JobRunner.ExecuteJob(IVssRequestContext requestContext)
    ClientConnectionId:00000000-0000-0000-0000-000000000000
    Error Number:3201,State:1,Class:16
    <https://teams.microsoft.com/l/message/19:4337d5ee1c4f4e0783e85f502995dd2f@thread.skype/1601995914116?tenantId=0e1609b0-5e7f-4722-8611-c7f3067cebdc&amp;groupId=c4973237-b7c6-41ea-97fb-6b724182d4de&amp;parentMessageId=1601995880671&amp;teamName=Enterprise DevOps Team&amp;channelName=dotNET DevOps&amp;createdTime=1601995914116>

我正在尝试找出哪个帐户被禁用了。

我做了以下事情:

我认为我的任何帐户都没有被禁用,它使用什么帐户来执行此任务?

原来使用的帐户是 Azure DevOps 数据库连接到的帐户 运行 SQL 服务器。

当我检查该帐户时,实际上它已被禁用,奇怪的是 SQL 仍然是 运行。当我重新启动服务时,它停止工作了。

事实证明,安全团队认为该帐户做了一些奇怪的事情,因此他们决定在不告诉任何人的情况下禁用该帐户。

Re-enabled 帐户,现在我又备份了。