So I run
omnidb -winfs dc01.corp.testbackup.com:/C 'C:' -session 2014/08/04-1 -catalog
and the result is "Object not found". I write the exact Object name which it provides in my first command.
What the reason could be?
-------------
'jruffer' is quite right, the syntax on some of these commands is quite demanding, and will tolerate no deviation. It took me years to understand most (but not all) of the ins and outs of commands
A command for a UNIX-based file system object would have the argumant '-filesystem' and need single quotes around the Object description
A command for a Windows-based file system object would have the argumant '-winfs' and need double quotes around the Object description
This is going to be true for any commands that needs an Object name , like 'omnidb' or 'omnir'
===============
Page 116: omnimlist –catalog [DiskAgentID]
so I type: omnimlist –catalog 1407141329
-> why it doesn’t work?It doesnt recognize the command.
'omnimlist' is a comand to read right off the media. You would be requird to state a logical device, a slot number, if application, and any number of options. For example
omnimlist -device "LTO Drive 1" -slot 14 -monitor -catalog
You may have taken the command a little out of context
omnimlist -device BackupDevice -catalog [-slot SlotID [Side]] [-monitor]
omnimlist -device BackupDevice -catalog DiskAgentID [-slot SlotID [Side]] [-monitor]
Each object has a Disk Agent ID, so you could use this to get a catalog for just that object, as opposed to the entire media