Problems upgrading from LMS 3.0 to LMS 3.2 - the backup fails.

Answered Question

I'm upgrading from LMS 3.0 to LMS 3.2 on Solaris. I've met all of the prereq's, patches, etc. It keeps failing on the Backup...It claims I need 15 Gig for the backup. The backup directory I'm using (/opt/backup) has 35 Gig free, so that shouldn't be the issue.

Here is the error I'm seeing in the backup.log;

okcwsi:tail backup.log

tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis

co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi

gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c2950-i6q4l2-mz.121

-13.EA1c.bin: prefix is greater than 155

tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis

co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi

gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c1310-k9w7-tar.124-

10b.JDA2.tar: prefix is greater than 155

tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis

co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi

gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c2800nm-advsecurity

k9-mz.124-22.T1.bin: prefix is greater than 155

tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis

co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi

gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c3560-ipbase-mz.122

-53.SE2.bin: prefix is greater than 155

tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis

co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi

gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c7600-fpd-pkg.122-3

3.SRE1.pkg: prefix is greater than 155

tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis

co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi

gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c7600s72033-advente

rprisek9-mz.122-33.SRE1.bin: file name too long

tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis

co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/20100922075

156561-10.181.252.1.cfg: No such file or directory

ERROR(704): Cannot create or back up tar file. Backup cancelled. Verify that you

have write-access to this directory.

Backup failed: 2010/09/22 07:54:20

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

okcwsi:

I've tried this multiple times and each time it appears to fail on a different file/folder in the sw_images directory. This is our FTP directory where we store lots of IOS images for download. I've removed each of these files it errors out on and it keeps failing. I just removed all files from the sw_images folder and am trying the backup again now.

I'm attaching the backup.log which contains the failure information for each backup I've tried in the past two days.

My main question is...can I skip this backup somehow? I've got another LMS 3.0 system that I can export everything I need from. Skipping the backup isn't an option on the install/upgrade? It gives me the option to quit the install or try the backup again.

Thanks,

Attachment: 
Correct Answer by yjdabear about 6 years 7 months ago

        You can skip the backup with a hidden option:


./setup.sh -b nobackup


However, I wouldn't feel comfortable until figuring out why the backup has been failing, ostensibly because tar is running into the 255-char limit (100 for the filename and 155 for the path), a result of the many iterations of the following:


sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
yjdabear Wed, 09/22/2010 - 12:35
User Badges:
  • Gold, 750 points or more

        You can skip the backup with a hidden option:


./setup.sh -b nobackup


However, I wouldn't feel comfortable until figuring out why the backup has been failing, ostensibly because tar is running into the 255-char limit (100 for the filename and 155 for the path), a result of the many iterations of the following:


sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/

Actions

This Discussion