Comments on: Backing up Exchange Server 2016 Using Windows Server Backup https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/ Practical Office 365 News, Tips, and Tutorials Tue, 21 Jan 2020 15:56:48 +0000 hourly 1 https://wordpress.org/?v=6.3.2 By: Penny Wendt https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-228716 Tue, 21 Jan 2020 15:56:48 +0000 https://www.practical365.com/?p=9008#comment-228716 Im installing Exchange backup to fix a space issue with transaction logging. However it seems to be stuck at 24% (over 30 minutes now) which makes me suspect its stuck. Im concerned its diskspace causing it. Can you tell me how much space I need to recoup before I can install the backup software? OR is there some other reason I would be stuck you can think of?

]]>
By: Robert Se https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-227886 Sun, 22 Sep 2019 00:28:27 +0000 https://www.practical365.com/?p=9008#comment-227886 Hi I did exactly what was stated but it came back with the below error

Writer Failures
Writer Id: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}
Instance Id: {5F35F80F-B590-4A56-BEB7-2A9BA7C2E631}
Writer Name: Microsoft Exchange Writer
Writer State: 5
Failure Result: 800423F3
Application Message: (null)
Logical Path: Microsoft Exchange Server\Microsoft Information Store\xxxxxxxxxxxxxxxx
Component Result: 800423F3
Component Message: (null)
File Spec: M:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 1801403271\Mailbox Database 1801403271.edb Recursive: 0
Logical Path: Microsoft Exchange Server\Microsoft Information Store\xxxxxxx
————————–*

]]>
By: Anthony https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-164550 Fri, 05 Oct 2018 15:10:33 +0000 https://www.practical365.com/?p=9008#comment-164550 Hi Paul,

I have set up a DAG in Exchange 2016. Server 1 has copied to Server 2 and appears healthy. When i run an Exchange aware backup on Server 1, the logs for the active copy on Server 1 truncate but the logs for the passive copy of this DB on Server 2 are not purged.

Should they be or do i need to run an Exchange aware backup against the passive copy of the DB on Server 2?

Thanks

]]>
By: Paul Cunningham https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-158775 Fri, 18 May 2018 02:10:05 +0000 https://www.practical365.com/?p=9008#comment-158775 In reply to John.

If something goes wrong with the server, treat is as a failed server and do a recovery.

https://www.practical365.com/exchange-server/recovering-a-failed-exchange-2016-database-availability-group-member/

Don’t just restore or roll back the server from the last backup/snapshot.

]]>
By: John https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-158774 Fri, 18 May 2018 01:54:34 +0000 https://www.practical365.com/?p=9008#comment-158774 Great article. I see that you only backup database and logs. What is the best recommended practice for Exchange servers’s backup?. For an example, we have servers in DAG and something went wrong with the servers when we apply CU and windows updates, in this case ,DBs and logs are good, only issue with OS or Exchange programs files.

]]>
By: Fried Bacon https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-158373 Sat, 28 Apr 2018 12:45:50 +0000 https://www.practical365.com/?p=9008#comment-158373 Thanks for your articles man, helped me out a lot in managing my exchange server. Self thought here, really need all the help I can get

]]>
By: Paul Cunningham https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-156164 Fri, 17 Nov 2017 22:26:31 +0000 https://www.practical365.com/?p=9008#comment-156164 In reply to Peter Atkin.

“When run directly a restore via shadow copies” – I don’t understand what you mean by this. There are specific ways to restore Exchange servers from backups. What guidance are you following?

]]>
By: Peter Atkin https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-156156 Fri, 17 Nov 2017 15:12:30 +0000 https://www.practical365.com/?p=9008#comment-156156 Great Article, I have come across an issue with restoring exchange that you might be able to help with?

1- DC server Windows 2012R2
2- Exchange 2016 cu6 installed onto Windows 2012R2 joined to domain but not a DC
— 3 drives (not partitions) OS, data, backup, C: D: and E: respectively
—OS drive has all the normal stuff +exchange, data Drive has the Exchange databases, and backup drive is for the backups.
3- OOS installed onto Windows 2012R2 joined to domain but not a DC
– All on separate vm machines

Backup seems to work fine but when I get to restore I get an error:

1. When run directly a restore via shadow copies: A volume that contains the operating system files or resides on a cluster shared disk cannot be reverted?
2. When running via the backup app in restore mode, I can only restore the OS to another drive? not the current OS drive.

I sure there is a reason, but no idea what I am doing wrong?

Possible for any advice in this matter.

]]>
By: Aleks Stolevski https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-86166 Tue, 16 May 2017 12:49:59 +0000 https://www.practical365.com/?p=9008#comment-86166 In reply to John Tseung.

Hi John,

Were you able to resolve this? I’m having the same issue 🙁

Thanks!
Aleks

]]>
By: Martin https://practical365.com/backing-up-exchange-server-2016-using-windows-server-backup/#comment-83362 Mon, 08 May 2017 18:39:25 +0000 https://www.practical365.com/?p=9008#comment-83362 I got the same issue like other people with Windows Backup not truncating the logs. I have selected the volumes during backup schedule and I selected VSS Full Backup to truncate the logs. The backup is successfull and also this command: Get-MailboxDatabase -Server -Status | fl Name,*FullBackup
shows a date and timestamp for “LastFullBackup” for all databases. However, all the logs are still there.

Any ideas?

]]>