vss writers services to restart

How to manually restart VSS Writers in a failed state without Rebooting Server.

Oct 26, 2021 • Consolidated Knowledge Type

Description:.

Find each of the VSS writers in a failed state by using the command in command prompt (Run As Administrator) - ' vssadmin list writers '.
Mark and copy all the failed VSS writers.
Find the VSS writer's associated Service Display Name in the table below and restart the service.

Run another Backup/snapshot.
If the VSS writers fail again, it would be necessary to restart the server.

Article Information

VSS Writer Failed: Re-registering VSS Writers on Windows Server

Find the components with the Failed state in the list. For the components working normally, the state looks as follows: State: [1] Stable .

Writer name: 'Microsoft Exchange Writer' Writer Id: {53da1ac4-4bab-404a-0917-ae23f8aacfb7} Writer Instance Id: {61b56ab0-9588-432f-ae7b-3233753ffa38} State: [7] Failed Last error: Retryable error

As you can see, in our case Microsoft Exchange Writer has failed (State: [8] Failed), so you won’t be able to complete the Exchange backup. Typically, to fix the state of this component, it’s enough to restart the server (which is not always possible for production reasons).

To repair the Exchange writer, try to restart the related service. (The table below shows the list of typical VSS Writers and the related Windows services.) Besides stopping the service, sometimes you will have to kill a hung service process manually.

vssadmin list writers

Check the status of the problem VSS writer. If it hasn’t changed to Stable state and the problem is not fixed, you can try to re-register the VSS components and libraries.

Go to this directory:

cd c:\windows\system32

Stop the following services: Volume Shadow Copy and Microsoft Software Shadow Copy Provider.

Net Stop VSS Net Stop SWPRV

stop the shadow copy services: vss and swprv

Re-register the VSS components:

regsvr32 /s ole32.dll regsvr32 /s oleaut32.dll regsvr32 /s vss_ps.dll vssvc /register regsvr32 /s /i swprv.dll regsvr32 /s /i eventcls.dll regsvr32 /s es.dll regsvr32 /s stdprov.dll regsvr32 /s vssui.dll regsvr32 /s msxml.dll regsvr32 /s msxml3.dll regsvr32 /s msxml4.dll vssvc /register

re-registering vss writers on windows server 2012 / 2016

Start the previously stopped services: Net Start SWPRV Net Start VSS

Make sure that the error of the problem VSS writer has disappeared.

This method of restarting and re-registering of VSS components is effective both on Windows Server 2008 / 2012/ R2 and on Windows Server 2016.

Limited Wi-Fi Access in Windows 10 and 8.1 – Troubleshooting

Windows server 2016: workgroup failover cluster without active directory, related reading, redirect http to https in iis (windows server), add an additional domain controller to an existing..., how to install an ssl certificate on iis..., fix: remote desktop licensing mode is not configured, extending a disk volume (partition) in windows.

completely full of errors when I remove the silent flag.

It is not recommended to do re-registration of DLLs on 2008 r2 or above version of OS.

Restart VSS Writers without a reboot

Having started working in my current IT support role a little over a year ago, I was shocked to discover that the general fix for Windows Server Backup errors caused by failed VSS writers was to reboot the server. I had in my previous role resolved this issue many times by restarting the service that related to the VSS writer. For example the “Microsoft Hyper-V VSS Writer” failure can be resolved by restarting the “Hyper-V Virtual Machine Management” service (vmms).

A list of failed writers on any given Windows server can be generated by executing the following command from an elevated command prompt:

C:\Windows\system32>vssadmin list writers

For easier reference I personally export the results to a text file using the following:

Once completed you can easily open the generated file in notepad with:

Using the table below find the service for each VSS Writer that is in a failed state, make a note of each service name.

[table caption=”” width=”100%” colwidth=”” colalign=”left|left|left”] VSS Writer,Service Name,Service Display Name ASR Writer,VSS,Volume Shadow Copy BITS Writer,BITS,Background Intelligent Transfer Service Certificate Authority,EventSystem,COM+ Event System COM+ REGDB Writer,VSS,Volume Shadow Copy DFS Replication service writer,DFSR,DFS Replication DHCP Jet Writer,DHCPServer,DHCP Server FRS Writer,NtFrs,File Replication FSRM writer,srmsvc,File Server Resource Manager IIS Config Writer,AppHostSvc,Application Host Helper Service IIS Metabase Writer,IISADMIN,IIS Admin Service Microsoft Exchange Writer,MSExchangeIS,Microsoft Exchange Information Store Microsoft Hyper-V VSS Writer, vmms,Hyper-V Virtual Machine Management NTDS,NTDS,Active Directory Domain Services OSearch VSS Writer,OSearch,Office SharePoint Server Search OSearch14 VSS Writer,OSearch14,SharePoint Server Search 14 Registry Writer,VSS,Volume Shadow Copy Shadow Copy Optimization Writer,VSS,Volume Shadow Copy SPSearch VSS Writer,SPSearch,Windows SharePoint Services Search SPSearch4 VSS Writer,SPSearch4,SharePoint Foundation Search V4 SqlServerWriter,SQLWriter,SQL Server VSS Writer System Writer,CryptSvc,Cryptographic Services TermServLicensing,TermServLicensing,Remote Desktop Licensing WINS Jet Writer,WINS,Windows Internet Name Service (WINS) WMI Writer,Winmgmt,Windows Management Instrumentation [/table]

Using the list of service names complied from the above table restart each of the services, this can be achieved from services.msc or an elevated command prompt.

Services.msc Right click on the service, and then, on the Action menu, click Restart.

Elevated command prompt Execute the following to stop the service:

Once stopped the service needs to be restarted with:

Once the necessary services have been restarted check the status of the VSS Writers:

The relevant VSS writers should now show as stable with no Error.

Published by Kevin Wiblin

View all posts by Kevin Wiblin

Carbonite Support > List of VSS Writers and Servic...

Outdated browser detected.

List of VSS Writers and Services

Hi I'm Cara, a Carbonite expert. I can walk you through this process!

This article is for Windows only

Carbonite Safe Server Backup (CSSB) utilizes a set of built-in Windows functions known as Volume Shadowcopy Services, or VSS. VSS allows backups of in-use, locked, or open files without interrupting whatever process or user is currently accessing those files. This is especially useful for databases, as it allows backups to be performed while the database is active without requiring downtime.

Most backup types in CSSB will rely upon one or more VSS Writers. Each backup type will have its own set of Writers, and each Writer is controlled by a Windows Service. A list of currently-available Writers can be accessed via the command prompt on any Windows computer. Run command prompt as an Administrator and run the command: vssadmin list writers .

