Im a bit late in on this conversation.
Jihm
I have done move of media and catelog from one master in to a existing
different master. I moved all tapes from a solaris master into a windows
master.
I did get help from veritas support but at one stage but when some things
didnt work out another support staff said he should not have done this
under support
Perhaps you are best to pay for consulting services.
Below is the mail I got from veritas support on the issue. Only the name
of the veritas support staff has been removed.
Now I can hardly remember what I did:
I did manually copy over indexes for clients.
I did manually edit the pool databases file. I had no pools ID clashes and
I think that turned out to be quite critical.
I did run commands like bpmedia -m ADI694 -movedb -oldserver
OLDSERVERNAME -newserver NEWSERVERNAME. I had to do some set up for this
first.
I used commands like: vmadd -m HFG933 -mt dlt -p 17 where I got info
for the command from the output of vmquery
one gotya I had was needing to put the old server in the restore failover
list of the new server.
I definately had a few issues and was wishing that I had got veritas to do
it under contract.
Subject: VERITAS Support: Case ID 230-061-782
To: [EMAIL PROTECTED]
Hi Bevan,
=20
now fully understanding the challenges ahead for you :), below is some
helpful information of the various Netbackup databases you will be
attempting to merge onto the final Netbackup master server, all at the
same level of NBU 5.1.
=20
Have a read of the following and I'll await your feedback. I have
included various extracts from different internal documents as there is
no Public Technote to do what you are doing - and the official take on
it is it is a Consulting issue rather than a Support responsibility,
but I am happy to assist you where I can :)
=20
- Chris.
--
Netbackup Databases invovlved:
--
There are six main databases that need to be considered when
reconfiguring a NetBackup environment:* The image database - this is a
flat file structure held on the NetBackup master server. In general
this database can be moved from one location to another with a simple
copy operation. However it is important to remember that this database
contains links to the media database, which need to be kept consistent.
* The media database - the only distributed database in most NetBackup
environments. While it is possible to manipulate this database by
various editing techniques there are no NetBackup CLI options to modify
it. It is therefore recommended that you endeavor to keep the media
database consistent and bring the image and volume database in line with
it.
* The policy database - another flat file structure that can simply be
copied between master servers (provided, of course, that the same class
name is not in use on both servers). Be sure to update the storage unit
information associated with classes when moving them between servers. *=20
=20
The volume database - volume database information can be extracted and
updated by using the vmquery command. When merging two environments the
best approach is to use vmquery to extract information from one volume
database and then a combination of vmadd and vmquery -assignbyid to
create corresponding information in the other volume database. Note
that it is not possible to carry over tape usage information from one
database to another.
* The pool database - this database usually consists of a relatively
small number of entries. The important thing to bear in mind is that it
is the number associated with each pool record, not the name, that is
used to link to the other databases. This means that, unless the pool
records have been added in exactly the same order in two environments,
some tapes are likely to change pools following a merger.
* The global device database - this database contains information about
all devices on all media servers in a domain. Storage units usually
change as a result of mergers and splits so it is simpler to define the
storage units you require rather than attempting to export and import
information. You may also choose to merge the jobs and error databases
if required but this is not essential and is not covered in this
document.
=20
Merging Master Servers:
In the interests of simplifying the management of a NetBackup
installation customers often seek to combine two or more domains under a
single, more powerful master server. In most cases this presents few
problems but it is important to ensure that there is no risk of conflict
before starting such a merge When merging master servers you are
concerned with the following aspects of the NetBackup database:=20
* Image database
* Policy database
* Client database
* Global device database
Note: the merging of the volume or pool databases have not yet been
discussed
