Skip to main content
added 200 characters in body
Source Link
Nathan
  • 111
  • 1
  • 9

Wow.

It's just incredibly slow.

In my case it hangs after those lines for about an hourabout an hour before producing any additional output in the PowerShell host or writing any files to the backup location.

As documented elsewhere, both the user running the Backup-SPFarm cmdlet and the user (service account) running the database service need permissions to write to the backup destination. ButAnd I have broken Search and Admin apps because I haven't finished configuring them yet. Once it won't even display errors about that until aftercan write to the long silent hang periodbackup destination, the spbackup.log file in the spbr000* folder has lots of details.

But it won't even display errors until after the long silent hang period.

Wow.

It's just incredibly slow.

In my case it hangs after those lines for about an hour before producing any additional output in the PowerShell host or writing any files to the backup location.

As documented elsewhere, both the user running the Backup-SPFarm cmdlet and the user (service account) running the database service need permissions to write to the backup destination. But it won't even display errors about that until after the long silent hang period.

Wow.

It's just incredibly slow.

In my case it hangs after those lines for about an hour before producing any additional output in the PowerShell host or writing any files to the backup location.

As documented elsewhere, both the user running the Backup-SPFarm cmdlet and the user (service account) running the database service need permissions to write to the backup destination. And I have broken Search and Admin apps because I haven't finished configuring them yet. Once it can write to the backup destination, the spbackup.log file in the spbr000* folder has lots of details.

But it won't even display errors until after the long silent hang period.

Source Link
Nathan
  • 111
  • 1
  • 9

Wow.

It's just incredibly slow.

In my case it hangs after those lines for about an hour before producing any additional output in the PowerShell host or writing any files to the backup location.

As documented elsewhere, both the user running the Backup-SPFarm cmdlet and the user (service account) running the database service need permissions to write to the backup destination. But it won't even display errors about that until after the long silent hang period.