This command will list all of the Writers currently available on the machine and display the state of each.

The sections below are collapsed. Please click the section title to open / close a particular section.

A Writer in the Stable state is ready and waiting to perform a backup. Ideally, all Writers should be Stable when no backups are in progress.
Writers in the Failed or Unstable states have encountered a problem, and must be reset to bring the Writer back to a Stable state.
If a Writer is listed as In-Progress or Waiting for Completion when no backups are running, the Writer may be "stuck". Stuck writers must be reset like a Failed or Unstable Writer.

In most cases, the Windows Service that controls a VSS Writer can be restarted. This usually brings the Writer back to a stable state. For example, the Microsoft Exchange Writer is controlled by the Microsoft Exchange Information Store (MEIS) service. If the Exchange Writer becomes Unstable, the MEIS service can be restarted to bring the Writer back to the Stable state.

It is important to note that not all services that control VSS Writers can be restarted. If a service cannot be restarted, a reboot of the machine is required. For example, the VSS Writers associated with System State usually require a reboot.

It is also important to note that restarting some services can cause downtime for the application that is related to the service. In our Exchange example above, Exchange would be unable to send or receive email while the MEIS service was offline. Please plan accordingly.

A reference list of VSS Writers and their controlling services can be found below.

The following list shows the VSS Writers used for each backup type and the service that controls these Writers.

Note: This list is for reference use only and is not comprehensive. A system may have active Writers that are not in this list.

Note: For System State, not all Writers in this list are required for the backup to complete. Some Writers will only be present if the corresponding Windows components are installed on the system. For example, the the NTDS Writer will only be present on Domain Controllers with Active Directory installed. This is normal

Thank you for your comments.

Definitions

Restore: The act of downloading your backed up files from our servers to your computer.
Back up: The act of uploading a copy of your files to our servers for safekeeping.
Backup: This is the copy of files that you've backed up to our servers.
InfoCenter: This is the Carbonite user interface on the Windows version of the product.
Carbonite Backup Drive (CBUD): this is your interface into what's in your backup and how you can restore files or remove files from your backup.
Dots: We place colored status dots on your files in order for you to quickly see what's backed up.
Frozen for safekeeping (freeze backup / frozen mode) : This is a state that you can place Carbonite in to let you safely restore your backup. While in this state, no files or changes will be backed up to our servers.

Common Articles

Personal Restore Overview [ Windows ] [ Mac ]
Office Restore Overview [ Windows ] [ Mac ]
[ Server Restore ] [ Appliance Restore ]
Backup Overdue Personal [ Windows ] [ Mac ]
Backup Overdue Pro [ Windows ] [ Mac ]

Catalogic Knowledge Base
Compatibility Guides
Knowledge Articles
Knowledge Base - Home

Clearing Failed States on VSS Writers Without Rebooting

VSS writers in a failed state cause block-level backup failures. Block level backup fails with the following errors: X.X.X.X sssnap Mon Feb 18 15:04:23 2019 SNBSNP3069E 4680: MsSnapShot::check_wrts_report_okay::check_wrt_status rc[-1] X.X.X.X sssnap Mon Feb 18 15:04:23 2019 SNBSNP3069E 4680: Failed to check the status of all writers after snapshot rc [-1] X.X.X.X sssnap Mon Feb 18 15:04:24 2019 SNBSNP3069E 4680: BACKUP::backup_components failed rc(-10) X.X.X.X sssnap Mon Feb 18 15:04:24 2019 SNBSNP3069E 4680: Failed to backup the applications / disk ( RC(-16) X.X.X.X aph Mon Feb 18 15:04:24 2019 SNBAPH_381E Exception in message (BACKUP_VSS) to module (sssnap), reqrc (-16)

VSS writers are application-specific components for Microsoft's Volume Shadow Copy Service (not operating system dependent), which ensure the consistency of application data when a shadow copy is created, and are useful for creating consistent backups of a system. However, some of these writers enter error states more or less frequently. An alternative solution other than restarting the server is to restart each of the associated services for each of the VSS writers in a failed state by following the steps below:

Find each of the VSS writers in a failed state by issuing this command in an elevated command prompt:
vssadmin list writers
Make a list of all the failed VSS writers, or take a screenshot.
Find the VSS writer's associated Service Display Name in the table below and restart the service.
Issue the command again to confirm the status has changed to Stable with no Error:
Attempt to perform another block-level backup
If the VSS writers fail again, you must restart the server.

Catalogic experts are here to help you.

General Windows

How to manually restart all VSS writers when in a failed state without rebooting

Facebook Opens a new window
Twitter Opens a new window
Reddit Opens a new window
LinkedIn Opens a new window

Spiceworks General Support

There are instances when snapshots are failing due to an agent's VSS writers being in a failed state but it is impossible or not desirable to restart the server until at least after business hours.

The VSS writers may be in a failed state for many different reasons. Once they are in a failed state, it is usually necessary to restart the server.

An alternative solution other than restarting the server is to restart each of the associated services for each of the VSS writers showing up in a failed state by following the steps below:

5 Steps total

Step 1: from elevated command prompt run vssadmin list writers..

vssadmin list writers.

Step 2: Make a list of all the failed VSS writers or take a screenshot.

Step 3: find the vss writer's associated service display name in the table below and restart the service..

ASR Writer - VSS Volume Shadow Copy BITS Writer - BITS Background Intelligent Transfer Service COM+ REGDB Writer - VSS Volume Shadow Copy DFS Replication service writer - DFSR DFS Replication DHCP Jet Writer DHCPServer - DHCP Server FRS Writer - NtFrs File Replication FSRM writer srmsvc - File Server Resource Manager IIS Config Writer AppHostSvc - Application Host Helper Service IIS Metabase Writer IISADMIN - IIS Admin Service Microsoft Exchange Writer MSExchangeIS - Microsoft Exchange Information Store Microsoft Hyper-V VSS Writer vmms - Hyper-V Virtual Machine Management NTDS NTDS - Active Directory Domain Services OSearch VSS Writer OSearch - Office SharePoint Server Search OSearch14 VSS Writer OSearch14 - SharePoint Server Search 14 Registry Writer - VSS Volume Shadow Copy Shadow Copy Optimization Writer - VSS Volume Shadow Copy SPSearch VSS Writer SPSearch - Windows SharePoint Services Search SPSearch4 VSS Writer SPSearch4 - SharePoint Foundation Search V4 SqlServerWriter SQLWriter - SQL Server VSS Writer System Writer CryptSvc - Cryptographic Services TermServLicensing TermServLicensing - Remote Desktop Licensing WINS Jet Writer WINS - Windows Internet Name Service (WINS) WMI Writer Winmgmt - Windows Management Instrumentation

Step 4: Issue the command again to confirm the status has changed Stable with no Error - vssadmin list writers.

Step 5: attempt to perform another snapshot..

If the VSS writers fail again, it will be necessary to restart the server.

Nice write up. It looks very similar to this one: https://support.software.dell.com/appassure/kb/129774

You are correct, there is a lot of information that is quite similar. I would say the biggest difference is the article you posted is not in our Spiceworks KB.

Excellent especially as the Dell article is now behind a paywall. I would suggest adding how to restart the service from the command line and maybe how to do it with psexec remotely.

Good article. The only thing I found missing wast he one I was actually looking for. The NPS VSS writer is associated with the COM+ Event System, (but so are a lot of services so be cautious restarting it).

EDIT: Just found another. Hyper-V VSS Writer is Hyper-V Virtual Machine Management

Here is a similar article at the ArcServe knowledgebase....

https://arcserve.zendesk.com/hc/en-us/articles/209606286-How-to-manually-restart-VSS-Writers-in-a-failed-state-without-Rebooting-Server-

Or, you can go to the place where everyone else copied the list from:

http://sdb.planetcobalt.net/vss_writers.shtml

Disclaimer: I'm the original author (in case that wasn't obvious).

