Printing, Personal Computing and Mobile BoardsHave Been Migrated to HP Support Forums

Open Menu

Printing, Personal Computing and Mobile BoardsHave Been Migrated to HP Support ForumsOpen Menu

We have completed the migration of all boards within the Printing and Digital Imaging, Desktops and Workstations, and Mobile categories to the HP Support Forums. Please see this post for full details on the migration, and how to get to your content.

I checked with my Database and application team they all are saying these files are not related to them. Also all the directory have root and sys access. Just need you expert optinions can I proceed to delete these files to have successfull Ignite backup.

I can take ignite backup excluding these files but just want to get rid of these directory and have a successfull ignite backup without any issue.

Appreciate you expert help on this.

Regards,

P.S. This thread has been moved from HP-UX > System Administration to HP-UX > ignite - HP Forums moderator

Re: Ignite backup not working

I am able to take ignite backup now but it is completing with the following WARNING:

WARNING: There was a problem with the list of files/directories to archive. Input: /var/opt/ignite/recovery/2013-02-04,WARNING: There was a problem with the list of files/directories to archive. Input: /var/opt/ignite/recovery/2013-02-04,13:07/flist The following line(s) had too few/incorrect entries in each of them. Problem lines: line: 14 tntabhome/dat 40777 1120047583 96 0

I tried to list /tntabhome/dat if any special or non printable character is there but couldn't find any.

Re: Ignite backup not working

Got one more server again on which ignite backup is failing since long time. Here also I find one directory in /.java named _!':!bw"t!#4!a!"w!#4!bw"2 . I tried to rename this directory as you suggested above but unable to do so. Is there any pattern to rename these types of directory?

Re: Ignite backup not working

Your command contains a total of 5 unescaped double quotes, so the shell is going to assume that you forgot to close one set of double quotes. The shell has no way of knowing that the double quotes within the first parameter are actually part of the parameter.