Forum Discussion

Andy_Cam's avatar
Andy_Cam
Level 3
11 years ago

5220 Appliance NetBackup Processes Stop at the Weekend

Hi, I have a NetBackup 5220 Appliance on 2.5.4 acting as a Media Server.

Every weekend the Netbackup processes get stopped and I have to start them up again on Monday.

The only clue I have found so far is in the SCSP Audit Logs found on the Appliance web page. Would this be the likely reason for the processes getiing stopped? And how do I reeconfigure SCSP to prevent it happening again. I checked the SCSP admin guides found here but there's nothig obvious...

http://www.symantec.com/business/support/index?page=content&id=DOC2218&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1400246509428cth13Yi2BB7HyEe8F8zAHN2AUAhu39H16S6jC

 

SCSP Audit Logs

2014-05-11 11:19:50 BST Information IDS Status IA_0023: Symantec IDS Service has started
2014-05-11 11:19:50 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/passwd".
2014-05-11 11:19:50 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/group".
2014-05-11 11:19:50 BST Warning IDS Error FWC_0018: Invalid path(s) will not be monitored: /opt/NBUAppliance/scripts/*/* Blank Value
2014-05-11 11:19:51 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/shadow".
2014-05-11 11:19:51 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/gshadow".
2014-05-11 11:19:52 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/user_attr".
2014-05-11 11:19:52 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/security/passwd".
2014-05-11 11:19:52 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/security/user".
2014-05-11 11:19:52 BST Information IDS Status PE_0110: Execute command called: "/opt/Symantec/scspagent/IDS/bin/user_monitor.sh /etc/security/group".
2014-05-11 11:19:55 BST Notice SysLog successful SU to another user Event source: SYSLOG [auth facility] To Username: sisips Port: none Complete message: May 11 11:19:55 xxxxxxmds002bk su: (to sisips) root on none
2014-05-11 11:20:00 BST Notice SysLog successful SU to another user Event source: SYSLOG [auth facility] To Username: sisips Port: none Complete message: May 11 11:20:00 xxxxxxmds002bk su: (to sisips) root on none
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (103 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/client_configure.pl
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (121 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/nbapp_client.pm
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (114 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/nbapp_nbutils.pm
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (179 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/nbapp_storage.pm
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (145 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/nbcplogs.pl
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (118 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/nbu_sf.pm
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (119 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/patch.pl
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (124 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/util.pm
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (3007 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/Intel_RAID_1.41.372-2527_Installer.pl
2014-05-11 11:20:02 BST Warning IDS Error FWC_0023: File too big to perform diff (3005 Kb < 100 Kb limit): /opt/NBUAppliance/scripts/LSI_RAID_1.40.342-1650_Installer.pl
2014-05-11 11:20:14 BST Warning File Watch Unix Watched File Modified (/etc/sysctl.conf)
2014-05-11 11:19:55 BST Information Agent Status Starting Symantec Critical System Protection Service 5.2.8.164
2014-05-11 11:19:55 BST Notice Agent Status Management Server URL : https://127.0.0.1:443/sis-agent/
2014-05-11 11:19:58 BST Warning Common Status

Curl Error: Verify the agent certificate matches the server..
Agents
Backup and Recovery
NetBackup Appliance
Not Applicable
  • Andy_Cam's avatar
    Andy_Cam
    10 years ago

    After sending endless logs to Symantec they had an engineer sent to site and replaced the Appliance chasi.

    This then fixed the problem.

9 Replies

Sort By
  • D_Flood's avatar
    D_Flood
    Level 6
    11 years ago

    It looks like SCP is doing exactly what it's designed for.  Detecting an (to it) unauthorized change.  In this case it's a bad certificate.

    I'd highly suggest opening a ticket with Symantec so they can take a look at what has changed and why.

     

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    I have never seen this sort of thing stop an appliance working - but would be interested in your findings..

    Having said that lets start with NetBackup, just in case - could we see an All Log Entries report for a period over the weekend from when it was working until it was no longer working

    The spad, storaged and spoold logs would be handy too

    Thanks

  • Andy_Cam's avatar
    Andy_Cam
    Level 3
    11 years ago

    From All Log Entries, everything seems to be running along as normal until I get this line...

    5/18/2014 1:47:48 AM xxxxxxmds002bk   Warning 0 512

    Server xxxxxxmds002bk's disk active state set to DOWN

     Spad.log....

    May 18 01:41:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:42:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:42:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:43:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:43:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:43:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:44:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:44:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:45:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
    May 18 01:45:31 INFO [1094347072]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 1
     

     

     

    Storaged.log....

    May 17 12:20:03 INFO [1080080704]: Time required to build index on objects2 table: 0.001228
    May 17 12:20:03 INFO [1080080704]: Time required to drop objects table: 0.010207
    May 17 12:20:03 INFO [1080080704]: Time required to rename objects2 table to objects: 0.003866
    May 17 12:20:03 INFO [1080080704]: Transaction log 880-880 Completed. Expect: 1 (0.00MB) Commit: 1 (0.00MB) Retry: 0 Log: from /disk/queue/partsorted-880-880-0.tlog to /disk/queue/partsorted-880-880-5.tlog SO: Add 0, Ref Add 0, Ref Add Fail: 0, Ref Del 0 DO: Add 0, Ref Add 0, Ref Add Fail: 0, Ref Del 0 TASK: Add 0, End 0, End All 0, Del 1 DCID: SO 0, SO Fail 0, DO 0, DO Fail 0 MARKER: 0, Fail 0
    May 17 12:20:03 INFO [1080080704]: Update last committed tlogid from 879 to 880
    May 17 12:20:04 INFO [1080080704]: Start processing delayed operations of '/disk/queue/sorted-880-880.delayed'.
    May 17 12:20:04 INFO [1080080704]: Completed processing of 0 delayed operations of '/disk/queue/sorted-880-880.delayed'.
    May 18 00:20:03 INFO [1080080704]: Queue processing triggered by external request.
    May 18 00:20:03 INFO [1080080704]: WSRequestExt: submitting &request=5&login=agent_3_236532&passwd=********************************&action=setCRDelay&id=1&delay=0
     

    Spoold.log....

    May 18 01:43:08 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:43:10 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:43:12 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:43:14 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:43:16 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:43:18 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:43:20 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:43:22 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:43:24 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:43:26 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:43:28 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:43:30 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:43:31 INFO [1080609088]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 2
    May 18 01:43:31 INFO [1080609088]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent crstats requesting access for DataSelection ID 1
    May 18 01:43:32 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:43:34 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:43:36 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:43:38 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:43:40 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:43:42 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:43:44 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:43:46 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:43:48 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:43:50 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:43:52 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:43:54 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:43:56 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:43:58 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:44:00 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:44:02 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:44:04 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:44:06 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:44:08 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:44:10 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:44:12 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:44:14 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:44:16 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:44:18 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:44:20 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:44:22 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:44:24 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:44:26 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:44:28 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:44:30 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:44:31 INFO [1080609088]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 2
    May 18 01:44:31 INFO [1080609088]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent crstats requesting access for DataSelection ID 1
    May 18 01:44:32 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:44:34 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:44:36 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:44:38 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:44:40 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:44:42 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:44:44 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:44:46 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:44:48 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:44:50 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:44:52 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:44:54 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:44:56 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:44:58 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:45:00 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:45:02 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:45:04 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:45:06 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:45:08 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:45:10 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:45:12 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:45:14 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:45:16 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:45:18 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:45:20 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:45:22 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:45:24 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:45:26 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:45:28 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:45:30 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:45:31 INFO [1080609088]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent bpstsinfo requesting access for DataSelection ID 2
    May 18 01:45:31 INFO [1080609088]: Remote is using libcr Version 7.0006.0013.112, Protocol Version 6.6.1 running on Linux-x86_64. Agent crstats requesting access for DataSelection ID 1
    May 18 01:45:32 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:45:34 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:45:36 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:45:38 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:45:40 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:45:42 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:45:44 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:45:46 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:45:48 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:45:50 INFO [1079023936]: CRC verify for data container(68) succeeded.
    May 18 01:45:52 INFO [1079023936]: CRC verify for data container(69) succeeded.
    May 18 01:45:54 INFO [1079023936]: CRC verify for data container(70) succeeded.
    May 18 01:45:56 INFO [1079023936]: CRC verify for data container(71) succeeded.
    May 18 01:45:58 INFO [1079023936]: CRC verify for data container(64) succeeded.
    May 18 01:46:00 INFO [1079023936]: CRC verify for data container(65) succeeded.
    May 18 01:46:02 INFO [1079023936]: CRC verify for data container(66) succeeded.
    May 18 01:46:04 INFO [1079023936]: CRC verify for data container(67) succeeded.
    May 18 01:46:06 INFO [1079023936]: CRC verify for data container(68) succeeded.

     

     

     

     

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    OK - not too much there to work on but interesting that you say it goes down every weekend

    So last night it shows it went down at 01:47 - how busy would the appliance have been at about that time?

    Just wondering of it is caused by being overloaded or by queue processing / compaction / rebasing that could be running.

    What is the process queue size at the moment? (crcontrol --queueinfo)

    What is the rebase state (crcontrol --rebasestate)

    Finally for now .. what is its de-dupe stats : crcontrol --dsstat

    Do you have any DSP* files on the master or appliance under /usr/openv/netbackup/db/config/

    if so what are they and what values do they contain

    Thanks

  • Andy_Cam's avatar
    Andy_Cam
    Level 3
    11 years ago

    This media server, the master server and the other two media servers get very little use so I doubt the problem is due to getting over loaded.

    Here's the info toy asked for...

    xxxxxxmds002bk:/usr/openv/pdde/pdcr/bin # ./crcontrol --queueinfo
    total queue size : 0
    xxxxxxmds002bk:/usr/openv/pdde/pdcr/bin # ./crcontrol --rebasestate
    Image rebasing: ON
    Rebasing busy: No
    xxxxxxmds002bk:/usr/openv/pdde/pdcr/bin # ./crcontrol --dsstat

    ************ Data Store statistics ************
    Data storage      Raw    Size   Used   Avail  Use%
                       4.0T   3.8T  32.9G   3.8T   1%

    Number of containers             : 8
    Average container size           : 3969 bytes (0.00MB)
    Space allocated for containers   : 31755 bytes (0.03MB)
    Space used within containers     : 31755 bytes (0.03MB)
    Space available within containers: 0 bytes (0.00MB)
    Space needs compaction           : 31590 bytes (0.03MB)
    Reserved space                   : 175921954816 bytes (163.84GB)
    Reserved space percentage        : 4.0%
    Records marked for compaction    : 150
    Active records                   : 2
    Total records                    : 152

    Use "--dsstat 1" to get more accurate statistics

     


    xxxxxxmds002bk:/usr/openv/netbackup/db/config # ls -l
    total 24
    lrwxrwxrwx 1 root root  45 Jun 11  2012 DEFERRED_IMAGE_LIMIT -> /opt/NBUAppliance/config/DEFERRED_IMAGE_LIMIT
    lrwxrwxrwx 1 root root  48 Jun 11  2012 DPS_PROXYDEFAULTRECVTMO -> /opt/NBUAppliance/config/DPS_PROXYDEFAULTRECVTMO
    lrwxrwxrwx 1 root root  45 Jun 11  2012 LIFECYCLE_PARAMETERS -> /opt/NBUAppliance/config/LIFECYCLE_PARAMETERS
    -rw-r--r-- 1 root root   3 Dec  2  2012 NUMBER_DATA_BUFFERS
    -rw-r--r-- 1 root root   3 Dec  2  2012 NUMBER_DATA_BUFFERS_DISK
    -rw-r--r-- 1 root root 341 Mar  6 11:54 behavior
    drwxr-xr-x 2 root root  96 Apr 11 11:09 shm


    xxxxxxmds002bk:/usr/openv/netbackup/db/config # cat DPS_PROXYDEFAULTRECVTMO
    800

    I have also found it's not just the processes stopping, the 5220 is actually rebooting and not starting the processes after the reboot. I just need to find out why it's rebooting.....

    xxxxxxmds002bk:/home/maintenance # last
    admin    pts/0        xxxxxxxxx30.uk1 Tue May 20 14:37   still logged in
    admin    pts/0        xxxxxxxxx30.uk1 Tue May 20 14:36 - 14:37  (00:00)
    admin    pts/0        xxxxxxxxx30.uk1 Tue May 20 10:28 - 11:06  (00:38)
    admin    pts/0        xxxxxxxxx30.uk1 Tue May 20 10:02 - 10:25  (00:22)
    admin    pts/0        xxxxxxxxx30.uk1 Mon May 19 10:50 - 12:54  (02:04)
    reboot   system boot  2.6.16.60-0.103. Sun May 18 01:49         (2+12:49)
    admin    pts/0        xxxxxxxxx30.uk1 Fri May 16 14:53 - 15:59  (01:05)
    admin    pts/0        xxxxxxxxx30.uk1 Fri May 16 09:35 - 13:33  (03:57)
    reboot   system boot  2.6.16.60-0.103. Thu May 15 17:03         (4+21:34)
    admin    pts/0        xxxxxxxxx30.uk1 Thu May 15 09:59 - 10:22  (00:22)
    admin    pts/0        xxxxxxxxx30.uk1 Wed May 14 14:55 - 14:56  (00:00)
    admin    pts/0        xxxxxxxxx30.uk1 Tue May 13 15:28 - 15:51  (00:22)
    admin    pts/0        xxxxxxxxx30.uk1 Mon May 12 13:44 - 14:18  (00:34)
    reboot   system boot  2.6.16.60-0.103. Sun May 11 11:21         (9+03:16)
    admin    pts/0        xxxxxxxxx30.uk1 Wed May  7 10:26 - 10:59  (00:32)
    reboot   system boot  2.6.16.60-0.103. Wed May  7 03:06         (13+11:31)
    reboot   system boot  2.6.16.60-0.103. Fri May  2 14:15         (18+00:22)
    admin    pts/0        xxxxxxxxx30.uk1 Tue Apr 29 10:02 - 10:39  (00:36)
    reboot   system boot  2.6.16.60-0.103. Mon Apr 28 07:10         (22+07:27)
    reboot   system boot  2.6.16.60-0.103. Thu Apr 24 02:43         (26+11:54)
    wtmp begins Thu Apr 24 02:43:41 2014

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    WOW!! I have never seen an appliance that has a queue size of zero apart from a brand new one ...

    I know you say it gets very little use but the dsstat of that one shows that it is totally empty

    If that should not be the case then you really do have issues and the rebooting is the least of it

    If you havent already logged a call then do so as there looks to be no images or de-dupe on that appliance at all.

  • Andy_Cam's avatar
    Andy_Cam
    Level 3
    11 years ago

    Thanks Mark,

    I do have a case open already with Symantec for this but having sent logs etc. over the last week, we've not got to the bottom of the problem yet.

    I'll let you know how it goes.

  • Mark_Solutions's avatar
    Mark_Solutions
    Level 6
    11 years ago

    OK - would you expect that appliance to be totally empty of any backup images?

    What does the Images on disk report say for that appliances disk pool?

  • Andy_Cam's avatar
    Andy_Cam
    Level 3
    10 years ago

    After sending endless logs to Symantec they had an engineer sent to site and replaced the Appliance chasi.

    This then fixed the problem.