Re: [Veritas-bu] Can Netbackup work on a DHCP network
It's not as bad as it sounds. You just have to make sure that the DHCP server modifies DNS records (forward and reverse) for each client as it hands out DHCP leases. You should have your servers acquire static leases (where the given MAC always gets the same IP addr) so they are always in the same place. But the clients can move around as long as the DNS server gets updated so you can do forward AND reverse lookups. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Monday, June 12, 2006 3:05 PM To: Carl Mathews Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Can Netbackup work on a DHCP network On Mon, Jun 12, 2006 at 02:54:46PM -0500, Carl Mathews wrote: Our networks are changing from static IP to DHCP. DHCP prevents netbackup from using reverse lookup. It also prevents you from doing a forward lookup! Will Netbackup work on a DHCP network? If you can't find the server, how can you possibly back it up? The *master* server initiates the backup, and if the target server is not static, there's not a thing you can do for it. What you can you do is to have your DHCP server always return the same IP address for the given MAC address. Then put that entry in your DNS. That defeats the purpose of DHCP but then DHCP for servers doesn't make much sense anyway. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Confidentiality Notice: The information contained in this e-mail from Rob Haig and any attachments is legally privileged or otherwise confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. Thank you in advance for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] FROZEN vs SUSPENDED
Basically that's the difference. When a tape is frozen, after it expires, it stays frozen and unavailable. (the data on the tape will expire, don't freeze tapes to keep data around) A suspended tape becomes available for use again after the data expires. Suspend tapes that you don't want to write further data to for some administrative reason. When they expire, you can re-use them. Freeze tapes that you suspect have problems and you never want to write data to again. When they expire, you can run some tests on them to see if they are really bad. -Original Message- So it looks like the main difference is that a frozen tape never expires. Confidentiality Notice: The information contained in this e-mail from Rob Haig and any attachments is legally privileged or otherwise confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. Thank you in advance for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Major incompatibility!
I don't know about the windows version. I'm using the 6.0 linux admin console to manage my 5.1 server and it works just fine Confidentiality Notice: The information contained in this e-mail from Rob Haig and any attachments is legally privileged or otherwise confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. Thank you in advance for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] could not deassign media due to Media Manager error
You could always do a vmquery -deassignbyid But afteryou do this make sure you delete the tape and then let NBU recreate it with an inventory robot. If you don't delete the tape in NBU 5.x you can end up with 2 media servers writing to the same tape causing data loss. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 30, 2006 11:06 AM To: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] could not deassign media due to Media Manager error Is this tape assigned to a media server that no longer exists? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of WEAVER, Simon Sent: Thursday, March 30, 2006 12:14 AM Morning Have an old LTO1 tape that has not been written to in over 12 months. When I run the media list it shows this tape 0807L1 expired 29th March 06. Today is the 30th. The status of the tape shows expired MPX So when trying to bpexpdate -m 0807L1 -d 0 it tell me it could not deassign media due to media manager error. Any tips on how to remove this from the report? Netbackup believes it is assigned to a volume and I can see it. The tape is not stored in the library and there will be no need to re-use this tape in the future Thanks Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ 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 Confidentiality Notice: The information contained in this e-mail from Rob Haig and any attachments is legally privileged or otherwise confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. Thank you in advance for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] command-line way to get vol_id from filespec and date range?
Im trying to determine through a command-line interface what piece of media a file is on given a hostname, file-spec, and date range. I suspect Ill have to start with a backup_id and get the media_id from that with bpimmedia or something like that. Im not shy of scripting, and given a backup_id (hostname_timestamp) I can derive the piece(s) of media it is on. I just dont know how to go from the date-range and filespec to the backup_id. thx Confidentiality Notice: This electronic communication contained in this e-mail from Rob Haig (including any attachments) may contain privileged and/or confidential information. This communication is intended only for the use of indicated e-mail addressees. Please be advised that any disclosure, dissemination, distribution, copying, or other use of this communication or any attached document other than for the purpose intended by the sender is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail and promptly destroy all electronic and printed copies of this communication and any attached document. Thank you in advance for your cooperation.
