ADSM-L

[no subject]

2015-10-04 17:33:42
Yes.  It is a NT permission problem.  When I remote access the =
filespace
through ADSM web client I got access deny error. Thanks for quick
responding.

I have an ADSM performance question.  It takes more than 11 hours for =
ADSM
to backup one of our big NT file/printer server.  There are about 4 =
millions
objects on this server. One filespace has 60 GB data and it takes 2 =
hours to
backup.  The another filespace has 125 GB data and it takes 9 hours to
backup.  Everyday normally only 2-3 GB data are transferred and backed =
up.
Look like the most of time are spent on file comparing.  I'd like to =
know if
it is normal for ADSM backup.  I also have a local DLT tape drive =
running
incremental backup using BackupExec.  It only takes 3 hours.  The =
following
is a summary of performance data.  ADSM server version is 3.1.2.40 and
client is 3.1.0.7.

Date/Time                Message
--------------------
----------------------------------------------------------
----------------------------------------------------------
01/28/2000 06:51:07      ANE4952I (Session: 4258, Node: CRRY0F03)  =
01/28/2000 06:51:07      ANE4952I (Session: 4258, Node: CRRY0F03)  =
Total
number of
                          objects inspected: 3,992,440
01/28/2000 06:51:07      ANE4954I (Session: 4258, Node: CRRY0F03)  =
Total
number of
                          objects backed up:    4,220
01/28/2000 06:51:07      ANE4958I (Session: 4258, Node: CRRY0F03)  =
Total
number of
                          objects updated:        159
01/28/2000 06:51:07      ANE4960I (Session: 4258, Node: CRRY0F03)  =
Total
number of
                          objects rebound:          0
01/28/2000 06:51:07      ANE4957I (Session: 4258, Node: CRRY0F03)  =
Total
number of
                          objects deleted:        467
01/28/2000 06:51:07      ANE4959I (Session: 4258, Node: CRRY0F03)  =
Total
number of
                          objects failed:          59
01/28/2000 06:51:07      ANE4961I (Session: 4258, Node: CRRY0F03)  =
Total
number of
                          bytes transferred:     1.24 GB
01/28/2000 06:51:07      ANE4963I (Session: 4258, Node: CRRY0F03)  Data
transfer
                          time:                   74.78 sec
01/28/2000 06:51:07      ANE4966I (Session: 4258, Node: CRRY0F03)  =
Network
data
                          transfer rate:        17,432.23 KB/sec
01/28/2000 06:51:07      ANE4967I (Session: 4258, Node: CRRY0F03)  =
Aggregate
data
                          transfer rate:         33.38 KB/sec
01/28/2000 06:51:07      ANE4968I (Session: 4258, Node: CRRY0F03)  =
Objects
                          compressed by:                    0%
01/28/2000 06:51:07      ANE4964I (Session: 4258, Node: CRRY0F03)  =
Elapsed
                          processing time:            10:50:52
01/28/2000 06:51:07      ANR0403I Session 4258 ended for node CRRY0F03
(WinNT).


Thanks!

Jialin Wu


> ----------
> From:         Kelly Lipp[SMTP:lipp AT STORSOL DOT COM]
> Reply To:     lipp AT storsol DOT com
> Sent:         Thursday, January 27, 2000 12:29 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: One Filespace Can't be Backed Up
>
> Probably an NT permissions thing.
>
> Kelly J. Lipp
> Storage Solutions Specialists, Inc.
> PO Box 51313
> Colorado Springs CO 80919
> (719)531-5926
> Fax: (719)260-5991
> www.storsol.com
> lipp AT storsol DOT com
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf =
Of
> Wu, Jialin
> Sent: Thursday, January 27, 2000 8:20 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: One Filespace Can't be Backed Up
>
>
> One of four filespaces of a NT server can't be backed up since Jan. =
4.  It
> was working before.  Other filespaces backups are fine.  Is there =
anyone
> who
> has experienced the similar problem?  Thanks.
>
> Jialin
>
<Prev in Thread] Current Thread [Next in Thread>
  • [no subject], Unknown <=