Thanks - Much Appreciated - I needed it as I am having Nutanix servers and rebooting them takes a lot of time because of CVMs RF

THanks again

I know you dont have to, But i also put the host servers in to maintenance mode, before restarting the service

Restarting VSS Writers with PowerShell script

VSS Writers are responsible for backups – if they stop working, then backups might fail. The solution to that is restarting VSS Writers, but the problem here is that there are many, and at least out of the box, there’s no mechanism to make this automatic… but there’s PowerShell.

I’m not interested in your code, I just want to restart these VSS Writers #

In that case, head on to: mygithub , use the code and run:

That function will go ahead, retrieve all failed VSS Writers, and restart associated services with them. If that won’t help, then you probably need to reboot the server.

Get-KPVssWriter

Let’s talk PowerShell #

The source code is available on GitHub .

As far as VSS Writers go, there were a few issues needed to be addressed for the function:

the VssAdmin.exe tool is CMD only, and returns only strings.
There’s no filter in VssAdmin, thus it always returns all writers
The writers are associated with many Windows Services, and it’s not always obvious which service is responsible for given VSS Writer

Therefore I’ve written a couple of functions:

Get-KPVssWriter – that function will convert the output string from VssAdmin into a PowerShell objects + it can filter results by state (at the moment Stable or Failed).
Restart-KPVssWriter – this function takes the name of the VSS writer and restarts required service with it. It has hard-coded names of VSS writers with associated services.

How do you make a use of these?

You pipe results from Get function, to Restart function thus:

will retrieve all failed writers and restart them. Let’s look into actual code.

Get-KPVssWriter #

First is to run VSSAdmin and start converting the output into PowerShell object:

Select-String #

These two lines will convert the output from vssadmin into PowerShell object. The Select-String really shines here as:

-Pattern parameter allows it to search for a specific phrase. In that case I’m looking for ‘Writer name:’ as each listed writer starts with that line.
-Context 0,4 tells PowerShell that for each pattern (line) you found, match 0 line prior to it, and 4 past it.

Thus if we look for this sample:

You can see that there’s pattern: Each Writer Name is followed by four line of text, and then the next one appears.

Select-String will then create an object for each pattern found, with properties of Line, Context.PostContext and Context.PreContext.

And since we know that:

Line = pattern found,

Context.PostContext = an array of each line found past pattern

Context.PreContext. = an array of each line found prior the pattern

It’s very easy to create the object, but first we need to remove the leftovers of the string.

For every object generated by Select-String, I will assign a specific variable, and run -replace to remove unnecessary characters. Replace can also take regex , making it super effective while working with text.

PsCustomObject #

The final step is to assembly all variables created in previous step into a PowerShell object:

Since the main purpose of using this function is to restart failed, I thought it would be worth to add a parameter for filtering out VSS Writers based on status, thus this simple if statement which amends what will be outputed by the function:

There we go, the analogue application has been converted into a digital form (LOL), we can go ahead now and work on the actual restarts.

Restart-KPVssWriter #

This function will take the name of the VSS writer that requires restart, match Windows service to it, and restart the service.

PowerShell has a beatifull command – Switch – that eliminates the need of writing complex if statements. Let’s have a look:

Hell yeah, that would be quite a if statement. Instead of that, switch will match the name on the left, and execute the code to the right.

The last line is interesting, default – if switch won’t match the name, it will execute that one instead. I’m casting that into $null.

The final step is to restart service:

Simple restart of service if it was matches earlier on, or just write warning if it wasn’t found.

Happy ever after #

I hope you found this useful. What can be done here is e.g. put the script into a scheduled task to run hourly, and hopefully you will have one problem less to worry about – as nobody likes to see failed backups on Monday morning.

Photo by Jason Yu on Unsplash

Articles VSS Writer Failed / How to Restart and Re-Register VSS Writers

Explore other articles and discussions on this topic.

VSS Writer Failed / How to Restart and Re-Register VSS Writers

Jun 25, 2020 • Break Fix

Information.

VSS writers can fail for various reasons, such as two or more resources trying to use the writer at the same time. When you run vssadmin list writers in a command prompt with admin rights, you might see one of the writers in a failed state, as shown below:

On the Windows server in question, open a command prompt with administrative rights and run the command vssadmin info vssadmin list writers
Check the writers that have failed.
You can use the list below to find the service that corresponds to the VSS Writer in question. Restart the corresponding windows services for the writers that are down.
Use the vssadmin list writers command again to show if the vss writer is now in a stable state.
If the vss writer remains in a failed state, you will need to re-register the writers.

KB 4447 contains some additional steps to follow from Technet and other related Microsoft VSS subsites.

Reset VSS Writer & Lookup Display Name

When troubleshooting vss writer errors, the following table can be used to identify the service display name in services.msc..

Backup fails with one or more VSS Writer errors.

