• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Volume "MS Configuration" complains because of size

FloydATC

ADSM.ORG Member
#1
[SOLVED] Volume "MS Configuration" complains because of size

I'm trying to use FastBack 6.1.9.0 to back up the local drives on a machine running Windows Server 2008 R2. The physical drives are all well under 2TB, in fact the largest drive is 900GB and disk 0 which holds C: and the boot sector is 300GB. There are several very large SAN volumes attached to the server via HBA but I'm not trying to back those up. Still, when trying to back up the "MS Configuration" object, FastBack complains:

Code:
1409994003,[06.09.2014 09:00:03]-> FBSS1535I        A full snapshot (6) for (servername) Policy on Signature 0xf23543f3 on (servername) VolLetter [B]MS Configuration[/B] was started                                                                     
1409994003,[06.09.2014 09:00:03]-> FBSS7563E        The job 6 was stopped because the volume 0xf23543f3 is on a disk that exceeds 2TB in size. Volumes must be on disks that are less than 2 TB in size. Remove this volume from the policy and run the snapsho...
I don't know what exactly the "MS Configuration" object is but I'm guessing it's similar to the "System State" target in BA Client? Any advice on how to solve this problem?
 
Last edited:

FloydATC

ADSM.ORG Member
#2
Figured it out. The "MS Configuration" object has nothing to do with "System State", it's the partition information for disks partitioned using GUID Partition Table (GPT) as opposed to the traditional Master Boot Record (MBR) format. In our case, GPT is used for the SAN volumes only. This means I can safely exclude the "MS Configuration object" and suddenly everything worked as expected.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 17 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 53 60.9%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.5%
  • Other (please comement)

    Votes: 7 8.0%

Forum statistics

Threads
31,471
Messages
134,133
Members
21,569
Latest member
srinathkodela
Top