RDZ client can not index, backup hangs

The only owner of the index and bootstrap save sets is the NW server's client.

By default, index and bootstrap backups are configured to be backed up at NW server. The index backups can be directed to a RSN but the bootstrap must go to a local backup device at the NW server.

You usually control this by defining an appropriate pool which uses

    save set: index

                  bootstrap

as selection criteria. In this case you never need to reconfigure your other resources.

Try running only index and bootstrap backup for the group in which this client belongs to. See if the index fails again, also look for any error message.

Use this command,

savegrp -O -vvv -c -G

Regards,

Prajith

Ensure that you have a local device available for the when the index backups is asking for it. Incase there was not local device configured the backup would fail, bu the fact that the backups is not failing means either the locally attached device is either busy or the client parallelism set for the client instance of the server is low.

Can you provide the output of the following command - replace backup_server with the host name of your backup[ server.

nsradmin

>. type: nsr client; name: backup_server

> print

I've been following this thread and I miss following information:

- you keep saying RDZ client - what is RDZ?

- when you say index and boostrap are not saved, do you see any pending message?

Typically, people make mistake where they direct client X to pool Y and volumes/devices for that pool do not exist on server where index and bootstrap is saved.  If this is your case, then you either make sure pool on server exists or you say index and bootstrap separately via index backups as mentioned earlier.  However, that is only if this is your case in the first place. Without logs it is all guess work.

Hello,y what do you mean by "local device"?

Our problem is indexing for an RDZ client. That is why it can not finish withe the task.

here is the output:

nsradmin> print

type: NSR client;

name: networker.servers.intra;

server: networker.servers.intra;

client id: \

9d458bfe-00000004-51223834-51223833-0001faa0-95cbd202;

scheduled backup: Enabled;

comment: NetWorker server;

             Save operations: ;

            archive services: Disabled;

schedule: FS-w_full;

browse policy: Month;

retention policy: Month;

statistics: elapsed = 2336699, index size (KB) = 410202,

                              amount used (KB) = 410202, entries = 2646380;

directive: ;

group: NetWorker, UNIXFS;

save set: /smit.log, /smit.script, /unix, /home, /opt,

                              /nfs/hmcbackup, /rcdir.tar, /var, /bin,

/smit.transaction, /install, /lib, /image.data,

                              /root, /rcfiles.tar, /audit, /admin,

                              /nfso_-L.txt, /tftpboot, /sbin,

/var/adm/ras/livedump, /bosinst.data, /lpp,

                              /etc, /.rhosts, /Data_Protection_Advisor_Uninstall_05_21_2013_15_57_26.log,

                              /esa, /u, /pconsole, /nsr, /usr;

  Backup renamed directories: Enabled;

Checkpoint enabled: Disabled;

      Checkpoint granularity: Directory;

priority: 500;

   File inactivity threshold: 0;

File inactivity alert threshold: 0;

remote access: ;

remote user: ;

password: ;

backup command: ;

     application information: ;

ndmp: No;

             NDMP array name: ;

De-duplication backup: No;

De-duplication node: ;

Pool: UXFSD;

          Data Domain backup: No;

Client direct: Enabled;

         Probe resource name: ;

virtual client: No;

               physical host: ;

           Proxy backup type: ;

           Proxy backup host: ;

executable path: ;

    server network interface: ;

aliases: networker, networker.servers.intra, networker-b,

networker-b.servers-bck.intra, networker-m,

networker-m.servers-mgmt.intra;

index path: ;

          owner notification: ;

parallelism: 12;

physical client parallelism: Disabled;

storage nodes: nsrserverhost;

       recover storage nodes: ;

hard links: Disabled;

             short filenames: Disabled;

BMR: Disabled;

BMR options: ;

                 backup type: ;

client OS type: AixOS;

CPUs: 8;

NetWorker version: 8.0.1.1.Build.132;

enabler in use: Yes;

       licensed applications: ;

licensed PSPs: ;

                        type: NSR client;

name: networker.servers.intra;

server: networker.servers.intra;

client id: \

9d458bfe-00000004-51223834-51223833-0001faa0-95cbd202;

scheduled backup: Enabled;

comment: NetWorker server;

             Save operations: ;

            archive services: Disabled;

schedule: AlwaysFull;

browse policy: Month;

retention policy: Month;

statistics: elapsed = 2336699, index size (KB) = 410202,

                              amount used (KB) = 410202, entries = 2646380;

directive: ;

group: UNIXFS_FULL;

save set: /nfs/iwiki_bck;

  Backup renamed directories: Enabled;

Checkpoint enabled: Disabled;

      Checkpoint granularity: File;

priority: 500;

   File inactivity threshold: 0;

File inactivity alert threshold: 0;

remote access: ;

remote user: ;

password: ;

backup command: ;

     application information: ;

ndmp: No;

             NDMP array name: ;

De-duplication backup: No;

         De-duplication node: ;

Pool: UXFSD;

          Data Domain backup: No;

Client direct: Enabled;

         Probe resource name: ;

virtual client: No;

physical host: ;

           Proxy backup type: ;

           Proxy backup host: ;

executable path: ;

    server network interface: ;

aliases: networker, networker.servers.intra, networker-b,

index path: ;

          owner notification: ;

parallelism: 12;

physical client parallelism: Disabled;

storage nodes: nsrserverhost;

       recover storage nodes: ;

hard links: Disabled;

             short filenames: Disabled;

BMR: Disabled;

BMR options: ;

backup type: ;

client OS type: AixOS;

CPUs: 8;

NetWorker version: 8.0.1.1.Build.132;

enabler in use: Yes;

       licensed applications: ;

licensed PSPs: ;

type: NSR client;

name: networker.servers.intra;

server: networker.servers.intra;

client id: \

9d458bfe-00000004-51223834-51223833-0001faa0-95cbd202;

scheduled backup: Enabled;

comment: NMC DB;

             Save operations: ;

            archive services: Disabled;

schedule: Default;

browse policy: Month;

retention policy: Month;

statistics: elapsed = 2336699, index size (KB) = 410202,

                              amount used (KB) = 410202, entries = 2646380;

directive: ;

group: NMC;

save set: "NMCASA:/gst_on_networker/lgto_gst";

  Backup renamed directories: Disabled;

Checkpoint enabled: Disabled;

      Checkpoint granularity: Directory;

priority: 500;

   File inactivity threshold: 0;

File inactivity alert threshold: 0;

remote access: ;

remote user: ;

password: ;

              backup command: savepsm.sh;

     application information: ;

ndmp: No;

             NDMP array name: ;

De-duplication backup: No;

De-duplication node: ;

Pool: BTI;

          Data Domain backup: No;

Client direct: Enabled;

         Probe resource name: ;

virtual client: No;

physical host: ;

           Proxy backup type: ;

           Proxy backup host: ;

executable path: ;

    server network interface: ;

aliases: networker, networker.servers.intra, networker-b,

networker-b.servers-bck.intra, networker-m,

networker-m.servers-mgmt.intra;

index path: ;

          owner notification: ;

parallelism: 12;

physical client parallelism: Disabled;

storage nodes: nsrserverhost;

       recover storage nodes: ;

hard links: Disabled;

             short filenames: Disabled;

BMR: Disabled;

BMR options: ;

backup type: ;

client OS type: AixOS;

CPUs: 8;

NetWorker version: 8.0.1.1.Build.132;

enabler in use: Yes;

       licensed applications: ;

licensed PSPs: ;

RDZ client is simply a Restricted Data Zone instance.

We would like to give it to users/tenants as it is part of a multy tanency feature.

Then these RDZ clients have their own tape libraries etc.

It is diyplaying a message: waiting for 1 writable volume to backup pool ... tape

Ah ok, that new feature... ok it is clear.  If you go to pool configuration, you will see devices selected.  For this RDZ there is device available to mount pool which you wish to use on backup server.  As index and bootstrap is saved under backup server ownership (so it is not part of RDZ), your recommended way of doing this is by creating index groups and do index&bootstrap backup only with it.

The problem with this is that an index group is outside of the RDZ so when you want to modify anything on that  RDZ you the have to remove all the clients first. A client have to be added to two places: inside RDZ and outside for the index group.

There should be a way to index inside the RDZ.

Index and bootstrap are databases owned not by client, but by backup server.  That means they reside outside RDZ domain. While I didn't play with RDZ, I suspect all you need to do is:

a) set no index save on group in RDZ

