TimTh
2 Iron

Moving clients from one networker server to another

Jump to solution

Hi all,

Currently, we have 1 Networker server, with 4 storage nodes.

We have about 500 clients, and that's about 6000 save sets and 10TB of data we take into backup each day.

We now want to introduce a second Networker server, to spread the load a little bit over these 2 networker servers.

What is the best way to move clients from 1 networker server to another?

I guess the best way to create clients on the second networker server is, by making sure that the client-id is the same as on the original server.

But how do you get the old backups and indexes from the 1st networker server to the second networker server?

Kind regards

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
coganb
3 Cadmium

Re: Moving clients from one networker server to another

Jump to solution

Hi,

This article explains what you need to do:

How to move a NetWorker client to a different server

http://solutions.emc.com/EMCSolutionView.asp?id=esg63354&usertype=C

Also, you might want to check out the Performance Optimisation Guide which details some sizing parameters you need to keep in mind and some tests you can run to analyse what is affecting your server performance.

http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-009-448.pdf?

-Bobby

0 Kudos
15 Replies
rene_roest
1 Copper

Re: Moving clients from one networker server to another

Jump to solution

i prefer to add storage nodes to scale, since it is not quite so easy to move backups between 2 backup servers (and thus different datazones). Why is your backup server overloaded? try to shift load from that backup server to a (new) storage node.

You can also opt not to do any backups to the backup server(expect it's own ofcourse); this could drastically reduce the load on your backup server by relegating it role just to schedule & track metadata of all backups (so not to fuzz around with terabytes of actual data on the backup server.)

René

0 Kudos
TimTh
2 Iron

Re: Moving clients from one networker server to another

Jump to solution

Hello Rene,

We already have 4 storage nodes, and we are not taking backups to the backup server itself, only to the storage nodes.

But with more and more clients, and thus more and more savesets, the media database, jobsdb, ... are all growing, and it seems this is starting to give problems.

We already lowered the retention of the jobsdbd to 3 days, and a maximum size of 60MB, but we see that it has a size of 200-300MB just to keep info for 3 days.

Also several mminfo's are taking an very long time to finish, and while running such mminfo querry's, the NMC has trouble loading it's info.

0 Kudos
coganb
3 Cadmium

Re: Moving clients from one networker server to another

Jump to solution

Hi,

This article explains what you need to do:

How to move a NetWorker client to a different server

http://solutions.emc.com/EMCSolutionView.asp?id=esg63354&usertype=C

Also, you might want to check out the Performance Optimisation Guide which details some sizing parameters you need to keep in mind and some tests you can run to analyse what is affecting your server performance.

http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-009-448.pdf?

-Bobby

0 Kudos
TimTh
2 Iron

Re: Moving clients from one networker server to another

Jump to solution

Hello Bobby,

That was exactly what I was looking for.

Too bad there is not an easy way to move the current backups to the new server. We are working with adv_file devices on datadomain.

So I guess we'll have to move all the backups of those clients to a specific device, and mount that device on the new server, and do a complete scanner of that device.

We also got that tuning guide from our support. And applied all the settings and recomandations.

Kind regards

0 Kudos

Re: Moving clients from one networker server to another

Jump to solution

Could you please let me know what process requires to be done if I add new storage nodes? How do I make sure those are being used? How is the migration done?

0 Kudos
bingo.1
4 Beryllium

Re: Moving clients from one networker server to another

Jump to solution

If this is a new client/storage node ...

  - Install the NW client and storage node software

  - Prepare its /nsr/res/servers file appropriately

      If it has changed, restart the NW client service/daemon

  - Define the client in your data zone

  - Define at least one remote device at that client

  - Add the appropriate license(s)

If this is an existing client ...

  - Install/promote the NW client by installing the storage node software

  - Verify the /nsr/res/servers file

      If it has changed, restart the NW client service/daemon

  - Define at least one remote device at that client

  - Add the appropriate license(s)

Finally, do not forget

  - to define additional pools (if required)

  - label new media to that pool

  - Adjust the client resources (storage node list) for the clients which shall use the storage node appropriately

Re: Moving clients from one networker server to another

Jump to solution

Thank you for the answer.can I move a device currently being used by another storage node to this storage node without losing data on the device? I know that relabeling will cause data loss

0 Kudos
bingo.1
4 Beryllium

Re: Moving clients from one networker server to another

Jump to solution

Of course you can :

  - do not forget that the media db does 'only' store save set and media information, but no device information

  - tapes will not be affected at all. That's why you can use them in any compatible device

  - disk drives will only be affected if you label/recycle the media. This is what you must not do.

0 Kudos

Re: Moving clients from one networker server to another

Jump to solution

So data domains can be moved

0 Kudos