Video Screencast Help

Import not starting on 5020

Created: 22 Sep 2012 • Updated: 21 Nov 2012 | 20 comments
Rami Nasser's picture
This issue has been solved. See solution.

Hi All,

I have two sites :one production with master and media 7.1.0.4 and appliance 5020 and second DR with the same . we configured SLP to duplicate backup from PR to DR through AIR . the issue is duplication giving me status 0 but in the other side import never starting.the oposite side working fine( i mean duplication to PR from DR succeed with status 0 and the import starting in the PR .we opened case with symantec for more than 50 days and they could't solve the issue and at last they ask to upgrade the patch from 1.4 to 1.4.2 . I feel upset from this because the environment is new and the appliances also .if they asked to do this from the begining so i can understand but asking this now this not normal and i believe after upgrade it may not work. and i dont thing it is issue of the applianc version because the other one is working.

hope i can find here some solution that they may help us to solve the issue.

Regards,

Comments 20 CommentsJump to latest comment

Mark_Solutions's picture

You have probably already been asked to do this but if not .. Just in case it is a simple typo in your import SLPs on the remote site I would delete them (just the Import ones you have made on the site that doesn't import!!) and then on the Master Server add, under netbackup\db\config the LIFECYCLE_PARAMETERS file.

In that file just add the line:

AUTO_CREATE_IMPORT_SLP = 1

This then, as soon as it detects images arrive, creates the SLPs it needs to import them.

There may be something like a SLP version causing issues so this lets it start afresh - useful to run:

nbstl -L -all_versions

To see if there is more than one version that could be causing issues anyway.

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Rami Nasser's picture

I hope that what you suggesting now will work , because 9 of symantec support engineers were worked on this case and didnt solve the issue.

I will try it tommorow and come back to you.

Regards,

Rami Nasser's picture

yes now i remember you because the lines already added but the issue still exist ,i removed the SLP and nothing new.the only things is :SLP versions as follow:

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbstl -L -all_versions
                                Name: DR_PRIMARY_REPLICATION
                 Data Classification: (none specified)
            Duplication job priority: 0
                               State: active
                             Version: 2
 Destination  1              Use for: backup
                             Storage: STU-RYHG2-DR
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: Fixed
                     Retention Level: 1 (2 weeks)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: true
                               State: active
                              Source: (client)
                      Destination ID: (none specified)
 Destination  2              Use for: duplication to remote master
                             Storage: Remote Master
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: Fixed
                     Retention Level: 8 (1 year)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: false
                               State: active
                              Source: Destination 1 (backup:STU-RYHG2-DR)
                      Destination ID: (none specified)
------------------------------------------------------------------------
                                Name: DR_PRIMARY_REPLICATION
                 Data Classification: (none specified)
            Duplication job priority: 80000
                               State: active
                             Version: 1
 Destination  1              Use for: backup
                             Storage: STU-RYHG2-DR
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: Fixed
                     Retention Level: 1 (2 weeks)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: true
                               State: active
                              Source: (client)
                      Destination ID: (none specified)
 Destination  2              Use for: duplication to remote master
                             Storage: Remote Master
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: Fixed
                     Retention Level: 8 (1 year)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: false
                               State: active
                              Source: Destination 1 (backup:STU-RYHG2-DR)
                      Destination ID: (none specified)
------------------------------------------------------------------------
                                Name: DR_PRIMARY_REPLICATION
                 Data Classification: (none specified)
            Duplication job priority: 0
                               State: active
                             Version: 0
 Destination  1              Use for: backup
                             Storage: STU-RYHG2-DR
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: Fixed
                     Retention Level: 1 (2 weeks)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: true
                               State: active
                              Source: (client)
                      Destination ID: (none specified)
 Destination  2              Use for: duplication to remote master
                             Storage: Remote Master
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: Fixed
                     Retention Level: 8 (1 year)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: false
                               State: active
                              Source: Destination 1 (backup:STU-RYHG2-DR)
                      Destination ID: (none specified)
------------------------------------------------------------------------
                                Name: primary-DRreplication
                 Data Classification: (none specified)
            Duplication job priority: 0
                               State: active
                             Version: 0
 Destination  1              Use for: import
                     Import Priority: -1
                             Storage: STU-RYHG2-DR
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: Remote (Imported) Expiration Date
                     Retention Level: Not Used (remote expiration)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: false
                               State: active
                              Source: (client)
                      Destination ID: (none specified)

 

please advice !!!!

Jeff Foglietta's picture

i am following this thread closely.. This is certainly would be a serious problem.. I did notice that the enable auto import was set to false in all versions. This should be true with the LIFECYCLE_PARAMETERS set.. yes?

Jeff Foglietta

Practice Lead - Data Protection and High Availability

AlistairR's picture

I have had the same problem - tried everything they suggested - can't get logs out for various reasons - but I have no errors. Luckily I have an empty second one so am about to rebuild it on  1.4.1. I also notice trying to get the properties under credentials/storage systems it fails to work on the destination master (times out). I have rebuilt it and I notice it works briefly for about 15-30 seconds following a restart services, yet despite the rebuild it does not work. I think the communication and image flags between the destination 5020 and destination master - yet can find no errors - only "no images to import"

I am getting round this and I know the replication is working by performing a phase 1 import every morning so if I need to I can run a quick phase2 and recover at the second site. This is not ideal as I need SLP's to help duplicate tape images!

Please keep this post up to date - as soon as I can rebuild the master (on 7.5.03) & 5020 I will however its a bit over the top to resolve this issue!

Mark_Solutions's picture

Very interesting!

It would be nice to use nbstl to modify this but it does look like it just picks it up from the LIFECYCLE_PARAMETERS file so it is worth double checking it all as it doesn't look like the setting has been picked up so a typo, wrong case, wrong place etc etc

 

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Rami Nasser's picture

my confuse in this issue is: the appliances in production site and DR site identical . the environment is new and all jobs running successfuly (backup and duplication in production success with status 0 but import not starting in DR site . and all backup jobs and duplication in DR success with 0 status and also import in production success with status 0) both sites with the same configuration. the support engineers from backline after more than month collecting logs they asked me to upgrade patch from 1.4 to 1.4.2. but i didnt do it yet and i have doubt that upgrade will solve the issue because the other appliance working fine with 1.4. also i read the technote about the steps to upgrade but no one giving garantee that i will not loose the images in the appliances in case of upgrade failed!!!sad

Mark_Solutions's picture

Can we see the nbstl -L -all_versions from the other site as well please

Also, out of interest could you take a look in netbackup\db\ss\ on each MAster and you will see files that relate to the name of the import slps at each site - rename them so we know which is from main and from dr and attached those too (rename then a .txt)

Finally (for now) can we see the pd.conf file from each media server (renamed again so we can see which is which)

Thanks

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Rami Nasser's picture

I will try to do this soon because iam not available all the time in the site:

nbstl -L -all_versions from PS

 netbackup\db\ss\ on each MAster

pd.conf file from each media server( you need the log or the pd.config text file.because i edit pd.config and changed to verbose 10 then run one job then we have collected the log.(also soon will send you the log)

Regards,

AttachmentSize
120918_1_pdpluginDR.rar 2.17 MB
Mark_Solutions's picture

Just need to see the pd.conf for now and the other files when you get chance - pdplugin logs is toooo big!

Thanks

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Rami Nasser's picture

ofcourse tooooooooooo big because we set the verbose 10!!!!!

Rami Nasser's picture

As disscussed with you :

 I run the nbstl -L -all_versions from Production  the result was

C:\Program Files\Veritas\NetBackup\bin\admincmd>nbstl -L -all_versions

Exit error: no entity was found

EXIT status = 227

 

AttachmentSize
ss dr.rar 1.3 KB
ss prodution.rar 5.91 KB
Mark_Solutions's picture

OK - I see several verisons of the files but don't understand why the command does not work in Production!

The only difference between the import jobs is one value:

655 *NULL* SLP_primary-DRreplication 2147483647 0 *NULL* 0 0

655 *NULL* SLP_DR_PRIMARY_REPLICATION 2147483647 0 *NULL* 0 2

Will try and find out exactly what this relates to

Could you add some screen shots (as attachments) of the SLPs and each of their parts so that I can see exactly what you have

Thanks

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Rami Nasser's picture

Appreciate your interest. I will try to do this ASAP because as i mentioned before that I'm not on the site all the time

Regards,

Rami Nasser's picture

symantec support asked to upgrade patch from 1.4 to 1.4.2 to solve this issue!!! but unfortunatly i did the upgrade and the issue still existno.

Iam looking to solve this issue by this way:

configure new appliance and replace the one having the issue then add that appliance with images as secondary(not SPA) please advice is it works?????

jandersen's picture

Hi,

Just to be sure: Did you check the timezone and time settings on your two master servers and on the 5020's?
Are they in sync? Issues you experience could be caused by 'out of sync' masters and appliances.
(But again: this should have been checked by support, so I hope this is not the issue)

--jakob;

 

Rami Nasser's picture

thanks for your response.letme tell you one thing: I logged in appliance through gui there in alert windows giving me error could not sync wth server"or some thing like this" so i told the engineer to check this if it may causing the problem.he answer me that doesnt matter.i didnt think that it doesnt matter ,so i checked the time zone in the appliance and the master server i found the time zone in the appliance different than the master so i adjust the time zone inside the appliance but the same error still indecated and the issue with import still exist.if you have any practice in this please advice.

regards

jandersen's picture

The important thing is that the two masterservers are in sync.

If the ctime for the image going to be imported lies in the future, then the importing masterserver will just 'sit and wait.

 

--jakob;

AlistairR's picture

Think I finally managed to fix this. First had to clear down some images manually as SPA filling up - phase 1 and phase 2 import followed by expire.

This morning I upgraded the destination master to 7.5.0.4. As soon as I did so the missing imports automatically appeared - pendimplist is now full of the missing last 6 months!

Looks like there is an index/counting bug in 7.1.04, or the db problem I had created has been fixed as part of the upgrade ( even though db validate and nbcc were clean). Either way I am happy as I saw no bugs or errors in logs previously - only errors now are 191's where I have already removed the images manually.

Rami Nasser's picture

After more than 80 days working on this case they were unable to solve the issue. they asked to reimage the appliance and configure it from scratch or configure other node as SPA .I did this and then the issue was solved.

it seems that there are hardware issue couldnot be fixed.

Thanks to all for helping to solve the issue.

Regards.

SOLUTION