Logical Back up taking long time

[AHassan]

Hi,

I am trying to import a logical backup (around 1.5 GB) and it is taking long time as it is being import for last 48 hours and still only half way through.

The "Commands acc/Sec" are 0 at the moment but "Analyzed commands" are increasing at very slow speed which means it is still importing data.

This is on V1R3. Any idea what could be the issue? - any previous experiences?

Regards,

Asim

[jhorber]

As Arunas said, using logical backup to transfer data may not be the most efficient way (although it can be justified in certain situations) for large repositories.

Prefer SQL backup and restore when possible.

Logical backup is a time consuming process and import of logical backup is a more time consuming process.
Common causes of slow import are:

• Low performance infrastructure (poor access to database server).
• Multiple rejects (many possible causes).

[Arunas]

If its RDBMS data , then inform DB team to handle the backup from their side and restore it in new database .

 This step is done you can refer your environment to these DB. This is the easy process rather than logical backup . In logical backup there might be the chance for data redundant (metamodel connection might loss)when you restore it if data is more than a GB .

I would suggest goahead with backend restore process.