Find each of the VSS writers in a Failed state by running the following command in a Command Prompt with administrator privileges : vssadmin list writers
Take note of all VSS Writers where the state is not Stable
Find the VSS writer’s associated Service Display Name in the table below
To open the Services window, click the Windows start button, type “Run”, and hit enter.
In the Run window, type services.msc and click OK.
Scroll to the Service Display Name(s) that corresponds to the VSS writer error(s).
Restart the service by right clicking on the service name and selecting Start .
To confirm the action was successful and the VSS writer is returned to the Stable state with no errors, go back to the Command Prompt and rerun the ‘vssadmin list writers’ command.

List of VSS Writers and Service Names:

Was this article helpful, related articles.

Book a Demo

Backup Portal 🔒

Full Image Backup

File Backup

Cloud Backup

Backup Servers

Cybersecurity Audits

Sign-up for Newsletter

Sign-up to receive special offers and data safety-related news. Unsubscribe anytime.

Please leave this field empty.

This website uses cookies and third party services. See Privacy Policy and Terms of Service

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

In-Box VSS Writers

6 contributors

The Windows operating system includes a set of VSS writers that are responsible for enumerating the data that is required by various Windows features. These are referred to as "in-box" writers.

The MSDE in-box writer is not available in Windows Vista, Windows Server 2008, and later. Instead, the SQL Writer should be used to back up SQL Server databases. Only SQL Server 2005 SP2 and later are supported on Windows Vista, Windows Server 2008, and later.

Active Directory Domain Services (NTDS) VSS Writer

Active directory federation services writer, active directory lightweight directory services (lds) vss writer, active directory rights management services (ad rms) writer, automated system recovery (asr) writer, background intelligent transfer service (bits) writer, certificate authority writer, cluster service writer, cluster shared volume (csv) vss writer, com+ class registration database writer, data deduplication writer, distributed file system replication (dfsr), dynamic host configuration protocol (dhcp) writer, file replication service (frs), file server resource manager (fsrm) writer, hyper-v writer, iis configuration writer, iis metabase writer, microsoft message queuing (msmq) writer, mssearch service writer, nps vss writer, performance counters writer, registry writer, remote desktop services (terminal services) gateway vss writer, remote desktop services (terminal services) licensing vss writer, shadow copy optimization writer, sync share service writer, system writer, task scheduler writer, vss metadata store writer, windows deployment services (wds) writer, windows internal database (wid) writer, windows internet name service (wins) writer.

This writer reports the NTDS database file (ntds.dit) and the associated log files. These files are required to restore the Active Directory correctly.

There is only one ntds.dit file per domain controller, and it is reported in the writer metadata as in the following example:

Here is an example that shows how to list components in the writer's metadata:

At backup time, the writer sets the backup expiration time in the writer's backup metadata. Requesters should retrieve this metadata by using IVssComponent::GetBackupMetadata to determine whether the database has expired. Expired databases cannot be restored.

If the computer that contains the NTDS database is a domain controller, the backup application should always perform a system state backup across all volumes containing critical system state information. At restore time, the application should first restart the computer in Directory Services Restore Mode and then perform a system state restore.

The writer name string for this writer is "NTDS".

The writer ID for this writer is B2014C9E-8711-4C5C-A5A9-3CF384484757.

This writer reports the Active Directory Federation Services (ADFS) data files.

Windows Server 2008 R2, Windows 7, Windows Server 2008, Windows Vista, Windows Server 2003 and Windows XP: This writer is not supported.

The writer name string for this writer is "ADFS VSS Writer".

The writer ID for this writer is 772C45F8-AE01-4F94-940C-94961864ACAD.

This writer reports the ADAM database file (adamntds.dit) and the associated log files for each instance in %program files%\Microsoft ADAM\instance N \data, where N is the ADAM instance number. These database log files are required to restore ADAM instances.

Windows XP: This writer is not supported.

At backup time, the writer sets the backup expiration time in the backup metadata. Backup applications should retrieve this metadata by using the IVssComponent::GetBackupMetadata method to determine whether the database has expired. Expired databases cannot be restored.

The writer name string for this writer is "ADAM (instance N ) Writer", where N is the ADAM instance number, for example, "ADAM (instance1) Writer", "ADAM (instance2) Writer", and so on.

The writer ID for this writer is DD846AAA-A1B6-42A8-AAF8-03DCB6114BFD. This writer ID is the same for all instances.

This writer reports the Active Directory Rights Management Service (AD RMS) data files.

The writer name string for this writer is "AD RMS Writer".

The writer ID for this writer is 886C43B1-D455-4428-A37F-4D6B9E43F50F.

The ASR writer stores the configuration of disks on the system. This writer reports the Boot Configuration Database (BCD) and is also responsible for dismounting the registry hive that represents the BCD during shadow copy creation. The ASR writer must be included in any backups required for bare-metal recovery. For more information about ASR, see Using VSS Automated System Recovery for Disaster Recovery .

Windows Server 2003 and Windows XP: This writer is not supported.

The writer name string for this writer is "ASR Writer".

The writer ID for the ASR writer is BE000CBE-11FE-4426-9C58-531AA6355FC4.

The BITS writer uses the FilesNotToBackup registry key to exclude files from the BITS cache folder. The default cache location is %AllUsersProfile%\Microsoft\Network\Downloader\Cache.

In addition, the BITS writer excludes the following files from backup: the BITS state files (qmgr0.dat and qmgr1.dat), the BITS debug log file, and BITS partially downloaded files.

If the BITS download destination file is an SMB file, the client account must have a trust relationship to the server, or else backups may fail.

The writer name string for this writer is "BITS Writer".

The writer ID for the BITS writer is 4969D978-BE47-48B0-B100-F328F07AC1E0.

This writer is responsible for enumerating the data files for the Certificate Server.

The writer name string for this writer is "Certificate Authority".

Windows XP: The writer name string for this writer is "Certificate Server Writer".

The writer ID for the writer is 6F5B15B5-DA24-4D88-B737-63063E3A1F86.

The Cluster Service VSS writer is documented in the Cluster Service API documentation.

Windows Vista, Windows Server 2003 and Windows XP: This writer is not supported until Windows Vista with Service Pack 1 (SP1) and Windows Server 2008.

This writer reports the Cluster Shared Volume (CSV) data files. This writer is an in-box writer for Windows Server operating system versions; it does not ship in Windows Client.

Windows Server 2008 R2, Windows Server 2008 and Windows Server 2003: This writer is not supported.

The writer name string for this writer is "Cluster Shared Volume VSS Writer".

The writer ID for the writer is 1072AE1C-E5A7-4EA1-9E4A-6F7964656570.

