Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Error: Failed to restore Orion DB backup The media set has 2 media families but only 1 are provided

Error: Failed to restore Orion DB backup The media set has 2 media families but only 1 are provided

Created by Malik Haider, last modified by MindTouch on Jun 23, 2016

Views: 1,244 Votes: 0 Revisions: 4


This article describes the issue when you receive the following error error while restoring Orion DB backup  to new SQL Server:

Failed to restore Orion DB backup The media set has 2 media families but only 1 are provided




All versions of NPM 


This error message occurs because the original backup was done as a striped backup where the backup stream was split into two destination files.

When attempting to restore, you need to specify all of the same files which were used to take the backup.


This works similar to RAID1, which means, we do not have one set of data on one file and another set of data on the other one. How it works is the data is inerspersed between the two files, which is the behavior that gives optimum performace.  One of the unfortunate results of this is you cannot get any data out of a subset of the backup files used to create the backup.


The reason that you cannot do a backup adding on to one of these files is that the files themselves are initialized to understand that they are part X of a Y-part backup. If you specify only one file, it doesn't fit.

You can always perform a backup by specifying a new backup file, and using WITH INIT.


If you don't need to stripe the backups across multiple files for performance reasons, go with a single destination for management simplicity.


The simple version is:

If you back up to two files, you must specify two files to restore from. If you back up to five files, you must specify five files to restore from, etc.


You cannot restore any data from less than the full set of files used for the backup.  This isn't like RAID 5 where we can synthesize missing data, nor is it a continuation volume, where we could restore up to the missing bit.



We recommend to consult your DBA for any further action to restore all the DB files as explained under this post:


Last modified