ADSM-L

Re: adsm errors...

1999-03-25 08:50:25
Subject: Re: adsm errors...
From: "Bijma, F" <fbijma AT AEGON DOT NL>
Date: Thu, 25 Mar 1999 14:50:25 +0100
Daniel,

If you define Shared Dynamic copy serialization in your Backup Copy
group

you get the following:

Select Shared dynamic to specify that the server attempts to back up a
file if it is being modified.  The file is committed to the server
during its last retry even if the file is being modified during the
backup process.

Default:  Shared static

Regards Frans Bijma

Solution 6000 BV


> -----Original Message-----
> From: Daniel Casey [mailto:jistdc1 AT MAIL.JBHUNT DOT COM]
> Sent: Wednesday, March 24, 1999 6:26 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: adsm errors...
>
>
> Client = aix421 with adsm 3.1.0.6
>
> Get the following near the end of the schedule.log:
>
>     03/24/99   00:18:25 Successful incremental backup of '/usr/local'
>     03/24/99   00:18:25 Incremental backup of volume 'RISC_DOMAIN'
> --> 03/24/99   00:18:25 ANS1076E *** Directory path not found ***
>     03/24/99   00:18:25 --- SCHEDULEREC OBJECT END RISC_SERVERS_WED
> 03/24/99   00:15
>     :00
>     03/24/99   00:18:25 --- SCHEDULEREC STATUS BEGIN RISC_SERVERS_WED
> 03/24/99   00:
>     15:00
>     03/24/99   00:18:25 Total number of objects inspected:   33,909
>     03/24/99   00:18:25 Total number of objects backed up:      139
>     03/24/99   00:18:25 Total number of objects updated:          0
>     03/24/99   00:18:25 Total number of objects rebound:          0
>     03/24/99   00:18:25 Total number of objects deleted:         26
>     03/24/99   00:18:25 Total number of objects failed:           2
>     03/24/99   00:18:25 Total number of bytes transferred:    28.06 MB
>     03/24/99   00:18:25 Data transfer time:
> 108.04 sec
>     03/24/99   00:18:25 Network data transfer rate:
> 266.00 KB/sec
>     03/24/99   00:18:25 Aggregate data transfer rate:
> 141.72 KB/sec
>     03/24/99   00:18:25 Objects compressed by:                    0%
>     03/24/99   00:18:25 Elapsed processing time:           00:03:22
>     03/24/99   00:18:25 --- SCHEDULEREC STATUS END RISC_SERVERS_WED
> 03/24/99   00:15
>     :00
> --> 03/24/99   00:18:25 ANS1512E Scheduled event
> 'RISC_SERVERS_WED' failed.
>   Return
> --> code = 4.
>     03/24/99   00:18:25 Sending results for scheduled event
> 'RISC_SERVERS_WED'.
>     03/24/99   00:18:25 Results sent to server for scheduled event
> 'RISC_SERVERS_WED
>     '.
>
> I read an APAR (IX83753) that said the rc=4 is normal when
> you have a file
> that
> didn't get backed up.  Well, the file that didn't get backed up was
> schedule.log
> because it was changing (duh?).  So, to prevent this, do I
> need to exclude
> this
> file from being backed up (inclexcl.def)?  Any other suggestions?
>
<Prev in Thread] Current Thread [Next in Thread>