Re: [Veritas-bu] Duplication job
On Wed, Jan 07, 2009 at 07:16:26PM +0200, Asiye Yigit wrote: > We have duplicated some tapes using catalog backup. After duplication, > when we search the images from the original copy, > > It says skipping media id xx it has already two copies. What do you mean by "search the images"? What commands are you running that generate that output? -- Darren ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Duplication job
Hello, We have duplicated some tapes using catalog backup. After duplication, when we search the images from the original copy, It says skipping media id xx it has already two copies. What is the reason? Duplication process can expire the images on the primary copy? Regards, ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Duplication job killing NB Catalog job
I've come across step2. Weird bug!! Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eagle, Kent Sent: Tuesday, January 10, 2006 4:16 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Duplication job killing NB Catalog job Greetings, Windoze 2K3 Master & 2 Media servers, NetBackup 5.1MP3 SSO, ADIC I2000 fiber LTO2. I have 2 interrelated questions: 1. We have 2 clients being backed up to the same DSU. The clients reside in independent policies, but are often running concurrently, for at least part of their active time. We have a duplication job we've set up as a vault profile to duplicate the images to tapes. The profile is currently being launched manually by an operator when they see both jobs have completed. I would like to automate this process, but can't find any verbose notes on bpend_notify.bat, which I think will do what I want? (P.S. - Windoze isn't my choice: I'm fairly familiar with batch files & not afraid of the CLI ;-) 2. Other backups are running and completing while the process above is transpiring. We've noticed that if all other jobs but the duplication process have completed, NetBackup will attempt to run a catalog backup. This results in a failure of the catalog backup with a "124" error which says the one of directories was not available for backup. My guess is it's one of the Master Servers catalog paths as it's still running the duplication process. Manually running the catalog after this scenario is always successful. If the duplication process and all other jobs have completed the catalog backup is always successful. Is there a way to have NetBackup treat the duplication step like a regular backup job so it will not attempt a catalog backup during the dup? I can't figure out why NB thinks the schema is quiesed when this process is still running? We could try to script it to run after the duplication process, but the duplication process wouldn't necessarily always be the last job to run (due to growth, we might have other backups still running after duplication has completed). Thank you, Kent C. Eagle Wilmington Trust Company Systems Engineer, MCP, MCSE Tech Services / SMSS [EMAIL PROTECTED] Visit our website at www.wilmingtontrust.com Investment products are not insured by the FDIC or any other governmental agency, are not deposits of or other obligations of or guaranteed by Wilmington Trust or any other bank or entity, and are subject to risks, including a possible loss of the principal amount invested. This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ 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] Duplication job killing NB Catalog job
Take a look at session_notify, this run when all the scheduled jobs are
complete. I don't know if it runs before, after or concurrently with the
catalog backup. You could always set catalog backup to manual and the run
bpbackupdb from the session_notify script.
Patrick Whelan
NetBackup Specialist
Architect & Engineering
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eagle, Kent
Sent: 10 January 2006 14:16
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Duplication job killing NB Catalog job
Greetings,
Windoze 2K3 Master & 2 Media servers, NetBackup 5.1MP3 SSO, ADIC I2000
fiber LTO2.
I have 2 interrelated questions:
1. We have 2 clients being backed up to the same DSU. The clients reside
in independent policies, but are often running concurrently, for at
least part of their active time. We have a duplication job we've set up
as a vault profile to duplicate the images to tapes. The profile is
currently being launched manually by an operator when they see both jobs
have completed. I would like to automate this process, but can't find
any verbose notes on bpend_notify.bat, which I think will do what I
want? (P.S. - Windoze isn't my choice: I'm fairly familiar with batch
files & not afraid of the CLI ;-)
2. Other backups are running and completing while the process above is
transpiring. We've noticed that if all other jobs but the duplication
process have completed, NetBackup will attempt to run a catalog backup.
This results in a failure of the catalog backup with a "124" error which
says the one of directories was not available for backup. My guess is
it's one of the Master Servers catalog paths as it's still running the
duplication process. Manually running the catalog after this scenario is
always successful. If the duplication process and all other jobs have
completed the catalog backup is always successful.
Is there a way to have NetBackup treat the duplication step like a
regular backup job so it will not attempt a catalog backup during the
dup? I can't figure out why NB thinks the schema is quiesed when this
process is still running? We could try to script it to run after the
duplication process, but the duplication process wouldn't necessarily
always be the last job to run (due to growth, we might have other
backups still running after duplication has completed).
Thank you,
Kent C. Eagle
Wilmington Trust Company
Systems Engineer, MCP, MCSE
Tech Services / SMSS
[EMAIL PROTECTED]
Visit our website at www.wilmingtontrust.com
Investment products are not insured by the FDIC or any other governmental
agency, are not deposits of or other obligations of or guaranteed by Wilmington
Trust or any other bank or entity, and are subject to risks, including a
possible loss of the principal amount invested. This e-mail and any files
transmitted with it may contain confidential and/or proprietary information.
It is intended solely for the use of the individual or entity who is the
intended recipient. Unauthorized use of this information is prohibited. If
you have received this in error, please contact the sender by replying to this
message and delete this material from any system it may be on.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-buì
*
The message is intended for the named addressee only and may not be disclosed
to or used by anyone else, nor may it be copied in any way.
The contents of this message and its attachments are confidential and may also
be subject to legal privilege. If you are not the named addressee and/or have
received this message in error, please advise us by e-mailing [EMAIL PROTECTED]
and delete the message and any attachments without retaining any copies.
Internet communications are not secure and COLT does not accept responsibility
for this message, its contents nor responsibility for any viruses.
No contracts can be created or varied on behalf of COLT Telecommunications, its
subsidiaries or affiliates ("COLT") and any other party by email Communications
unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate
potential viruses and unsolicited promotional emails. For more information
refer to www.colt.net or contact us on +44(0)20 7390 3900.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Duplication job killing NB Catalog job
Greetings, Windoze 2K3 Master & 2 Media servers, NetBackup 5.1MP3 SSO, ADIC I2000 fiber LTO2. I have 2 interrelated questions: 1. We have 2 clients being backed up to the same DSU. The clients reside in independent policies, but are often running concurrently, for at least part of their active time. We have a duplication job we've set up as a vault profile to duplicate the images to tapes. The profile is currently being launched manually by an operator when they see both jobs have completed. I would like to automate this process, but can't find any verbose notes on bpend_notify.bat, which I think will do what I want? (P.S. - Windoze isn't my choice: I'm fairly familiar with batch files & not afraid of the CLI ;-) 2. Other backups are running and completing while the process above is transpiring. We've noticed that if all other jobs but the duplication process have completed, NetBackup will attempt to run a catalog backup. This results in a failure of the catalog backup with a "124" error which says the one of directories was not available for backup. My guess is it's one of the Master Servers catalog paths as it's still running the duplication process. Manually running the catalog after this scenario is always successful. If the duplication process and all other jobs have completed the catalog backup is always successful. Is there a way to have NetBackup treat the duplication step like a regular backup job so it will not attempt a catalog backup during the dup? I can't figure out why NB thinks the schema is quiesed when this process is still running? We could try to script it to run after the duplication process, but the duplication process wouldn't necessarily always be the last job to run (due to growth, we might have other backups still running after duplication has completed). Thank you, Kent C. Eagle Wilmington Trust Company Systems Engineer, MCP, MCSE Tech Services / SMSS [EMAIL PROTECTED] Visit our website at www.wilmingtontrust.com Investment products are not insured by the FDIC or any other governmental agency, are not deposits of or other obligations of or guaranteed by Wilmington Trust or any other bank or entity, and are subject to risks, including a possible loss of the principal amount invested. This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
