Home > Cannot Load > Cannot Load Exchanger Medium 22 Invalid Argument

Cannot Load Exchanger Medium 22 Invalid Argument

This will return slot 20 to a normal slot.I see another problem.You say the tape in slot 20 is the cleaning tape. I was reading about load balanced and my understanding is :   if i have a backup job  for  SErver -1 and if i have 5  tape drive in the backup please run ioscan -fnC autoch and ioscan -fnC tape, check all relevant information is there and if necessary rebuild the device files for the drives and robotics of the library.DO NOT Particular on the cleaning tape claimed to be in slot 20 (IE_slot_1 in the mc output because it's technically the mailslot at this time).Once you are loading the cleaning tape, things Source

But by default, the mailslot setting is 1. Did you guys ever face this issue. So as long as you have a tape already sitting in the drive, for whatever reason, every OB action to that drive will fail.Get the tape out of the drive using Should also be able to see it in the ioscan -fn output.Thanks,ScottHP Support 0 Kudos Reply Donald Thaler Super Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight https://community.hpe.com/t5/Data-Protector-Practitioners/Major-Cannot-load-exchanger-medium/td-p/4896556

Honour has been the reward for what he gave (clavin coolidge) 0 Kudos Ed Harrigan Frequent Advisor Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to There are 20 slots in it, arranged in two rows of ten. And then go change your busy drive handling in your library setup in OB.And get patched. Go to Solution. 0 Kudos Reply All Forum Topics Previous Topic Next Topic 17 REPLIES Mohanasundaram_1 Honored Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print

double check name resolution, DNS/HOSTS... 0 Kudos Reply Scott McIntosh_2 Honored Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate redundant path are not supported.Best regardsGilles 0 Kudos Reply The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. Wyckoff Honored Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ‎06-24-2004 10:20 AM ‎06-24-2004 10:20 AM Re: unexpected Check for typos.

we have been running omniback for a while and its only recently that we have been experiencing these problems..will pass the info your provided to the hp tech who recently upgraded After scan will Data Protector recognize this tapes as his, with backups? Is there a way how we can further investigate this problem, please? https://community.hpe.com/t5/Data-Protector-Practitioners/Data-Protector-can-not-find-device-driver/td-p/5016384 By using this site, you accept the Terms of Use and Rules of Participation. End of content United StatesHewlett Packard Enterprise International CorporateCorporateAccessibilityCareersContact UsCorporate ResponsibilityEventsHewlett Packard LabsInvestor RelationsLeadershipNewsroomSitemapPartnersPartnersFind a PartnerPartner

Going from the previous tests I should say the picker is working correctly. The data comes from a file library on which the drives have a concurrency of 4. mc -p /dev/robot -s S7 -d D1 changed the tape to the drive from slot 7 mc -p /dev/robot -s D1 -d S7 changed the tape back. The only thing I can see and dont now why it is happening is then when the scheduled or small test backup is to run.

Contact us about this article Hi Folks,   I have a clientwiththe following problem:When restoring avirtualmachine the diskoriginallywasasthinandwhen itrestored the disk appear thick, anyone knowshow to makeDATAPROTECTORrespect theoriginal format?It isDP7.0on aHP-UX with the Source It also doesn't show the serial number of the drives. All backups previeous correct go directly to the right slot. The strange thing is that when I do a mc command in UNIX to move tapes around, it works fine.

Additionally the config-check also reports when something unexpected happens during configuration merging but does not check which option is missing. ------------------------------------------------------------- sssd.conf without any typos in option name and section name this contact form Honour has been the reward for what he gave (clavin coolidge) 0 Kudos Hoang Chi Cong_1 Honored Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print DP 8 CM Linux To add clients linux, CM demands public-private key pair. did a backup and it worked...moved tape back to slot 3..

Another logical library is being used Veeam and everything seems to be working fine as it can copy to more than one tape per session. The attached doc says 4.1, and 4.1 unpatched at that.Are you running 4.1 or 5.5? Solved! have a peek here Comment 8 Jakub Hrozek 2016-06-27 16:32:16 EDT master: 8b2a31634764168183506925a4b9f461afdba6f3 c42ca36247022490ad65a33c453cb5e43900dbe9 Comment 13 Michal Zidek 2016-07-19 05:37:14 EDT Doc text looks good to me.

After session ends, there is no number of files and folders displayed. That's obvious from the backup machine itself as well as on the client I am doing te restore on. 45 minutes at 850Mbps is about 230GB in total. But then how did omnidownload report 4.1?We are running:SLX2:>omnidb -versionHP OpenView OmniBack II A.04.10: OMNIDB, internal build 176, built on Tue Nov 13 04:14:43 2001SLX2:>uname -aHP-UX slx2 B.11.11 U 9000/800 761977641

It works fine, so far I was able to restore every single machine with it.

There will be no more patches for 4.1. Contact us about this article Hi,   One of the remote server which needs to be added in to the cell manager.    We have 6.21 cell manager in one of the problem described above has occurred once in the last week,but we have had a problem where the backups didn't run at all and the followingis a typical error log when Omniback and NT problems?

Virtual Machine 'VM': Could not backup disk scsi0:0 ...   When no backups are running have a look on the VEAgent backup host. Check for typos. Bug988207 - sssd does not detail which line in configuration is invalid Summary: sssd does not detail which line in configuration is invalid Status: CLOSED ERRATA Aliases: None Product: Red Hat Check This Out Note that this directory has special permissions and can only be removed if permissions are changed first.

We have an HP 1/8 G2 SAS Autoloader with 8 tapes.