Lotus-notes single mailbox backup problem

[Malak]

Hello All,

I'm  having a strange(or not) situation.

Netbackup 7.1.0.3 (server and medias)

I need to backup a single mailbox from Lotus server (besides from normal backup - this one work's fine) .

I’m on netbackup customer side (lotus server cluster logical node), and when I try to backup, in backup, archive and restore windows, the backup window, does not have the Lotus notes TAB.

I follow this “how to”

http://www.symantec.com/business/support/index?page=content&id=HOWTO47916#v14705287

My problem is on step 6.

Does anyone saw this?

Thank you

MALAK

[Yasuhisa_Ishika]

What OS are you using?
I tryed same operations in BAR on RHEL, there are no tab in Backup Files window. But text box for notes.ini file is present on this window.
As documented in NetBackup 7.1 for Lotus Notes Administrator's Guide page 52, Lotus Notes Options tab is present in BAR on Windows. BAR on other platform does not have Lotus Notes Options tab.

6 Select Actions > Backup.
7 Select the backup options, as follows:
■ When you back up a server partition, provide the absolute path for the
notes.ini file.
(On Windows clients, click on the Lotus Notes Options tab.)
Associate this notes.ini file with the particular server partition that you
want to perform the backup.
■ (UNIX or Linux) When you back up one of multiple installations of Domino
server, provide the absolute path for the notes.ini file. Associate this
notes.ini file with the Domino installation you want to back up. Also
provide the directory of the Domino server installation.

[Malak]

Hello Yasuhisa,

Thank you for your reply. Our servers, in this case, are all windows (Master, media, and client).

This looks like some minor step I'm not going throut.

This backups concerns a Cluster logical node, but this client is also in another policy as a simple windows client.

One policy for cluster node, where we backup Lotus database, logs, and all lotus concening files

Another policy for SO(windows) for all non-lotus stuff.

[Malak]

Making a long history short... the "Lotus Notes Options tab" does not appear on backup options.
We are trying to backup a single mailbox, and it gives an error like 245 or 240 ....

Windows servers and client.

[Marianne]

Please show us you Lotus Notes policy config.

On master, run the following from cmd:

<install-path>\veritas\netbackup\bin\admincmd\bppllist <policy-name> -U

[Yasuhisa_Ishika]

How did you configured 'Cluster', Domino's native cluster feature or other HA clustering software like MSCS(MSFC), VCS or so on?

On BAR, can you find [Lotus Notes] on top of All Folders tree?
If NetBackup detect that Lotus Domino is installed on the host, you can see [Lotus Notes] here.
When you can not find [Lotus Notes] on top of tree, try to set [INIT path] and [Path] from Client Host Propertis -> [Windows Client] -> [Lotus Notes].

[Malak]

Hello Marianne,

here goes the policy config:

Policy Name:       PL_LOGICA_LOTUS_LDEP06

  Policy Type:         Lotus-Notes
  Active:              yes
  Effective date:      12/14/2011 16:52:14
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           stu_dedupe_med1
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds

  Granular Restore Info:  no
  Ignore Client Direct:  no
  HW/OS/Client:  Windows-x86   WindowsXP     ldep06

  Include:  BACKUP_TRANSACTION_LOGS
            NOTES_INI_PATH=L:\lotus\domino\ldep06\notes.ini
            LOTUS_INSTALL_PATH=C:\LOTUS\DOMINO
            L:\lotus\domino\ldep06
            M:\lotus\domino\ldep06

  Schedule:          User
    Type:            Application Backup
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 4 (2 months)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          domingo    00:00:00  -->  domingo    24:00:00
          segunda-f  00:00:00  -->  segunda-f  24:00:00
          terþa-fei  00:00:00  -->  terþa-fei  24:00:00
          quarta-fe  00:00:00  -->  quarta-fe  24:00:00
          quinta-fe  00:00:00  -->  quinta-fe  24:00:00
          sexta-fei  00:00:00  -->  sexta-fei  24:00:00
          sßbado     00:00:00  -->  sßbado     24:00:00

  Schedule:          Full
    Type:            Automatic Backup
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Calendar sched: Enabled
      Saturday, Week 1
      Saturday, Week 2
      Saturday, Week 3
      Saturday, Week 4
      Saturday, Week 5
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     03:20:00  -->  Sunday     10:10:00
          Monday     03:20:00  -->  Monday     10:10:00
          Tuesday    03:20:00  -->  Tuesday    10:10:00
          Wednesday  03:20:00  -->  Wednesday  10:10:00
          Thursday   03:20:00  -->  Thursday   10:10:00
          Friday     03:20:00  -->  Friday     10:10:00
          Saturday   03:20:00  -->  Saturday   10:10:00

  Schedule:          Diff_inc
    Type:            Differential Incremental Backup
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 1 (2 weeks)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Calendar sched: Enabled
      Sunday, Week 1
      Monday, Week 1
      Tuesday, Week 1
      Wednesday, Week 1
      Thursday, Week 1
      Friday, Week 1
      Sunday, Week 2
      Monday, Week 2
      Tuesday, Week 2
      Wednesday, Week 2
      Thursday, Week 2
      Friday, Week 2
      Sunday, Week 3
      Monday, Week 3
      Tuesday, Week 3
      Wednesday, Week 3
      Thursday, Week 3
      Friday, Week 3
      Sunday, Week 4
      Monday, Week 4
      Tuesday, Week 4
      Wednesday, Week 4
      Thursday, Week 4
      Friday, Week 4
      Sunday, Week 5
      Monday, Week 5
      Tuesday, Week 5
      Wednesday, Week 5
      Thursday, Week 5
      Friday, Week 5
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     00:10:00  -->  Sunday     10:00:00
          Monday     00:10:00  -->  Monday     10:00:00
          Tuesday    00:10:00  -->  Tuesday    10:00:00
          Wednesday  00:10:00  -->  Wednesday  10:00:00
          Thursday   00:10:00  -->  Thursday   10:00:00
          Friday     00:10:00  -->  Friday     10:00:00
          Saturday   00:10:00  -->  Saturday   10:00:00

[Marianne]

HW/OS/Client:  Windows-x86   WindowsXP     ldep06

OS : WindowsXP ??

Client name : ldep06

Is the client name in the policy the physical nodename or the virtual name?

For a User backup, the client will send its 'configured' client name to the master as part of the request. This configured name is normally the same as the physical nodename. This means that the master cannot find the client name in the Notes policy.

Probably the easiest to config a separate Notes policy containing only User schedule with physical nodenames in Client list.

[Malak]

Sorry, OS client information is not correct.

This customer is win2003 with NB 7.1.0.3

The ldep06 it the cluster node name.

So, for what I understand we need to creat a policy Notes type with physical name, for client to use when a user_backup is needed. right?

We create a new policy, Lotus_Notes type, with physical nodenames as clientes, and only a User_Backup schedule. The result is:

"the specified policy is not of the correct client type(245)"

For what I can understand, the server does not recognise the physical nodes as Lotus type system, which seems normal to me.
The Lotus-Notes client is the logical node.

The BAR "should know" that when I loggin to ldep06 I'm in a Lotus-Notes "machine type" for netbackup
And when I loggin into ldepm02(physical), I'm in a "windows type" system, for what concerns netbackup

Any new ideas?

Thank you.

[Yasuhisa_Ishika]

Observing you policy configuration, your Lotus Domino is not standart setup.
Try to specify 'INI Path'(notes.init pathname) and Path(installation folder) attributes from Client Host Propeties.

[Marianne]

Try to change the configured client name to the virtual name. NBU sends the 'configured' name to the master. You also got status 245 when you were trying with the virtual name in the policy?

On the active node in the BAR GUI, open File -> Properties.

Change the Client name to the virtual name.

Please also check that the OS selection in the Clients tab is correct.

[Malak]

This cluster is a MSCS.

There's 2 physical nodes ldepm01 & ldepm02 and 2 logical nodes ldep01 & ldep06

On BAR, we can't see [Lotus Notes] on all foldes tree.

There's a policy for fhysical backup (MS-Windows type), which backup up all SO related information and there's 2 Lotus-Notes type policies one for ldep01 and another for ldep06, in which we backup mailboxes, transations logs and INI information for Lotus.

This 2 physical nodes cluster has 2 logical Notes nodes, so I can't configure on client properties the INI Path, only the Path is configured (C:\lotus\notes).

Thank you,

[Malak]

Yes, when we change it, the problem persists, with error 240 (no schedule, or something...) we try it yesterday...

It looks like those properties only apply to restores. Even when we change it, on master console monitor we see a job starting with physical server name, and this should be with logical name.

Thank you.