Re: [Veritas-bu] cannot add new tapes into volume in media server
You should NEVER have more than one volDB in ANY version of NBU - that's asking for problems. Up to version 5.1, each media server has its own device database (robotic_def and ltidevs) as well as own mediaDB but only one volDB for entire environment (usually on Master). Although it is possible to have more than one volDB, Symantec recommends one only. See the topic called 'Volume Database Host' in the Media Manager Admin Guide: There should be only one volume database host per global device database host (see Global Device Database Host on page 8), and both of these key databases should be located on the same server. This server is known as the Media and Device Management Domain (MDM Domain) server. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of footsoldier Sent: 09 April 2009 02:05 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] cannot add new tapes into volume in media server hi Patrick, no problem, thks for helping, if i got chance i will ask that consultant why my volume database got corrupted, but my domain design isn't orthodox enough to begin with, i have 1 master and 1 media in the same domain each with it's own volume database, the media one got corrupted while the master has no problems. They don't allow that in versions 6 and above.. +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] cannot add new tapes into volume in media server
I'm glad you got your problem fixed and thank you for forwarding the solution. I shall add that to my growing list of solutions to problems. Did they by any chance tell you how the volDB got corrupt in the first place so you can prevent it from happening again? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of footsoldier Sent: 08 April 2009 02:43 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] cannot add new tapes into volume in media server hi Patrick, Symantec consultant gives me the following solution, i tried it and it works: 1. Check for corruption : # strings volDB | head -1 This will return the volDB version, which will be either volDB004 or volDB005. Find the size of volDB: # ls -l /usr/openv/volmgr/database/volDB Subtract eight bytes from the size (the volDB header is eight bytes). Then divide by 596 for volDB version volDB004, or divide by 660 for volDB version volDB005. If the result is a whole number, then the database is intact. If the result is not a whole number, then it is corrupt. 2. Use the procedure below to recover a corrupt volDB: 1. Shut down the vmd process if it is running: /usr/openv/volmgr/bin/vmctrldbm -t 2. Move volDB to volDB.old: mv /usr/openv/volmgr/database/volDB /usr/openv/volmgr/database/volDB.old 3. Start vmd /usr/openv/volmgr/bin/vmd This creates a new empty volume database volDB (size = 8 bytes) 4. Run the command /usr/openv/volmgr/bin/vmdb_compact This reads records from volDB.old, and inserts them into a new volDB. 5. Use the UNIX strings command on both the volDB and volDB.old, redirecting the output to files (instead of to the screen). Compare the two output files to determine if any media has not been transferred to the new volume database. If there are pieces of media that have not gone across to the new volDB, then they will need to be re-added using Media Manager. _ +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] cannot add new tapes into volume in media server
hi Patrick, no problem, thks for helping, if i got chance i will ask that consultant why my volume database got corrupted, but my domain design isn't orthodox enough to begin with, i have 1 master and 1 media in the same domain each with it's own volume database, the media one got corrupted while the master has no problems. They don't allow that in versions 6 and above.. +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] cannot add new tapes into volume in media server
hi Patrick, Symantec consultant gives me the following solution, i tried it and it works: 1. Check for corruption : # strings volDB | head -1 This will return the volDB version, which will be either volDB004 or volDB005. Find the size of volDB: # ls -l /usr/openv/volmgr/database/volDB Subtract eight bytes from the size (the volDB header is eight bytes). Then divide by 596 for volDB version volDB004, or divide by 660 for volDB version volDB005. If the result is a whole number, then the database is intact. If the result is not a whole number, then it is corrupt. 2. Use the procedure below to recover a corrupt volDB: 1. Shut down the vmd process if it is running: /usr/openv/volmgr/bin/vmctrldbm -t 2. Move volDB to volDB.old: mv /usr/openv/volmgr/database/volDB /usr/openv/volmgr/database/volDB.old 3. Start vmd /usr/openv/volmgr/bin/vmd This creates a new empty volume database volDB (size = 8 bytes) 4. Run the command /usr/openv/volmgr/bin/vmdb_compact This reads records from volDB.old, and inserts them into a new volDB. 5. Use the UNIX strings command on both the volDB and volDB.old, redirecting the output to files (instead of to the screen). Compare the two output files to determine if any media has not been transferred to the new volume database. If there are pieces of media that have not gone across to the new volDB, then they will need to be re-added using Media Manager. _ +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] cannot add new tapes into volume in media server
Why do you not use the GUI? When you say delete 5 or more... what do you mean by delete? Are these tapes empty? If so, why do you need to add more, if not how can you delete them? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of footsoldier Sent: 02 April 2009 01:18 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] cannot add new tapes into volume in media server hi Patrick, yes i am using a 60-slot HP MSL library..i am just trying to add 4 or 5 tapes with new volume labels...running Vmupdate -rt -tld -rn 1 command from the command line..i will get this error : Update failed: could not add new media ID '9UD034' into slot 50 Insert media failed: network protocol error (39) One last time baby... Unable to obtain database handle: Could not connect to vmd on host stmes11bkup (70) ...the vmd daemon will then hang, and i have to restart my Netbackup services..unless i delete 5 or more existing volumes from my database, this operation will always hit this error... +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] cannot add new tapes into volume in media server
i am using netbackup 5.1 domain, i cant seem to add anymore new tapes into the volume database using the vmupdate command, unless i delete old volumes away...if i dont, the vmupdate will fail and hang the vmd daemon...which i then have to restart netbackup... can anyone advise, is there a limitation to the number of tapes i can add to my database ?? +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] cannot add new tapes into volume in media server
How many tapes are we talking about? Do you have a library? Are you using the inventory library GUI to add the volumes? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of footsoldier Sent: 01 April 2009 10:02 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] cannot add new tapes into volume in media server i am using netbackup 5.1 domain, i cant seem to add anymore new tapes into the volume database using the vmupdate command, unless i delete old volumes away...if i dont, the vmupdate will fail and hang the vmd daemon...which i then have to restart netbackup... can anyone advise, is there a limitation to the number of tapes i can add to my database ?? +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] cannot add new tapes into volume in media server
hi Patrick, yes i am using a 60-slot HP MSL library..i am just trying to add 4 or 5 tapes with new volume labels...running Vmupdate -rt -tld -rn 1 command from the command line..i will get this error : Update failed: could not add new media ID '9UD034' into slot 50 Insert media failed: network protocol error (39) One last time baby... Unable to obtain database handle: Could not connect to vmd on host stmes11bkup (70) ...the vmd daemon will then hang, and i have to restart my Netbackup services..unless i delete 5 or more existing volumes from my database, this operation will always hit this error... +-- |This was sent by garrick...@yahoo.com.sg via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
