Thanks
From tests this morning I have seemed to get it all working , one last
question , if I issue
tpconfig -d
on all media servers and the volume database entry all point to one
server does this mean that there is only one volBD I need to worry about
or does this in fact point to the device database globDB?
Dave
-----Original Message-----
From: Stefanos Monovasios [mailto:smpt at peppas.gr]
Sent: 04 August 2006 11:35
To: Clooney, David; veritas-bu at mailman.eng.auburn.edu
Cc: smpt at peppas.gr
Subject: RE: [Veritas-bu] Master Server Hostname Change
If you have the services down during the copy and move the voldb, pooldb
from the master and mediadb from all media servers (and the master)
there is no problem with the tapes.
It will be good to logically move the tapes out of the robot before move
the voldb
smpt
-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Clooney,
David
Sent: Friday, August 04, 2006 12:42 PM
To: smpt; veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Master Server Hostname Change
That's great info , much appreciated
Quick Q ,how did you over come the tapes being overwritten in the new
system, or as you have moved all db's the new system recognises the
media as if it where its own?
Cheers
Dave
-----Original Message-----
From: smpt [mailto:smpt at peppas.gr]
Sent: 04 August 2006 10:36
To: Clooney, David; veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Master Server Hostname Change
Hi, I've done this many times.
You are correct.
You must run the bpimage command before you move the database.
Then you can move the image dir to the new server.
Also you must move the files: mediadb, voldb, pooldb, ruledb. The
vmglob is not needed. Check the vm.conf and bp.conf.
Move the class, client and config dirs (if byou need the policies, and
the configuration setings of the Previous server).
If you use DSSU move the shed dir
If you use vault move the vault dir
All copies must be done with the services down.
As I told you I've done many times, most of them with success. But with
some installations Although the backup and restore is working,u I
can't restore from old server's backups with error 202. I don't know why
and I can't call Veritas as this is unsupported. It is strange.
smpt
> -------Original Message-------
> From: Clooney, David <david.clooney at bankofamerica.com>
> Subject: Re: [Veritas-bu] Master Server Hostname Change
> Sent: 04 Aug '06 10:29
>
> All
>
> you wont believe it but I'm still investigating the master server
> hostname change and need some advice as to where else something could
> go wrong.Now i know this is possible and everyone mentions that
> Symantec PS should be pulled in to complete otherwise unsupported and
> this I realise. What I'm trying to do is validate the expense in
> order to get the PS work approved so here goes, the new master is
> identical to the current with nothing active at all. I know this is
> not as simple as it seems however am trying to get an outline.
>
> The problem we have is if we go the importing route this would take
> us 9 months.
>
> Scenario is the domain the master was bulit in is going to be
> discontinued and we can't stop it ( and host file options are ruled
> out too) , additionally the master was bulit with a fqdm which I tend
> to disagree with.
>
> the db's to worry about are
>
> Image db: As this is a flat file directory structure this can be
copied
> and then manipulated for the images to reflect the new server
>
> bpimage: -newserver <name> [-oldserver <name>] [-id <id>]
>
> PoolDB: can be copied as flat file
>
> PolicyDB: once again flat file structure, straight copy
>
> MediaDB: the media db can too be manipulated to reflect the new
server
> and this I have tested, so now no "FORCE_RESTORE_MEDIA_SERVER" is
> required on the old server.
>
> bpimage: -newserver <name> [-oldserver <name>] [-id <id>] Question
> , once this is done and the mediaDB is copied over , would Netbackup
> then know of the images resident on media ??
>
>
> VolDB: This is the problem child in my opinion, one because
its
> distibuted and two because there is no real way of manipulating it ,
> suggestions would be most welcome
>
> Sure it can be copied over, but no doubt would need some changing.
> Once volume is added , assignbyid with allocation time which can be
> retrieved from bpmedialist -L
>
> Globdb: this can be recreated quite easily
>
>
> If anyone knows of anything I'm missing please let me know.
>
> Much appreciated
>
> David Clooney
>
>
> --------------------
>
>
> Notice to recipient:
> The information in this internet e-mail and any attachments is
> confidential and may be privileged. It is intended solely for the
> addressee. If you are not the intended addressee please notify the
> sender immediately by telephone. If you are not the intended
> recipient, any disclosure, copying, distribution or any action taken
> or omitted to be taken in reliance on it, is prohibited and may be
unlawful.
>
> When addressed to external clients any opinions or advice contained
> in this internet e-mail are subject to the terms and conditions
> expressed in any applicable governing terms of business or client
> engagement letter issued by the pertinent Bank of America group
entity.
>
> If this email originates from the U.K. please note that Bank of
> America, N.A., London Branch and Banc of America Securities Limited
> are authorised and regulated by the Financial Services Authority.
>
>
> --------------------
>
> --------------------
> _______________________________________________
> Veritas-bu maillist - [LINK:
> compose.php?to=Veritas-bu at mailman.eng.auburn.edu]
> Veritas-bu at mailman.eng.auburn.edu
> [LINK: http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu]
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Notice to recipient:
The information in this internet e-mail and any attachments is
confidential and may be privileged. It is intended solely for the
addressee. If you are not the intended addressee please notify the
sender immediately by telephone. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted to
be taken in reliance on it, is prohibited and may be unlawful.
When addressed to external clients any opinions or advice contained in
this internet e-mail are subject to the terms and conditions expressed
in any applicable governing terms of business or client engagement
letter issued by the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America,
N.A., London Branch and Banc of America Securities Limited are
authorised and regulated by the Financial Services Authority.
_______________________________________________
Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Notice to recipient:
The information in this internet e-mail and any attachments is confidential and
may be privileged. It is intended solely for the addressee. If you are not the
intended addressee please notify the sender immediately by telephone. If you
are not the intended recipient, any disclosure, copying, distribution or any
action taken or omitted to be taken in reliance on it, is prohibited and may be
unlawful.
When addressed to external clients any opinions or advice contained in this
internet e-mail are subject to the terms and conditions expressed in any
applicable governing terms of business or client engagement letter issued by
the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America, N.A.,
London Branch and Banc of America Securities Limited are authorised and
regulated by the Financial Services Authority.
|
