Windows – VSS error–Event ID 25

July 11, 2017

Recently I got an Error Event ID 25 and the System State backup failed!

image

Event ID 25 : …Shadow Copy Storage could not grow in time…

Debugging :

Use this command vssadmin list shadowstorage /for=D:

image

It showed some storage limitations for the VSS on the D: drive.

Also check the Backup Logs: %windir%\logs\WindowsServerBackup

image

Opening the last log I see that there are no errors and the log suddenly stops …

image

Solution :

I checked the settings and indead there was a limitation set…

image

image

So I changed it to unlimited and solved Smile

But make sure that you have enough disk capacity before you set it to unlimited !!

image

Because it can grow fast !

In case this does not work you can use these alternatives :

The following command on the host in order to place the shadow copy on another disk; drive letters need to be changed accordingly:

vssadmin add shadowstorage /For=D: /On=E: /MaxSize=UNBOUNDED
vssadmin resize shadowstorage /For=D: /On=E: /MaxSize=UNBOUNDED

Or you can modify the System Performance by Adjusting the Page File to 1.5 times the amount of RAM:

  1. Open System in Control Panel.
  2. On the Advanced tab, under Performance, click Settings.
  3. On the Advanced tab, under Virtual memory, click Change.
  4. Under Drive [Volume Label], click the drive that contains the paging file you want to change.
  5. Under Paging file size for selected drive, click Custom size, and type a new paging file size in megabytes in the Initial size (MB) or Maximum size (MB) box, and then click Set.

This will have only an effect after a REBOOT !

Advertisements

Windows – Backup failed with following error code ‘2155347997’

June 9, 2015

I have a System State backup failing for days on a Windows 2K8r2 server, giving an Event ID 517 error Sad smile

image

Quite a cryptic error code ‘2155347997’

After looking around on the interweb I found a lot of hotfixes and workarounds to get it solved. But I was convinced that none of those was really the root cause.

I had a gut feeling that lack of disk space would be a more reasonable cause of the failing backup.

I decided to start a manual backup using WBAdmin

But it did end into the same error ?

Next I decided to save the backup to a different server logical disk using this command :

WBADMIN START SYSTEMSTATEBACKUP -backupTarget:\\server\e$

image

And voila all went well Smile


MS SQL – Compressed Back Tool

February 17, 2013

Making MS SQL backups is quite easy using the build-in features.

But it is more efficient using the Compressed Backup Tool which you can download here http://mssqlcompressed.sourceforge.net/doc_command.shtml

The syntax us as follows :

msbp.exe backup "db(database=YourDB)" 
"zip64(level=3;filename=YourDB)" 
"local (path=D:\Temp\YourDB.zip)"

The benefits are highly compressed backups compared to the native MS SQL backups.

image

Just give it a try