Why does a CMS disk get backed up as NON-CMS

Products

• VM:Backup for z/VM
• VM:Backup High-Speed Disaster Recovery Option (HiDRO)

Issue/Introduction

I have not checked for other disks but our VMANAGER 191 gets backed up as NON-CMS and I cannot figure out why.
Here's a line from the DAILY report;

 VMANAGER 0191 2 266 LOGICAL CKD NON-CMS

Here is the MDSIK statement from the directory:

MDISK 191 3390 4738 500 WSSG04 RR

I do not use VMANAGER on a daily basis but it does not appear corrupt or anything like that. I needed to restore a local exec and then noticed the NON-CMS thing. There is probably a simple explanation - please help me determine why. 

Environment

Release:
Component: VMB

Resolution

Non-CMS minidisks are those not formatted for CMS. VMANAGER's 191 is a CMS minidisk and is typically backed up as such. Suggested that customer reformat minidisk and restore/load files back.