Solved: ERROR: invalid backup file version. Exception: Error while unzipping invalid wcs 7.x export file

cisco-renexter · ‎07-17-2012

Hi,

I'm having a serious issue with your brend new Cisco Prime Network Control System (NCS) and i would appreciate if someone could give me good answers.

After a background backup task failure, the database was entirelly corrupted and the oracle server no longuer wanted to start. And because of that the NCS web server is unusable, since no one can log in.

We tryed to restore to last known backup obtained after a former suucessful backup. But we get this error:

"ERROR: invalid backup file version. Exception: Error while unzipping invalid wcs 7.x export file"

All the lost data was previously migrated from the former WCS 7.x server. Before this issue everything was working fine.

So we think that the appliance is seeing the backup file from NCS as a WCS backup.

We need to find rapidly a solution. Here is our configuration:

We formerly had WCS 7.0.172.0 hosted on Microsoft Windows Server 2003 SP2 with the above caracteristics:

Intel(R)Xeon(R) CPU 5120 @ 1.86Ghz 1.87Ghz 16GB of RAM.

We now have NCS Version 1.1.1.24 running under Cisco Application Deployment Engine

OS Release: 2.0
ADE-OS Build Version: 2.0.1.038
ADE-OS System Architecture: x86_64

Mark Withers · ‎06-19-2013

I was getting this error too. TL;DR: When you transfer the wcs.zip file to your FTP server, make sure you are using BINARY mode... which is often NOT the default FTP mode.

Long Version:

TO GET THIS ERROR, what I had done was use the Windows CLI FTP command to transfer my "wcs.zip" to the NCS FTP server.

-----BEGIN WRONG STEPS-----

C:\ftp

ftp> open x.x.x.x

Connected to x.x.x.x.

220 Service ready for new user

User (x.x.x.x:(none)): ftp-user

331 User name okay, need password for ftp-user

Password:

230 User logged in, proceed

ftp> put wcs.zip

200 Command PORT okay

150 File status okay; about to open data connection

226 Closing data connection

ftp: 526768949 bytes sent blah blah etc

-----END WRONG STEPS-----

I would then run "ncs stop" and "ncs migrate" and get the "ERROR: invalid backup file version. Exception: Error while unzipping invalid wcs 7.x export file".

I remembered something from my misspent youth: Windows, for no good reason, likes to transfer files in ASCII mode. UNIX (which LINUX comes from) prefers BINARY, and the two do not like to negotiate.

TO FIX THIS, I had to just FTP in Binary mode.

-----BEGIN RIGHT STEPS-----

C:\ftp

ftp> open x.x.x.x

Connected to x.x.x.x.

220 Service ready for new user

User (x.x.x.x:(none)): ftp-user

331 User name okay, need password for ftp-user

Password:

230 User logged in, proceed

ftp> binary

200 Command TYPE okay

ftp> put wcs.zip

200 Command PORT okay

150 File status okay; about to open data connection

226 Closing data connection

ftp: 526768949 bytes sent blah blah etc

-----END RIGHT STEPS-----

NOW when I enter "ncs stop" (actually... had to restart them... then stop them... x.x) and then the proper "ncs migrate" commands, I get a happy output and don't have to go home late troubleshooting this.

" Stage 1 of 5: Decompressing backup ...

-- complete.

Stage 2 of 5: Restoring Support Files ...

: Restoring the Domain Maps ...

: -- complete.

: Restoring the License files ...

: -- complete.

-- complete.

Stage 3 of 5: Restoring Data ...

"

I hope this helps anyone banging their head against the WCS->PI1.3 install wall.

(Note, WCS needs to be migrated to NCS 1.1.1.24 (NOT NCS 1.1.3!!!!!) before you can migrate to Prime Infrastructure 1.2 or 1.3, because for no readily apparent reason the "ncs migrate" command was removed from PI 1.2 and up. Also note, there is no "Prime Infrastructure 1.1;" they just renamed NCS to Prime Infrastructure after NCS 1.1 because. Yes, the sentence ends there. Great products, all 3, just... agonizing to migrate.)

View solution in original post

Jason Aarons · ‎11-06-2012

