\n#!perl -I..\/lib\/perl -X -CA<\/p>\n### needed modules
\nuse Omniback;<\/p>\n
# Get DP folders
\nmy $OMNIHOME = Omniback::CmnQuotePath($Omniback::PAN{'BASE'});
\nmy $OMNIHOME_STR = $OMNIHOME;
\n$OMNIHOME_STR =~ s\/\\\"\/\/g;
\nmy $OMNIBIN = \"\\\"${OMNIHOME_STR}\/bin\\\"\";<\/p>\n
# define the exclude pools, pool for vaulting, ...
\n$exclude_pools=\"Pool1,Pool2,PoolX\";<\/p>\n
# the pool mus exist in DP
\n$vault_pool=\"Vaulting\";<\/p>\n
# the time frame to retriev the session information
\n# assuming the script should run monday 8am, the timeframe of
\n# 60 month covers backups starting friday evening
\n$timeframe_start=\"60\";
\n$timeframe_duration=\"60\";<\/p>\n
# the stuff needed to send a mail at the end of the script
\n# you need to download blat (mail program) search for blat at google<\/p>\n
$mailrecipient=\"firstname.lastname\\@domain.com\"; \t\t# please remind the quoted (at)
\n$mailserver=\"192.168.2.10\"; \t\t\t\t\t# the ip address of the smtp server
\n$mailsender=\"dataprotector\\@domain.com\";\t\t\t# please remind the quoted (at)
\n$mailsubject=\"Media vaulting\";\t\t\t\t\t# Subject for the mail<\/p>\n
print \"Generating Report\\n\";
\nprint \"- skipping pools: $exclude_pools\\n\";
\nprint \"- target pool is: $vault_pool\\n\";
\nprint \"- start time: $timeframe_start\\n\";
\nprint \"- duration: $timeframe_duration\\n\";
\nprint \"\\n\\nNote: Ignore messages regarding \\\"No medium found\\\"\\n\\n\";<\/p>\n
@exec=`${OMNIBIN}\/omnirpt -report list_sessions -timeframe $timeframe_start $timeframe_duration -tab`;
\nforeach (@exec)
\n{
\n\tchomp $_;
\n\tnext if \/^#\/;
\n\t(@sessionid)=split(\/\\t\/,$_,23);
\n\tpush(@sessions,$sessionid[22]);
\n}<\/p>\n
foreach (@sessions)
\n{
\n\t@exec=`${OMNIBIN}\/omnidb.exe -session \\\"$_\\\" -media`;
\n\t$media = $exec[2];
\n\tchomp $media;
\n\t($media_short,$dummy)=split(\/ \/,$media,2);
\n\tif ($media_short ne \"\")
\n\t{
\n\t\tpush(@media,$media_short);
\n\t}
\n}<\/p>\n
@newmedia=&del_double(@media);<\/p>\n
print \"Summary\\n\";
\n@movedmedia=();
\nforeach (sort(@newmedia))
\n{<\/p>\n
\t($media1,$dummy)=split(\/ \/,$_,2);
\n\t$media1 =~ s\/\\[\/\/ig;
\n\t$media1 =~ s\/\\]\/\/ig;<\/p>\n
\t@exec=`${OMNIBIN}\/omnimm -media_info \\\"$media1\\\" -detail`;
\n\t$pool = $exec[2];
\n\tchomp $pool;
\n\tchop $pool;
\n\t$pool =~ s\/Pool name : \/\/ig;
\n\tif ($exclude_pools =~ \/$pool\/)
\n\t{
\n\t\tprint \"skipping media: $media1 \\n\";
\n\t}
\n\telse
\n\t{
\n\t\tprint \"moving media: $media1 \\n\";
\n\t\t@exec=`${OMNIBIN}\/omnimm -move_medium \\\"$media1\\\" $vault_pool`;
\n\t\tpush(@moved_media,$media1);<\/p>\n
\t}
\n}<\/p>\n
$anzahl=@moved_media;
\nif ($anzahl gt 0)
\n{
\n\t$message=\"\";
\n\t$message=\"Vaulting media:\\n============================\\n\\n\";
\n\t$message=$message.\"Following media were moved to pool: $vault_pool for vaulting.\\n\";
\n\t$message=$message.\"Media:\\n\";
\n\tforeach (@moved_media)
\n\t{
\n\t\t$message=$message.$_.\"\\n\";
\n\t}<\/p>\n
\t$message=$message.\"\\n\\nMail generated by robot\\n\\n\";
\n\t`${OMNIBIN}\/blat -to $mailrecipient -f $mailsender -subject \\\"$mailsubject\\\" -body \\\"$message\\\"`;
\n}<\/p>\n
exit;<\/p>\n
sub del_double{
\nmy %all;
\ngrep {$all{$_}=0} @_;
\nreturn (keys %all);
\n}
\n<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"
Der Wunsch die Daten seiner Server auf Medien zu sichern und somit Datensicherheit zu erhalten h\u00f6rt nicht nur bei der Datensicherung auf Band auf, oft besteht auch der Wunsch oder Anforderung die beschriebenen B\u00e4nder vor weiterem Beschreiben zu sch\u00fctzen oder die Medien aus der Bandlibrary zu entfernen und an einem sicheren Ort (Tresor, Ausfall Rechenzentrum, …) zu verwahren. Jeder […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[11],"tags":[129],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"de","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-dM","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1819,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2014\/01\/storeonce-success-story-australia\/","url_meta":{"origin":854,"position":0},"title":"StoreOnce success story from Australia","date":"27. Januar 2014","format":false,"excerpt":"{:en}Recently I asked you to share your StoreOnce success story. Here is a awesome story and a good example for federated deduplication from a company in Australia. Before using HP StoreOnce, the company used to protect its data in the two datacentres using HP Data Protector. The data (FileSystems, MS\u2026","rel":"","context":"In "SCD"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":694,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/07\/data-protector-migration-unix-to-other-os\/","url_meta":{"origin":854,"position":1},"title":"Data Protector Migration Unix to other OS","date":"29. Juli 2011","format":false,"excerpt":"{:de}Ich kenne nicht viele gute Gr\u00fcnde warum man eine Data Protector Installation von HP-UX auf ein anderes Betriebssystem wechseln sollte,\u00a0dennoch gibt es viele Kunden die diesen Schritt gehen wollen und zum Beispiel auf Windows oder Linux wechseln;\u00a0meist noch verbunden mit einem Upgrade auf eine aktuelle Version von Data Protector.\u00a0Und hier\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2395,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2015\/09\/future-tape-technology\/","url_meta":{"origin":854,"position":2},"title":"The future of the Tape Technology","date":"25. September 2015","format":false,"excerpt":"{:en} Many customers continue to rely on tape storage to protect their business critical applications and data. The benefit to continue performing classic backup is obvious: Tape storage is cheap compared with backup-to-disk technolgies. In a TCO consideration lower cost per GB and lower energy costs are speaking for an\u2026","rel":"","context":"In "Common"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1478,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2013\/07\/write-device-parameter-incorrect\/","url_meta":{"origin":854,"position":3},"title":"Cannot write to device – the parameter is incorrect","date":"5. Juli 2013","format":false,"excerpt":"{:en}When using the wrong block size for the tape devices, you may get the error message Cannot write to device ([87] The Parameter is incorrect.) during the backup or while formatting media. This error may occur if as SAS library, attached to the controller P212-ZM is used. When you try\u2026","rel":"","context":"In "HowTo"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":211,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2010\/10\/initialization-of-medium-failed-filelibrary-full\/","url_meta":{"origin":854,"position":4},"title":"Initialization of medium failed – filelibrary full","date":"22. Oktober 2010","format":false,"excerpt":"{:en}The error Initialization of medium failed is shown when the Filelibrary is full or almost full (one or more mountpoints \/ folders in filelibrary). If you did not install the GR Patches from July 2010, you may also see a lot of media with blue question mark withhin the mountpoint\u2026","rel":"","context":"In "Bugs"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":815,"url":"https:\/\/www.data-protector.org\/wordpress\/de\/2011\/11\/data-protector-cases-and-hp-support\/","url_meta":{"origin":854,"position":5},"title":"Data Protector Cases and HP Support","date":"30. November 2011","format":false,"excerpt":"{:de}Nicht immer ist Software von Fehlern befreit und eine Funktion im Data Protector arbeitet nicht wie gew\u00fcnscht oder liefert nicht das notwendige Ergebnis. In diesen F\u00e4llen ben\u00f6tigt man die Unterst\u00fctzung von Support um einen m\u00f6glichen Fehler zu identifizieren, zu analysieren und zu beheben. Nachfolgend findet ihr ein Anleitung wie man\u2026","rel":"","context":"In "Common"","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/854"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/comments?post=854"}],"version-history":[{"count":25,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/854\/revisions"}],"predecessor-version":[{"id":2708,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/posts\/854\/revisions\/2708"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/media?parent=854"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/categories?post=854"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/de\/wp-json\/wp\/v2\/tags?post=854"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}