b) create index group and run it

So unless NW would allow visibility of RDZ client on main portion of NW then yes, you need to create it there as well. Another option is that you must have device on backup server for each RDZ (unless sharing device between RDZ is supported which I really don't know as I do not use RDZ approach).

Hi,

it works like you mentioned, but this was my initial starting point.

I want to separete the RDZ clients so they wouldn't need to be linked outside of the RDZ.

Problem is when you have multiple clients,multiple RDZ's and you want to change the config of the RDZ then each time you have to remove the client from the index group and also from the RDZ config.

What do you mean by this:

"Another option is that you must have device on backup server for each RDZ" ?

Hello,

will test that, thank you.

May I ask another question?

I am looking for info on how to configure a networker server to be in multiple domains.

This is what I found, but after registration can not access the info.

Any info on how to set up networker for this?

Thanks

Dual Homed NetWorker.

Please loging to http://powerlink.emc.com and review the following Knowledge Objects. They have all you need to consider for configuring multi-homed NetWorker servers and clients

Multi-homed NetWorker servers and clients

esg50319: NetWorker backup over a dedicated network

esg58519: How to configure a NetWorker server with multiple network interfaces for backups 

esg55057: How to backup NetWorker server and clients using multiple NICs

Hello,

You can create index pool for every RDZ. Then you don't select index device from rdz device filter. It will be success.