Solved: LMS 2.6 backup failure

yjdabear · ‎11-11-2008

/var/adm/CSCOpx/files/rme/cri/archives

tar: /var/adm/CSCOpx/files/rme/jobs/ArchivePurge/1562/299/log: file changed size

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

have write-access to this directory.

Backup failed: 2008/11/11 03:20:17

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

The perms look fine to me:

ls -al /var/adm/CSCOpx/files/rme/jobs/ArchivePurge/1562/299/log

-rw-rw---- 1 casuser casusers 8900780 Nov 11 03:24 /var/adm/CSCOpx/files/rme/jobs/ArchivePurge/1562/299/log

ls -al /var/adm/CSCOpx/files/rme/jobs/ArchivePurge/1562/299

total 899678

drwxr-x--- 2 casuser casusers 1024 Nov 11 03:24 .

drwxrwx--- 15 casuser casusers 1024 Nov 11 01:30 ..

-rw-r----- 1 casuser casusers 8234 Nov 11 03:24 ResultSummary.obj

-rw-r----- 1 casuser casusers 17641 Nov 11 01:30 deviceList.obj

-rw-rw---- 1 casuser casusers 8900780 Nov 11 03:24 log

-rw-rw---- 1 casuser casusers 10240166 Nov 11 03:23 log.1

-rw-rw---- 1 casuser casusers 10240197 Nov 11 03:10 log.10

-rw-rw---- 1 casuser casusers 10240055 Nov 11 03:08 log.11

-rw-rw---- 1 casuser casusers 10240116 Nov 11 03:07 log.12

-rw-rw---- 1 casuser casusers 10240145 Nov 11 03:06 log.13

-rw-rw---- 1 casuser casusers 10240144 Nov 11 03:04 log.14

-rw-rw---- 1 casuser casusers 10240118 Nov 11 03:03 log.15

-rw-rw---- 1 casuser casusers 10240036 Nov 11 03:01 log.16

-rw-rw---- 1 casuser casusers 10240045 Nov 11 03:00 log.17

-rw-rw---- 1 casuser casusers 10240199 Nov 11 02:53 log.18

-rw-rw---- 1 casuser casusers 10240060 Nov 11 02:52 log.19

-rw-rw---- 1 casuser casusers 10240095 Nov 11 03:21 log.2

-rw-rw---- 1 casuser casusers 10240095 Nov 11 02:50 log.20

-rw-rw---- 1 casuser casusers 10240047 Nov 11 02:49 log.21

-rw-rw---- 1 casuser casusers 10240000 Nov 11 02:47 log.22

-rw-rw---- 1 casuser casusers 10240004 Nov 11 02:46 log.23

-rw-rw---- 1 casuser casusers 10240021 Nov 11 02:44 log.24

-rw-rw---- 1 casuser casusers 10240128 Nov 11 02:43 log.25

-rw-rw---- 1 casuser casusers 10240202 Nov 11 02:42 log.26

-rw-rw---- 1 casuser casusers 10240165 Nov 11 02:40 log.27

-rw-rw---- 1 casuser casusers 10240100 Nov 11 02:34 log.28

-rw-rw---- 1 casuser casusers 10240192 Nov 11 02:33 log.29

-rw-rw---- 1 casuser casusers 10240115 Nov 11 03:20 log.3

-rw-rw---- 1 casuser casusers 10240060 Nov 11 02:11 log.30

-rw-rw---- 1 casuser casusers 10240090 Nov 11 02:09 log.31

-rw-rw---- 1 casuser casusers 10240061 Nov 11 02:08 log.32

-rw-rw---- 1 casuser casusers 10240128 Nov 11 01:47 log.33

-rw-rw---- 1 casuser casusers 10240024 Nov 11 01:46 log.34

-rw-rw---- 1 casuser casusers 10240055 Nov 11 01:44 log.35

-rw-rw---- 1 casuser casusers 10240033 Nov 11 01:43 log.36

-rw-rw---- 1 casuser casusers 10240101 Nov 11 01:42 log.37

-rw-rw---- 1 casuser casusers 10240130 Nov 11 01:40 log.38

-rw-rw---- 1 casuser casusers 10240126 Nov 11 01:39 log.39

-rw-rw---- 1 casuser casusers 10240151 Nov 11 03:19 log.4

-rw-rw---- 1 casuser casusers 10240067 Nov 11 01:38 log.40

-rw-rw---- 1 casuser casusers 10240128 Nov 11 01:36 log.41

-rw-rw---- 1 casuser casusers 10240005 Nov 11 01:35 log.42

-rw-rw---- 1 casuser casusers 10240109 Nov 11 01:33 log.43

-rw-rw---- 1 casuser casusers 10240001 Nov 11 01:32 log.44

-rw-rw---- 1 casuser casusers 10240126 Nov 11 03:17 log.5

-rw-rw---- 1 casuser casusers 10240299 Nov 11 03:16 log.6

-rw-rw---- 1 casuser casusers 10240158 Nov 11 03:15 log.7

-rw-rw---- 1 casuser casusers 10240108 Nov 11 03:13 log.8

-rw-rw---- 1 casuser casusers 10240129 Nov 11 03:12 log.9

-rw-r----- 1 casuser casusers 329137 Nov 11 03:24 results.20081111032425.obj

-rw-r----- 1 casuser casusers 232675 Nov 11 03:24 results.20081111032425.txt

-rw-r----- 1 casuser casusers 421453 Nov 11 03:24 tempResults.obj

Joe Clarke · ‎11-11-2008

Your backup is running at the same time this job was running. Your choices to get around this are to either run the backup offline (by setting BACKUP_OFFLINE to YES in /opt/CSCOpx/conf/backup.properties), or to pick a different time for your purge job or backup. You can also minimize this race condition by making sure all debugging is disabled.

View solution in original post

Joe Clarke · ‎11-11-2008

Your backup is running at the same time this job was running. Your choices to get around this are to either run the backup offline (by setting BACKUP_OFFLINE to YES in /opt/CSCOpx/conf/backup.properties), or to pick a different time for your purge job or backup. You can also minimize this race condition by making sure all debugging is disabled.

yjdabear · ‎11-11-2008

I have the Archive Purge Job scheduled at 18:20. It must have been the debugging that caused it to drag on into the morning then.

Joe Clarke · ‎11-11-2008

That stands to reason as it was the log that was being updated.

yjdabear · ‎11-11-2008

Are there any caveats to enabling BACKUP_OFFLINE, i.e. why wouldn't everyone want to use that mode by default?

Joe Clarke · ‎11-11-2008

That option shuts down the LMS daemons before the backup begins. This will cause downtime which may be unacceptable. It can also trigger bug CSCsl98252 (for which you already have the fix).