07-09-2012 08:50 AM
hi,
we are at 7.5.01 master and media. after upgrade we changed one of policy full backup to to synthetic full backup to test. full ( synthtic full backup ) schedule is on sunday so today i check the acitivty monitor i seen the client is still job id and run the full backup just like other regular full backups.
question
1. if synthetic full backup doing his job in background does it create job id and activity on master/media server
2. how to confirm the full backup image created for that client is a synthetic full.
appreaciate your help
Solved! Go to Solution.
09-05-2012 05:29 AM
I opened a case with EMC/DataDomain to confirm this, as I had not been able to find it documented anywhere, and they did confirm that:
It is true that virtual/optimized synthetic will not be supported until DDOS 5.2 with OST plugin 2.5.x.
07-09-2012 09:01 AM
For a synth backup to run ..
The synth schedule must be in the same policy
A full must have run
One or more incrementals must have run.
Simply, remove the backup window for the full schedule, then once at least one incremental has run, manually run the Synth full schedule.
Martin
07-09-2012 09:19 AM
07-09-2012 09:33 AM
The synth schedule must be in the same policy - yes its in same policy ( basically that policy has just2 schedules now , once is incremental other is synthetic full )
A full must have run - yes , it has 2-3 full backup sets already before i configure this a syn full
One or more incrementals must have run - yes
remove the backup window for the full schedule - hmm. this syn full has backup window now so we need to remove this one ? if we remove that part how/when the syn full backup run ?
then once at least one incremental has run -- it doen't run any incremental after we configure the synthetic but it has 1 month incremental images ( until saturday we don't have synthetic , on sunday morning i confiurgure synthetic , its scheduled for sunday night )
marianne.. here is the policy info.
XXXXXXXX:/opt/openv/netbackup/$ bppllist XXX_XXX_XXX_XXX -U
------------------------------------------------------------
Policy Name: XXX_XXX_XXX_XXX
Policy Type: Standard
Active: yes
Effective date: 07/07/2010 18:41:52
Client Compress: no
Follow NFS Mounts: no
Cross Mount Points: no
Collect TIR info: yes, with move detection
Block Incremental: no
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: yes
Interval: 15
Policy Priority: 0
Max Jobs/Policy: 10
Disaster Recovery: 0
Collect BMR info: no
Residence: LTO4-XXX
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
HW/OS/Client: RS6000 AIX53 XXXX
RS6000 AIX53 XXXX
Include: ALL_LOCAL_DRIVES
Schedule: Full
Type: Full Backup
Frequency: every 14 days
Maximum MPX: 1
Synthetic: 1
Checksum Change Detection: 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)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 22:00:00 --> Monday 08:00:00
Schedule: Incremental
Type: Differential Incremental Backup
Frequency: every 1 day
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 2 (3 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)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Monday 22:00:00 --> Tuesday 06:00:00
Tuesday 22:00:00 --> Wednesday 06:00:00
Wednesday 22:00:00 --> Thursday 06:00:00
Thursday 22:00:00 --> Friday 06:00:00
Friday 22:00:00 --> Saturday 06:00:00
Saturday 22:00:00 --> Sunday 06:00:00
07-09-2012 10:53 AM
I meant to remove the Full window, not the Synth full window.
What happens if you run the synth full backup manually.
Martin
07-10-2012 08:41 AM
Full schedule is removed , we have only 2 schedules now 1. incremental 2. synthetic fulll
when i run the synth full backup manually , it failed with error:
unsupported image format for the requested database query(79)
here i attach the file with screen shots
07-10-2012 08:42 AM
forgot to mention: Master/media - 7.5.0.1
Client - AIX - 7.0.1
07-10-2012 09:34 AM
I'd be tempted to start from the beginning.
Create a new policy (don't copy the existing one) with the following schedules (this would remove *any* possibility of 'corruption' within the existing policy - it does happen, altho' infrequently):
a) a FULL without a backup window
b) an INCREMENTAL with whatever backup window is appropriate
c) a SYNTHETIC with whatever backup window is appropriate
Run a MANUAL backup of (a) to 'seed' the synthetic as it were.
Then either let nature take it's course & allow the scheduled incrementals to run & then the synthetic or run a few incrementals manually & then a synthetic.
07-10-2012 05:36 PM
New policy is created.
a) a FULL without a backup window - Done
b) an INCREMENTAL with whatever backup window is appropriate - done
c) a SYNTHETIC with whatever backup window is appropriate - done
manual full backup is completed today.. tomorrow this policy has incr schedule on thursday it has synth full backup schedule ..i update with results on thursday.
appreciate your help.
07-10-2012 11:33 PM
if this does work the synthetic full will only be as up-to-date as the last incremental as it does not read any changes from the client ('synthetically' composed of previous full & subsequent incrementals, hence the name) - for this reason our synthetics are scheduled directly after an incremental.
07-13-2012 02:13 PM
synthetic full backup schedule is yestarday night i check the activity today no job run in activity monitor and even i open backup,archive and restore client window there isno full backup image ...any suggestions ?
07-13-2012 02:21 PM
Yes, look in nbpem log and see what it did, or, didn't do ..
vxlogview -p 51216 -i 116 -d all -t hh:mm:ss
Go back as may hours necessary to some time before the window opened, relative to when you run the command. That is the <hh:mm:ss> is the past x amount of logs.
Also, there might be some useful info in the output of:
nbpemreq -subsystems 1 screen >file.txt
Martin
07-13-2012 02:48 PM
i check the bpcd no entires related to this client job at all
root@xxxxx:/opt/openv/netbackup/db/class$ vxlogview -p 51216 -i 116 -d all 14:00:00
V-1-1-8 An unknown argument 14:00:00 was passed.
root@xxx:/opt/openv/netbackup/ram$ nbpemreq -subsystems 1 screen > synthetic.txt
root@xxxx:/opt/openv/netbackup/xxx$ ls
synthetic.txt
root@xxxx:/opt/openv/netbackup/ram$ more synthetic.txt
Maximum output size exceeded, see log
07-13-2012 04:34 PM
root@xxxxx:/opt/openv/netbackup/db/class$ vxlogview -p 51216 -i 116 -d all 14:00:00
V-1-1-8 An unknown argument 14:00:00 was passed.
Run the command without screen
nbpemreq -subsystems 1
This then goes into the pem log
You need -t
vxlogview -p 51216 -i 116 -d all -t 14:00:00
And ... what is the name of the client, and policy ?
Martin
07-16-2012 03:11 PM
vxlogview -p 51216 -i 116 -d all -t xxxxxx , no entry . policy didn't even initiated/started. open case with support , as a first point they want to disable allow multiple data stream option in policy and he created a new one today evening it supposed to do synth full i let u guys know the update and results.
07-16-2012 07:08 PM
Saw your first policy setting - right before Andy asked for creating a new policy. That policy does not have a Synthetic full schedule, well.. it has, but you're not supposed to change the typical full schedule to be "synthetic", you need to create a new synthetic full schedule on top of that.
One simple check for your new policy:
a) a FULL without a backup window - Done
b) an INCREMENTAL with whatever backup window is appropriate - done
c) a SYNTHETIC with whatever backup window is appropriate - done
Can you provide policy details again as in bppllist output? Can you confirm if SYNTHETIC schedule has the "synthetic" enabled?
If it's a scheduling problem, nbpem log should be collected to check.
07-19-2012 12:41 PM
sorry for the dealy.. the issues is Data Domain OST version, we are at 2.4 which NB opt synthetic compatable with OST 2.5 so i upgraded that to 2.5 today and compatable OS as well. i let u guys know the update. thank you.
07-26-2012 01:15 PM
synthetic full backup schuedule is created ( new one )
full backup completed
incremental completed
synfull failed again even after i upgraded the OST and DDos version to compatable syn versions.
root@xxxx:/opt/openv/netbackup/scripts$ bppllist xxxxxx_0800 -U
------------------------------------------------------------
Policy Name: xxxxxx_0800
Policy Type: Standard
Active: yes
Effective date: 07/07/2010 18:41:52
Client Compress: no
Follow NFS Mounts: no
Cross Mount Points: no
Collect TIR info: yes, with move detection
Block Incremental: no
Mult. Data Streams: yes
Client Encrypt: no
Checkpoint: yes
Interval: 15
Policy Priority: 0
Max Jobs/Policy: 10
Disaster Recovery: 0
Collect BMR info: no
Residence: xxxxxx
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Granular Restore Info: no
Ignore Client Direct: no
Enable Metadata Indexing: no
Index server name: NULL
Use Accelerator: no
HW/OS/Client: RS6000 AIX53 XXXX
RS6000 AIX53 xxxx
RS6000 AIX53 xxx
RS6000 AIX53 xxxx
Include: ALL_LOCAL_DRIVES
Schedule: Full
Type: Full Backup
Frequency: every 7 days
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 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)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Tuesday 07:50:00 --> Tuesday 23:10:00
Schedule: SynFull
Type: Full Backup
Frequency: every 7 days
Maximum MPX: 1
Synthetic: 1
Checksum Change Detection: 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)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Thursday 08:00:00 --> Thursday 20:10:00
Schedule: Incremental
Type: Differential Incremental Backup
Frequency: every 1 day
Maximum MPX: 1
Synthetic: 0
Checksum Change Detection: 0
PFI Recovery: 0
Retention Level: 2 (3 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)
Residence is Storage Lifecycle Policy: 0
Schedule indexing: 0
Daily Windows:
Sunday 08:00:00 --> Sunday 20:10:00
Monday 08:00:00 --> Monday 20:10:00
Wednesday 08:00:00 --> Wednesday 20:10:00
Friday 08:00:00 --> Friday 20:10:00
Saturday 08:00:00 --> Saturday 20:10:00
error msg in job activity is:
/26/2012 1:05:05 PM - Error WriteVirtualSynth::handleEndpointMsg(pid=1490) received EXIT message from writer parent with error status=media write error(84)
7/26/2012 1:05:05 PM - Error WriteVirtualSynth::giveEndpointStatus(pid=1490) received end point error = media write error(84)
7/26/2012 1:05:05 PM - Error PlanAdmin::actionDone(pid=1490) action failed, error=media write error(84)
7/26/2012 1:05:37 PM - Error SynthJob::cleanup(pid=1490) end bpsynth with status = media write error(84)
7/26/2012 1:05:37 PM - end Parent Job; elapsed time: 00:00:47
7/26/2012 1:05:37 PM - end writing
am i missing any settings in policy ?
08-21-2012 11:52 AM
Bottom line is: Optimized synthetic full backups are didn't work until Data domain OS is 5.2 which is not released to public yet so . its closed case now.
09-05-2012 05:29 AM
I opened a case with EMC/DataDomain to confirm this, as I had not been able to find it documented anywhere, and they did confirm that:
It is true that virtual/optimized synthetic will not be supported until DDOS 5.2 with OST plugin 2.5.x.