This writer is responsible for the contents of the %SystemRoot%\Registration directory. The COM+ catalog is a file in %SystemRoot%\Registration with a name that follows the pattern R xxxxxxxxxxxx .clb, where xxxxxxxxxxxx is a 12-digit hexadecimal number. There can potentially be multiple such files if COM+ applications have been configured on the computer. The file that contains the current COM+ catalog is the file with the largest value of xxxxxxxxxxxx .

The COM+ class registration database depends on a registry key being backed up and hence needs to be backed up and restored together with the registry.

To restore the COM+ Registration Database, a backup application (requester) must call the ICOMAdminCatalog::RestoreREGDB method.

The writer name string for this writer is "COM+ REGDB Writer".

The writer ID for the COM+ class registration database writer is 542DA469-D3E1-473C-9F4F-7847F01FC64F.

The Data Deduplication VSS writer is documented in the Data Deduplication API documentation. This writer is an in-box writer for Windows Server operating system versions; it does not ship in Windows Client.

The following component includes a VSS writer: Distributed File System Replication (DFSR)

Windows Vista, Windows Server 2003 and Windows XP: This writer is not supported until Windows Vista with SP1 and Windows Server 2008.

This writer is responsible for enumerating files required for the DHCP server role. This writer is an in-box writer for Windows Server operating system versions; it does not ship in Windows Client.

The writer name string for this writer is "Dhcp Jet Writer".

The writer ID for this writer is BE9AC81E-3619-421F-920F-4C6FEA9E93AD.

The File Replication Service writer is documented in Backing Up and Restoring an FRS-Replicated SYSVOL Folder .

This writer enumerates the FSRM configuration files that are used for system state backup. During restore operations it prevents changes in FSRM configuration and temporarily halts enforcement of quotas and file screens. After the restore is complete, the writer refreshes FSRM with the configuration that was restored. This writer is only present when FSRM (part of File Services role) is both installed and running. This writer is an in-box writer for Windows Server operating system versions; it does not ship in Windows Client.

Windows Server 2003: This writer is not supported until Windows Server 2003 R2.

The writer name string for this writer is "FSRM Writer".

The writer ID for this writer is 12CE4370-5BB7-4C58-A76A-E5D5097E3674.

The Hyper-V VSS writer is documented in the Hyper-V API documentation. This writer is an in-box writer for Windows Server operating system versions; it does not ship in Windows Client.

Windows Server 2003: This writer is not supported until Windows Server 2008.

The IIS configuration writer is responsible for enumerating the IIS configuration files.

Windows Vista, Windows Server 2003 and Windows XP: This writer is not supported until Windows Vista with SP1 and Windows Server 2008. Requesters are required to back up the IIS configuration files, including the .NET FX machine.config file or the ASP.NET root web.config file.

This writer does not back up the .NET FX machine.config file or the ASP.NET root web.config file because these files are enumerated by the System Writer.

This writer backs up all files that are in the %windir%\system32\inetsrv\config\schema and %windir%\system32\inetsrv\config directories, except for files that are enumerated by the System Writer.

The writer ID for the IIS configuration writer is 2A40FD15-DFCA-4aa8-A654-1F8C654603F6.

The Internet Information Server (IIS) metabase writer is responsible for enumerating the IIS metabase file.

Windows Vista, Windows Server 2003 and Windows XP: This writer is not supported until Windows Vista with SP1 and Windows Server 2008. Requesters are required to back up the IIS metabase file.

The writer ID for the IIS metabase writer is 59B1f0CF-90EF-465F-9609-6CA8B2938366.

This writer reports the Microsoft Message Queuing (MSMQ) data files.

The writer name string for this writer is "MSMQ Writer ( SvcName )", where SvcName is the name of the MSMQ service the writer is associated with. For default installation, the service name is "MSMQ". For clustered instances, the service name is MSMQ$ ResourceName , where ResourceName is the clustered MSMQ resource name.

The writer ID for this writer is 7E47B561-971A-46E6-96B9-696EEAA53B2A.

This writer exists to delete search index files from shadow copies after creation. This is done to minimize the impact of Copy-on-Write I/O during regular I/O on these files on the shadow-copied volume.

Windows Server 2003: This writer is not supported.

To install this writer on the server, you must install the File Services role and enable the Windows Search Service.

The writer name string for this writer is "MSSearch Service Writer".

The writer ID for the MSSearch service writer is CD3F2362-8BEF-46C7-9181-D62844CDC0B2.

The NPS writer is responsible for enumerating the Network Policy Server (NPS) configuration files for servers that have the Network Policy and Access Services role installed.

The writer name string for this writer is "NPS VSS Writer".

The writer ID for the NPS VSS writer is 0x35E81631-13E1-48DB-97FC-D5BC721BB18A.

This writer reports the performance counter configuration files. These files are only modified during application installation and should be backed up and restored during system state backups and restores.

Windows Server 2008, Windows Vista, Windows Server 2003 and Windows XP: This writer is not supported. Requesters are required to back up these files manually. (See Backing Up and Restoring System State .)

The writer name string for this writer is "Performance Counters Writer".

The writer ID for the Performance Counters Writer is 0BADA1DE-01A9-4625-8278-69E735F39DD2.

The registry writer is reports the Windows registry files to enable in-place backups and restores of the registry. It does not report user hives.

Windows Server 2003: In Windows Server 2003, this writer uses an intermediate repository file (sometimes called a "spit file") to store registry data. (See Registry Backup and Restore Operations Under VSS .)

Windows XP: This writer is not supported. (See Registry Backup and Restore Operations Under VSS .)

The writer name string for this writer is "Registry Writer".

The writer ID for the registry writer is AFBAB4A2-367D-4D15-A586-71DBB18F8485.

This writer is responsible for enumerating the Remote Desktop Services (Terminal Services) Gateway files for servers that have Remote Desktop Gateway, a subrole of Remote Desktop Services role, installed.

This writer is an in-box writer for Windows Server operating system versions; it does not ship in Windows Client.

The Remote Desktop Services Gateway depends on several registry keys being backed up and therefore needs to be backed up and restored together with the registry.

The writer name string for this writer is "TS Gateway Writer".

The writer ID for this writer is 368753EC-572E-4FC7-B4B9-CCD9BDC624CB.

This writer is responsible for enumerating the Remote Desktop Services Licensing (RD Licensing) or Terminal Services Licensing (TS Licensing) files for servers that have Remote Desktop Licensing, a subrole of Remote Desktop Services role, installed.