Julien did you get a solution? I got a similar error exporting WCS 7.0.230.0 to NCS 1.1.1.24.

I export userdata and then ran on NCS;

NCS/ncsadmin# configure

Enter configuration commands, one per line. End with CNTL/Z.

NCS/ncsadmin(config)# repository repo

NCS/ncsadmin(config-Repository)# url ftp://x.x.x.x

NCS/ncsadmin(config-Repository)# user admin password plain password

NCS/ncsadmin(config-Repository)# exit

NCS/ncsadmin(config)# exit

NCS/ncsadmin# ncs stop

Stopping Network Control System...

This may take a few minutes...

Network Control System successfully shutdown.

NCS/ncsadmin# ncs migrate wcs-data data.zip repository jongsoon

Initiating WCS 7x DB restore . Please wait...

INFO: no staging url defined, using local space. rval:2

Starting Network Control System...

This may take a few minutes...

Network Control System started successfully.

Stopping Network Control System...

This may take a few minutes...

Network Control System successfully shutdown.

ERROR: invalid backup file version. Exception: zip file not created by backup or export

NCS/ncsadmin#

mukka · ‎11-08-2012

did you get a solution?I have the same problem

thanks

Mark Withers · ‎06-19-2013

I was getting this error too. TL;DR: When you transfer the wcs.zip file to your FTP server, make sure you are using BINARY mode... which is often NOT the default FTP mode.

Long Version:

TO GET THIS ERROR, what I had done was use the Windows CLI FTP command to transfer my "wcs.zip" to the NCS FTP server.

-----BEGIN WRONG STEPS-----

C:\ftp

ftp> open x.x.x.x

Connected to x.x.x.x.

220 Service ready for new user

User (x.x.x.x:(none)): ftp-user

331 User name okay, need password for ftp-user

Password:

230 User logged in, proceed

ftp> put wcs.zip

200 Command PORT okay

150 File status okay; about to open data connection

226 Closing data connection

ftp: 526768949 bytes sent blah blah etc

-----END WRONG STEPS-----

I would then run "ncs stop" and "ncs migrate" and get the "ERROR: invalid backup file version. Exception: Error while unzipping invalid wcs 7.x export file".

I remembered something from my misspent youth: Windows, for no good reason, likes to transfer files in ASCII mode. UNIX (which LINUX comes from) prefers BINARY, and the two do not like to negotiate.

TO FIX THIS, I had to just FTP in Binary mode.

-----BEGIN RIGHT STEPS-----

C:\ftp

ftp> open x.x.x.x

Connected to x.x.x.x.

220 Service ready for new user

User (x.x.x.x:(none)): ftp-user

331 User name okay, need password for ftp-user

Password:

230 User logged in, proceed

ftp> binary

200 Command TYPE okay

ftp> put wcs.zip

200 Command PORT okay

150 File status okay; about to open data connection

226 Closing data connection

ftp: 526768949 bytes sent blah blah etc

-----END RIGHT STEPS-----

NOW when I enter "ncs stop" (actually... had to restart them... then stop them... x.x) and then the proper "ncs migrate" commands, I get a happy output and don't have to go home late troubleshooting this.

" Stage 1 of 5: Decompressing backup ...

-- complete.

Stage 2 of 5: Restoring Support Files ...

: Restoring the Domain Maps ...

: -- complete.

: Restoring the License files ...

: -- complete.

-- complete.

Stage 3 of 5: Restoring Data ...

"

I hope this helps anyone banging their head against the WCS->PI1.3 install wall.

(Note, WCS needs to be migrated to NCS 1.1.1.24 (NOT NCS 1.1.3!!!!!) before you can migrate to Prime Infrastructure 1.2 or 1.3, because for no readily apparent reason the "ncs migrate" command was removed from PI 1.2 and up. Also note, there is no "Prime Infrastructure 1.1;" they just renamed NCS to Prime Infrastructure after NCS 1.1 because. Yes, the sentence ends there. Great products, all 3, just... agonizing to migrate.)

Marvin Rhoads · ‎06-19-2013

Thanks for sharing your solution.

Endorsed and +5 for keeping a sense of humor.