Quantcast
Channel: All Data Protector Practitioners Forum posts
Viewing all articles
Browse latest Browse all 10494

Re: Media object copy from command line; how?

$
0
0

Ulrich Windl wrote:

I wrote a script that selects from all protected media those who have less than 50% of the used capacity protected (Data Protector cannor do that!). Now I'd like to create a media object copy job by script that copies all the protected objects form the media found in the previous step to another media (to free the source media completely).


I reckon that's not explicitly provided by DP because it's a situation better to be avoided in the first place. It may build up occasionally by accident (wrong protection on some backups/copies, fixed later) or due to churn in long term protected media (objects were protected for years or even permanently, then some part of the objects became irrelevant and their protection was revoked or shortened). In such cases, the Interactive Copy GUI is usually enough to fix it. I would not go to the extreme of trying to automate this (except maybe when I inherit a heap of such media that grew out of bounds already, but not to be part of regular backup ops), instead to fix it at the source. Objects with different protections should funnel into different pools and if that means there are a lot of them, consider using a free pool to simplify the media lifecycle. Or unify the protections into less classes than you had before. Or both.


It seems to me I can only run such a copy interactively from the GUI (or the manual pages are way too incomplete).
Can anybody tell me how to start such a command from command line? I'm using Linux for the Cell Manager...


Ignoring the manpage for a second, I had a look into omniobjcopy -help and most of what I know from the GUI seems to be reflected there one way or another. So if you already have a list of objects you need to copy, the format

omniobjcopy [GeneralOptions] Object [Object] ... [Device] ...

looks quite right. You apparently have to know the individual object's type, name (a tuple specific to the type), session ID and ideally copy ID to make the selection unique, but that's not really different from the GUI methinks. What's missing?

HTH,
Andre.


Viewing all articles
Browse latest Browse all 10494

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>