Remote Desktop Services Licensing depends on several registry keys being backed up and therefore needs to be backed up and restored together with the registry.

The writer name string for this writer is "TermServLicensing".

The writer ID for this writer is 5382579C-98DF-47A7-AC6C-98A6D7106E09.

This writer deletes certain files from volume shadow copies. This is done to minimize the impact of Copy-on-Write I/O during regular I/O on these files on the shadow-copied volume. The files that are deleted are typically temporary files or files that do not contain user or system state.

The writer name string for this writer is "Shadow Copy Optimization Writer".

The writer ID for the shadow copy optimization writer is 4DC3BDD4-AB48-4D07-ADB0-3BEE2926FD7F.

Windows Server 2012 R2: This writer is included with Windows Server 2012 R2 and newer server versions. It is not compatible with desktop versions.

This writer is responsible for enumerating the sync shares on servers that have the Sync Share Service installed, and for ensuring that their metadata and data remain consistent during backup and restore.

This writer is only present when Sync Share Service is both installed and running.

There will be one VSS writer component for each sync share. This includes the metadata and data paths. These must be backed up together for consistency.

The writer name string is "Sync Share Service VSS writer".

The writer ID is D46BF321-FDBA-4A35-8EC3-454DF03BC86A.

The system writer enumerates all operating system and driver binaries and it is required for a system state backup.

This writer runs as part of the Cryptographic Services (CryptSvc) service. The system writer generates a file list that contains the following files:

All static files that have been installed. A static file is a file that is listed in the component manifest with the writeableType file attribute set to "static" or "". Static files include all files that are protected by Windows Resource Protection (WRP). However, not all static files are WRP-protected files. For example, game files are static but not WRP-protected so that administrators can change parental control settings.

The contents of the Windows Side-by-Side (WinSxS) directory, including all manifests, optional components, and third-party Win32 files.

Many of the files in the %windir%\system32 directory are hard links to files in the WinSxS directory.

All PnP files for installed drivers (owned by PnP).

All user-mode services and non-PnP drivers.

All catalogs owned by CryptSvc.

The restore application is responsible for laying down the files and registry and setting ACLs to match the system shadow copy. The appropriate hard links must also be created for a system state restore to succeed.

The writer name string for this writer is "System Writer".

The writer ID for the system writer is E8132975-6F93-4464-A53E-1050253AE220.

This writer reports the task scheduler's task files.

The writer name string for this writer is "Task Scheduler Writer".

The writer ID for the writer is D61D61C8-D73A-4EEE-8CDD-F6F9786B7124.

This writer reports the writer metadata files for all VSS express writers.

Windows Server 2008, Windows Vista, Windows Server 2003 and Windows XP: This writer is not supported.

The writer name string for this writer is "VSS Express Writer Metadata Store Writer".

The writer ID for the writer is 75DFB225-E2E4-4D39-9AC9-FFAFF65DDF06.

This writer reports the Windows Deployment Services (WDS) data files.

The writer name string for this writer is "WDS VSS Writer".

The writer ID for this writer is 82CB5521-68DB-4626-83A4-7FC6F88853E9.

This writer reports the Windows Internal Database (WID) data files.

The writer name string for this writer is "WIDWriter".

The writer ID for this writer is 8D5194E1-E455-434A-B2E5-51296CCE67DF.

This writer is responsible for enumerating files required for WINS.

The writer name string for this writer is "WINS Jet Writer".

The writer ID for this writer is F08C1483-8407-4A26-8C26-6C267A629741.

This writer is used for identifying WMI-specific state and data during backup operations. The data includes files from the WBEM repository.

The writer name string for this writer is "WMI Writer".

The writer ID for this writer is A6AD56C2-B509-4E6C-BB19-49D8F43532F0.

Was this page helpful?

Submit and view feedback for

Additional resources

Optus outage updates: Services 'gradually' restored as experts warn outage exposes serious vulnerabilities in Australian networks — as it happened

This blog is now closed. For the latest on the Optus outage head to today's blog .

Optus says some services are "gradually being restored" but it may take a "few hours" for all connectivity to return after a huge outage that affected more than 10 million customers on Wednesday.

Look back on what happened in our blog.

8:53 AM 8:53 AM Wed 8 Nov 2023 at 8:53am Cyber security expert says Optus's redundancies likely failed
8:30 AM 8:30 AM Wed 8 Nov 2023 at 8:30am Optus could suffer serious reputational damage, marketing expert says
8:01 AM 8:01 AM Wed 8 Nov 2023 at 8:01am Some Optus customers say they're still having trouble accessing services

Live updates

This is where we stand.

By Dannielle Maguire

Here's a quick recap of what's been happening today.

Optus mobile and internet services were down across the country.

The company's chief executive Kelly Bayer Rosmarin said that happened at about 4am AEDT.

People with Optus landline phones were unable to call triple-0.

And some people were unable to call triple-0 from their mobiles — although many did have that capability.

At about 1pm ADET — some nine hours after the outage first hit — some customers reported having mobile signal again.

Here's what the company posted on social media:

"Some services across fixed and mobile are now gradually being restored. "This may take a few hours for all services to recover, and different services may restore at different sites over that time."

Optus hasn't said what caused the outage, except that it was a "technical network fault".

Ms Bayer Rosmarin said there was no indication the outage was caused by a cyber attack or hack.

We'll wrap up our live coverage here

By Audrey Courty

Thank you very much for joining us today as we brought you live coverage of the Optus outage.

We hope that you are safe and well.

Please take care and good night.

'There is a fragility' in Australia's telco systems, cyber security expert says

CEO of the Cyber Security Cooperative Research Centre, Rachael Falk, has echoed engineers and digital security experts in saying that today's outage exposed how vulnerable Australian telcos are.

"There is a fragility there, absolutely. It is one that I think we all need to consider and we can't go backwards from the reliance, but what we can do is understand the fragility of the telco network," she told ABC's Sarah Ferguson. "I think governments get that. There's a bunch of legislation around network security. But, today, 12 hours was a long time to be without crucial services. "It highlights that telecommunications companies are the back bone of everything connected to the internet. If a telco goes down ... you literally cannot function."

'Today wasn't a day to be a shy CEO,' Falk says

ABC's Sarah Ferguson has asked Rachael Falk what she thought about Optus's communication with customers today.

Falk used to be Telstra's National Security Advisor and is now the CEO of the Cyber Security Cooperative Research Centre.

