Note: I don’t recommend this, except in emergencies.
Note that the script below assumes your databases are on C: and that there is
not a volume named G:. Adjust as necessary.
That being said:
[1] create a folder named c:\bk
[2] within c:\bk create a file named online-backup.cmd. Insert
these contents:
@echo off
exit 0
[3] within c:\bk create a file named online-backup.dsh. Insert these contents:
# Diskshadow purge script.
set context persistent
set metadata C:\bk\online-backup.cab
# verify presence of 'Microsoft Exchange Writer'
writer verify {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
# exclude 'Task Scheduler Writer' 2012
writer exclude {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
# exclude 'VSS Metadata Store Writer' 2012
writer exclude {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
# exclude 'Performance Counters Writer' 2012
writer exclude {0bada1de-01a9-4625-8278-69e735f39dd2}
# exclude 'System Writer' 2012
writer exclude {e8132975-6f93-4464-a53e-1050253ae220}
# exclude 'FRS Writer' 2012
writer exclude {d76f5a28-3092-4589-ba48-2958fb88ce29}
# exclude 'SqlServerWriter' 2012
writer exclude {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
# exclude 'NTDS' 2012
writer exclude {b2014c9e-8711-4c5c-a5a9-3cf384484757}
# exclude 'IIS Metabase Writer' 2012
writer exclude {59b1f0cf-90ef-465f-9609-6ca8b2938366}
# exclude 'IIS Config Writer' 2012
writer exclude {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
# exclude 'WMI Writer' 2012
writer exclude {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
# exclude 'ASR Writer' 2012
writer exclude {be000cbe-11fe-4426-9c58-531aa6355fc4}
# exclude 'BITS Writer' 2012
writer exclude {4969d978-be47-48b0-b100-f328f07ac1e0}
# exclude 'Registry Writer' 2012
writer exclude {afbab4a2-367d-4d15-a586-71dbb18f8485}
# exclude 'Shadow Copy Optimization Writer' 2012
writer exclude {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
# exclude 'COM+ REGDB Writer' 2012
writer exclude {542da469-d3e1-473c-9f4f-7847f01fc64f}
# exclude 'MSMQ Writer (MSMQ)' 2012
writer exclude {7e47b561-971a-46e6-96b9-696eeaa53b2a}
begin backup
add volume C: alias shadow_C
create
expose %shadow_C% G:
exec C:\bk\online-backup.cmd
end backup
delete shadows exposed G:
exit
[4] open an elevated cmd.exe prompt. Cd to c:\bk. Execute the following command:
diskshadow /s online-backup.dsh
Voila!
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On
Behalf Of Joseph L. Casale
Sent: Thursday, July 27, 2017 12:08 PM
To: exchange@lists.myitforum.com
Subject: Re: [Exchange] Changing logging to Circular and back?
Truncate them yourself if space is an issue before the proper backup strategy
is in place. There are few ways to do this. Check out the eseutil docs.
From: NP
Sent: Thursday, July 27, 8:50 AM
Subject: [Exchange] Changing logging to Circular and back?
To: exchange@lists.myitforum.com<mailto:exchange@lists.myitforum.com>
Apparently we had a miscommunication between departments and our backup guys
were only doing a DB copy when backing up our 2013 DB’s so logs haven’t been
getting trunked for months. That equals about 2TB’s of log files. I’m not
sure how to dig myself out of this (if we can’t get a full backup with logs so
they are deleted) other than maybe turning circular logging on for a short time
and letting Exchange clean them up. Will Exchange even clean them up or will
we still need to manually delete?
Thanks
Niles
