08-09-2012 02:01 AM
Hi!
How could i disable mesia server role on master server ? I see that my clients try to perform restore through master server and in some cases master server tries to perform duplication job to tape. I want that it will used only as master server, cause i have two additional media servers. Is it will be enough to disable it through Device - Media Servers - Deactivate ?
08-09-2012 02:48 AM
08-09-2012 03:01 AM
I have selected so, but it still use master server for read purposes.
08-09-2012 03:08 AM
08-09-2012 07:00 AM
Hi
While creating storage unit select the media server. While creating policy, select the STU which has media server.
While restoring, If u want to direct the data from master to media server. Refer to FORCE MEDIA RESTORE option.
08-09-2012 11:28 AM
If media server is used for duplications, it is because it is configured to do so.
How are your duplications configured - Vault? Disk staging? SLP?
Double-check all of these. If a Storage Unit Group is specified, remove master STU from STUG.
For backups, check ALL policies and schedules to see if Master STU is specified anywhere.
Do not remove Master STU or disable it as media server - it is best for master to perform catalog backup to its own devices.
For restores:
restores are performed by the media server who performed the backup.
So, if master has done the backup, it will perform the restore.
See FORCE_RESTORE entry as suggested above.
08-09-2012 11:56 PM
Hi Marianne !
My duplication configured through SLP. I make backup to STU1_DISK, then duplicate to STU2_DISK and STUGRP_TAPE. Master server does not marked for use in *_DISK STU`s, inside STUGRP_TAPE just one STU which belongs to media server. No bindings inside policies to master server, it was checked out.
Duplication jobs still go through master server only for disk to tape duplication, but master server does not used for backup, all backup trafic (excluding catalog backup) goes through media server, it is the one ho has got access to STU`s.
08-10-2012 01:40 AM
When were STUG changes made? After initial backup to disk?
If so, the entire lifecycle of images are determined at backup time.
If not, master STU is still hidden somewhere in the config.
We can help to trace it if you post output of all of the following:
bpstulist -g -U
nbstl -L
Please highlight Master STU in bpstulist output.
08-14-2012 05:11 AM
bpstulist -g -U
Label: STU-LOCAL
Storage Unit Type: Disk
Storage Unit Subtype: DiskPool (6)
Host Connection: media1
Concurrent Jobs: 64
On Demand Only: yes
Max MPX: 1
Max Fragment Size: 524288 MB
Block Sharing: no
Ok On Root: no
Disk Pool: Local_DP
Snapshots: no
Replication Primary: no
Replication Source: no
Replication Target: no
Mirror : no
Independent : no
Label: STU-REMOTE
Storage Unit Type: Disk
Storage Unit Subtype: DiskPool (6)
Host Connection: media1
Concurrent Jobs: 64
On Demand Only: yes
Max MPX: 1
Max Fragment Size: 524288 MB
Block Sharing: no
Ok On Root: no
Disk Pool: Remote_DP
Snapshots: no
Replication Primary: no
Replication Source: no
Replication Target: no
Mirror : no
Independent : no
nbstl -L
------------------------------------------------------------------------
Name: Oraslp
Data Classification: (none specified)
Duplication job priority: 0
State: active
Version: 3
Operation 1 Use for: 0 (backup)
Storage: STU-LOCAL
Volume Pool: (none specified)
Server Group: (none specified)
Retention Type: 0 (Fixed)
Retention Level: 9 (infinity)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: 0 (client)
Operation ID: (none specified)
Operation Index: 1
Operation 2 Use for: 1 (duplication)
Storage: STU-REMOTE
Volume Pool: (none specified)
Server Group: (none specified)
Retention Type: 0 (Fixed)
Retention Level: 1 (2 weeks)
Alternate Read Server: (none specified)
Preserve Multiplexing: false
Enable Automatic Remote Import: false
State: active
Source: Operation 1 (backup:STU-LOCAL)
Operation ID: (none specified)
Operation Index: 2
Operation 3 Use for: 1 (duplication)
Storage: TAPE_GROUP
Volume Pool: NetBackup
Server Group: Any
Retention Type: 0 (Fixed)
Retention Level: 9 (infinity)
Alternate Read Server: (none specified)
Preserve Multiplexing: true
Enable Automatic Remote Import: false
State: active
Source: Operation 2 (duplication:STU-REMOTE)
Operation ID: (none specified)
Operation Index: 3
------------------------------------------------------------------------
09-07-2012 06:52 AM
bump
09-07-2012 12:27 PM
If I have understood this correctly, the master is sometimes used to make the SLP duplication and you do not wish this to happen.
I'm guessing you are running NBU 7.x, if so, try this :
nbemmcmd -changesetting -common_server_for_dup required -machinename <master server name>
This should force NBU to match the duplication media server to be the same server that ran the SLP backup.
Martin
09-07-2012 09:37 PM
Difficult to assist when you don't give us all relevant info.
You showed us two Disk STUs, both connected to SAME media server although one local and the other remote?
You also have duplication to 'TAPE_GROUP' but bpstulist output does not contain ANY tape STU or group??