Forum Discussion

apomazkin's avatar
apomazkin
Level 5
12 years ago
Solved

Storage problem: Ready; Invalid storage device

There are 3 BE2012 servers: one management and two media servers.

At first, I upgrade menegement to BE2014.
And get problems with backup job on media server's storages. There was status:"Ready; Invalid storage device".
On the upgraded management server jobs worked succesfull if they backed up to management server's storage.

And if i go to Backup Definition Properties and then to Backup Options, and then to Storage, I can't select storages of media servers.
There are only: Any disk storage and Any virtual disk storage. No one servers:

storage_1.jpg

Haw can I select any media server's storage?
I try to create new job, but there are only management stprage appear, not media server's storages.

And then, i upgraded one media server to 2014, but problems with "Ready; Invalid storage device" not disappeared.

I guess, this is problems on management server.

This is storage settings on server: 
storage1.jpg

 

  • I found the answer!
    After upgrading, backup exec server become Standalone server.
    I see it, typing in Powershell: Get-BECentralAdministrationBackupExecServer 
    and get this:
    Get-BECentralAdministrationBackupExecServer : This Cmdlet can only be executed
    on a Backup Exec server of type 'CentralAdministration'.
    At line:1 char:1
    + Get-BECentralAdministrationBackupExecServer
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    and commanlet  Get-BEStandaloneBackupExecServer return right answer.

    But in storage tab there was all managed server with error in topic.

    I reinstall this server in CASO mode and all works fine!!!

14 Replies

  • My step:
    1. hold all jobs.
    2. upgrade CASO! and on this step CASO bacome a stand-alone server.
    3. upgrading MMS - and all of this MMS bacame managed. but CASO did'nt work.

    after reinstall(uncheck CASO and check in again in installation menu) all work fine.
    i never do enything with MMS after upgrade.

  • It really shouldn't be doing that, and I would do the following to be honest:

    1. Check the Known Issues section to see if your problem is listed there...if it is, then vote it up.

    2. Log a call with Symantec so that they are aware of it...

    Thanks!

  • I suspect the issue: BE 2012 CASO was installed in Windows 2012. This OS is upsupported.

  • OK that wasn't mentioned in the original post. Might also have been the case...