"Today wasn't a day to be a shy CEO. You needed your CEO front and centre out today, early in the morning, hitting every major network, giving pressers left, right and centre. You can't have enough communication on a day like today," she said. "Unfortunately, I don't think we saw that. I'm prepared to forgive Optus for potentially being all on the Optus network but today was not the day for the Optus CEO to be shy."

Cyber security expert says Optus's redundancies likely failed

Rachael Falk, who is the CEO of the Cyber Security Cooperative Research Centre, has spoken to ABC's Sarah Ferguson.

She was asked whether the Optus outage meant that the telco didn't have enough layers of redundancy to prevent a major failure.

"I think that is right," Falk said. "You can call it whatever you want, the CEO can say, deep technical faults, major engineering issue — it is what it is. It had significant consequences."

Ferguson then asked Falk why she thinks the service took so long to be restored.

"I can only imagine a couple of things. They realised it impacted all their services ... and I don't know this, but I suspect they were also all themselves internally using Optus devices," Falk said. "If you are reliant on your own Optus mobile and you're execs and have Optus Wi-Fi and mobile, you all can't communicate — I imagine that caused a bit of a problem."

Optus could suffer serious reputational damage, marketing expert says

A marketing expert says today's Optus outage may do serious reputational damage.

Optus also came under fire last year after it was hacked, leading to information leaks affecting more than 2.5 million customers.

Australian National University marketing expert Dr Andrew Hughes says this latest incident could do even more damage.

"The one last year, by the way, their brand value slipped by around one billion dollars in 2022 — that's how big it was," he says. "So this time around you can sort of expect to have maybe even a bit higher because the people that stayed with them last time, may be thinking again this time, 'You know what, we keep on hearing the same language, but we're seeing the same action as well'."

Did Optus's contingencies fail?

A digital security researcher from the University of Queensland says telecommunications operators are by law required to have contingencies in place for incidents like today's outage.

"The question really is was this such a big incident it actually might have affected the redundancies Optus already had in place," Dr Brendan Walker-Munro said. "And if that's the case, then it's actually a really big problem for Optus that they're going to want to address quickly."

Echoing Engineers Australia, he said the Optus incident shows when critical infrastructure stops working, the effects can be widespread.

"And it's not just at the individual level, you're also talking about those market businesses, people who can't use EFTPOS, it really has a big ripple effect through society."

Some Optus customers say they're still having trouble accessing services

Some of our readers say they still haven't been able to access their mobile and internet services after Optus announced they were restored.

These comments were sent to us in the past half hour.

WiFi still not working, and mobile data is back but very very shaky. Disappointed they'd blanket say everything is resolved. - Sarah

Feels a bit disingenuous from Optus to say "restored" when that clearly isn't 100% so. My Optus NBN is still out, and I've given my equipment a couple of chances to restart in the last half hour - Nick

Optus says it's customers should now have their internet back ,However we still have no Internet on hold with Optus😞 - Margaret Bay

NBN in Brisbane is still not restored, contrary to what the Optus CEO is saying. Appalling treatment of customers and my last day of being an Optus customer after 18 years. - Pat

Engineers Australia urges businesses to assess their systems for weak points

Engineers Australia has also urged businesses to to assess their systems for weak points amidst the Optus network disruptions.

"Cascading risk can result from various factors, such as extreme weather events, cyberattacks, or geopolitical events," Chief Engineer Jane MacMaster says. "Australia has witnessed several instances of cascading risk in the past, including the 2016 electricity system blackout in South Australia and the recent impact on transport networks and vital services during bushfires. "I think a lot of companies across Australia today – small, medium enterprises and the larger ones — will be internalising this a little bit and focusing on their own systems to understand where are our risks, where are our quality management systems, where do we need to put more focus to make our vulnerability as low as we can make it."

MacMaster says although we should expect these sorts of disruptions to be kept at a minimum, it will require "a concerted effort" on risk and quality management to keep them that way.

The Optus outage has exposed vulnerabilities in Australia's telco networks, engineers say

Engineers Australia says the Optus outage has exposed vulnerabilities in Australia's telecommunications networks.

Jane MacMaster, who is the Chief Engineer at Engineers Australia, says outages like this create a domino effect on our digital systems and economy.

"I think society is heading in a direction where we're very reliant on modern technology and part of the challenge is that technology is becoming increasingly complex and increasingly connected," she says. "So if there's a problem in one part of all our systems it's very easily felt in other parts because the connections are there."

Today's outage disrupted everything from trains to hospitals, bank call centres, information lines, and the ability of millions of consumers to access services.

The outage even disrupted some gym workouts

A gym in Canberra had to scramble to put together impromptu classes and turned away a handful of clients after all of their systems went down this morning.

UBX Belconnen manager Christopher Murphy said it had been "panic stations" for staff throughout the day as the gym relied on a constant feed of circuit-style workouts fed through WIFI-connected TVs for its operations.

Gym manager Christopher Murphy. He is wearing a black tank top. He has short black hair and has tattooed arms.

Mr Murphy said the event had put a lot of strain and extra staff had to be called in to try and manage the disruption by making up workouts and resorting to whiteboards with instructions.

"Our operations were messed around … it does put a sour taste in people's mouths because this is their stress relief," he told the ABC.

"Internet service is a needed service — we just want reliability."

Mr Murphy said the gym would likely change internet providers after the disruption.

Reporting by Lottie Twyford

'Restored': Optus says customers should now be able to get back online

Optus has posted a new update on X, formerly known as Twitter, confirming that their services have been restored and "customers should now be able to be back online".

The telco, once again, thanked customers for their patience.

Why am I still not getting service?

Service has not been fully restored. Optus NBN is still down! - Ben

While Optus's CEO Kelly Bayer Rosmarin has said that the telco's services are now fully restored, there may still be a delay before that change takes effect on your personal device.

"The way that we restored services meant that we had to bring services online on a progressive basis so that has been rolling out throughout the day," Rosmarin said.

About half an hour ago, Optus told customers on its website that it was "continuing" to restore connectivity.

It said the service should restore automatically, though some customers may need to restart their device or turn airplane mode on and off again.

What is a 'deep network' problem?

Earlier today, Communications Minister Michelle Rowland described the Optus outage as a "deep network" problem.

Now, Optus chief Kelly Bayer Rosmarin has revealed that it was a "technical network fault" but did not provide further details.

So what does that actually mean?

Here's an explanation of the factors that can cause such events:

WATCH: Optus CEO apologises for the outage

Optus chief Kelly Bayer Rosmarin has just spoken to ABC's News Channel about the outage.

You can watch the full interview below:

'Services are continuing to be restored,' Optus says

Optus has just posted a new update on its website.

It says internet and phone services "are continuing to be restored".

"Service will be automatically restored," the statement says.

"Some customers may need to restart their device or turn airplane mode on then off."

Here's the rest of the statement:

Optus CEO says the outage was 'a very rare occurrence'

Optus CEO Kelly Bayer Rosmarin has repeated her apologies for the outage but says the company cannot provide further detail about the outage until it conducts a thorough investigation.

"In my three and a half years, as the CEO of Optus, we've never had an outage of this nature," she said. "So it's a very rare occurrence, but unfortunately, it does happen. It happens to telcos all around the world. It happens to other telcos in Australia. "We try and avoid it happening and we will make sure we learn as much as we possibly can from what occurred and hopefully keep it as an extremely rare occurrence."

You can read more about what she said here:

BREAKING: Optus says a 'technical network fault' was to blame

Optus CEO Kelly Bayer Rosmarin says the company's services have been restored after today's major network outage affected millions of Australians.

In an interview with the ABC, she said the cause was a "technical network issue" and a "thorough, root-cause analysis" would be conducted by the company before more information could be provided.

Ms Bayer Rosmarin said such an outage was a "very rare occurrence" that happens to telcos around the world, including to other telcos in Australia.

When asked about possible compensation, she said the company had been focused on restoring services but "would now start thinking about ways in which we can thank customers for their patience... and rewarding them for their loyalty to Optus".

'Cash only due to Optus outrage'

Regarding the earlier post titled "Adelaide businesses resort to cash only sales", I had to laugh a the sign in the picture affixed to the bowser: "cash only, due to Optus outrage"... Fairly accurate summary of events - intentional or not! - Lain

Well-spotted, Lain!

For those of you just tuning in, here's the picture we shared earlier as reference:

A sign at a petrol sign says 'cash only due to Optus outrage, sorry for inconvenience'

NT retail workers frustrated at loss of customers, sales

At the Northern Territory’s largest shopping centre, Casuarina Square in Darwin, businesses and customers have been impacted by the outage.

One handbag store has been unable to make any sales, with staff estimating it has lost $1,000 in business.

Kalliopi Hatzimihali, who manages a store at the centre, said when she tried to serve customers, no payments could be processed.

"It’s really hard, because I am trying to fix it, but I can’t,” she says.

"We’re losing customers. We’re losing sales."

Tianna Gilchrist standing in a shopping centre

Retail employee Tianna Gilchrist said she was furious and wanted to change phone providers.

"I was affected by the cybersecurity breach last year as well,” she said.

Reporting by Myles Houlbrook-Walk

How to manually restart VSS Writers in a failed state without Rebooting Server.

Oct 26, 2021 • Consolidated Knowledge Type

Description:.

Find each of the VSS writers in a failed state by using the command in command prompt (Run As Administrator) - ' vssadmin list writers '.
Mark and copy all the failed VSS writers.
Find the VSS writer's associated Service Display Name in the table below and restart the service.

Run another Backup/snapshot.
If the VSS writers fail again, it would be necessary to restart the server.

Article Information

How to manually restart VSS Writers in a failed state without Rebooting Server.

Oct 27, 2021 • consolidated knowledge type, information, description:.

Find each of the VSS writers in a failed state by using the command in command prompt (Run As Administrator) - ' vssadmin list writers '.
Mark and copy all the failed VSS writers.
Find the VSS writer's associated Service Display Name in the table below and restart the service.

Run another Backup/snapshot.
If the VSS writers fail again, it would be necessary to restart the server.

Nothing here yet?

Number of Views 11.67K
Number of Views 742
Number of Views 711
Number of Views 1.91K
Number of Views 1.04K

vss writers services to restart

IMAGES

VIDEO

COMMENTS

Oct 26, 2021 • Consolidated Knowledge Type

Article Information

Trending Articles

VSS Writer Failed: Re-registering VSS Writers on Windows Server

Limited Wi-Fi Access in Windows 10 and 8.1 – Troubleshooting

Leave a Comment Cancel Reply

Restart VSS Writers without a reboot

Published by Kevin Wiblin

Leave a Reply Cancel reply

Carbonite Support > List of VSS Writers and Servic...

List of VSS Writers and Services

Related Articles:

Definitions

Common Articles

Clearing Failed States on VSS Writers Without Rebooting

Catalogic experts are here to help you.

How to manually restart all VSS writers when in a failed state without rebooting

5 Steps total

Step 2: Make a list of all the failed VSS writers or take a screenshot.

Step 4: Issue the command again to confirm the status has changed Stable with no Error - vssadmin list writers.

Restarting VSS Writers with PowerShell script

I’m not interested in your code, I just want to restart these VSS Writers #

Let’s talk PowerShell #

Get-KPVssWriter #

Select-String #

PsCustomObject #

Restart-KPVssWriter #

Happy ever after #

Articles VSS Writer Failed / How to Restart and Re-Register VSS Writers

Jun 25, 2020 • Break Fix

Trending Articles

Reset VSS Writer & Lookup Display Name

List of VSS Writers and Service Names:

Sign-up for Newsletter

In-Box VSS Writers

Active Directory Domain Services (NTDS) VSS Writer

Additional resources

Optus outage updates: Services 'gradually' restored as experts warn outage exposes serious vulnerabilities in Australian networks — as it happened

Live updates

We'll wrap up our live coverage here

'There is a fragility' in Australia's telco systems, cyber security expert says

'Today wasn't a day to be a shy CEO,' Falk says

Cyber security expert says Optus's redundancies likely failed

Optus could suffer serious reputational damage, marketing expert says

Did Optus's contingencies fail?

Some Optus customers say they're still having trouble accessing services

Engineers Australia urges businesses to assess their systems for weak points

The Optus outage has exposed vulnerabilities in Australia's telco networks, engineers say

The outage even disrupted some gym workouts

'Restored': Optus says customers should now be able to get back online

Why am I still not getting service?

What is a 'deep network' problem?

WATCH: Optus CEO apologises for the outage

'Services are continuing to be restored,' Optus says

Optus CEO says the outage was 'a very rare occurrence'

BREAKING: Optus says a 'technical network fault' was to blame

'Cash only due to Optus outrage'

NT retail workers frustrated at loss of customers, sales

Oct 26, 2021 • Consolidated Knowledge Type

Article Information

Trending Articles

How to manually restart VSS Writers in a failed state without Rebooting Server.

Nothing here yet?

Related Articles

Trending Articles

IMAGES

VIDEO

COMMENTS