Regardless of the autoloader..you still must specify number of tapes per 
a backup...if the config resticts you to use 1 tape then so be it......I 
believe that if you specify two tapes  in your config file and it only 
takes up one (depending if you are using hardware compression ) then the 
next tape would be loaded at he next invocation of a backup.

Juanjo wrote:

> Hello,
>
> Seems that only 4 out of 6 dumps are backed up. Two of them are 
> skipped giving error message: dumps too big....
>
> What I see is that it starts estimating sizes of every disk, therefore 
> total size exceeds single tape size, but I'm using an autoloader, so 
> It should jump on to a new tape, shouldnt it? And send there the disks 
> that didnt fit on that prior tape. How?
>
> Here I paste a piece of amdump.log:
>
> 
>-----------------------------------------------------------------------------------------------------------------------------------------------------
> 
>
> got result for host srvc disk /data1: 0 -> 32149300K, -1 -> -1K, -1 -> 
> -1K
> got result for host srvc disk /data0: 0 -> 20482410K, -1 -> -1K, -1 -> 
> -1K
> got result for host srvb disk /data1: 0 -> 35674680K, -1 -> -1K, -1 -> 
> -1K
> got result for host srvb disk /data0: 0 -> 21510210K, -1 -> -1K, -1 -> 
> -1K
> getting estimates took 266.671 secs
> FAILED QUEUE: empty
> DONE QUEUE:
>  0: srva       /data1
>  1: srva       /data0
>  2: srvc       /data1
>  3: srvc       /data0
>  4: srvb       /data1
>  5: srvb       /data0
>
> ANALYZING ESTIMATES...
> pondering srva:/data1... next_level0 -11737 last_level -1 (due for 
> level 0) (new disk, can't switch to degraded mode)
>  curr level 0 size 27650 total size 27770 total_lev0 27650 
> balanced-lev0size 4608
> pondering srva:/data0... next_level0 -11737 last_level -1 (due for 
> level 0) (new disk, can't switch to degraded mode)
>  curr level 0 size 423860 total size 451670 total_lev0 451510 
> balanced-lev0size 75251
> pondering srvc:/data1... next_level0 -11737 last_level -1 (due for 
> level 0) (new disk, can't switch to degraded mode)
>  curr level 0 size 32149300 total size 32601010 total_lev0 32600810 
> balanced-lev0size 5433467
> pondering srvc:/data0... next_level0 -11737 last_level -1 (due for 
> level 0) (new disk, can't switch to degraded mode)
>  curr level 0 size 20482410 total size 53083460 total_lev0 53083220 
> balanced-lev0size 8847202
> pondering srvb:/data1... next_level0 -11737 last_level -1 (due for 
> level 0) (new disk, can't switch to degraded mode)
>  curr level 0 size 35674680 total size 88758180 total_lev0 88757900 
> balanced-lev0size 14792982
> pondering srvb:/data0... next_level0 -11737 last_level -1 (due for 
> level 0) (new disk, can't switch to degraded mode)
>  curr level 0 size 21510210 total size 110268430 total_lev0 110268110 
> balanced-lev0size 18378017
> INITIAL SCHEDULE (size 110268430):
>  srvb /data1 pri 11738 lev 0 size 35674680
>  srvc /data1 pri 11738 lev 0 size 32149300
>  srvb /data0 pri 11738 lev 0 size 21510210
>  srvc /data0 pri 11738 lev 0 size 20482410
>  srva /data0 pri 11738 lev 0 size 423860  srva /data1 pri 11738 lev 0 
> size 27650 
> DELAYING DUMPS IF NEEDED, total_size 110268430, tape length 71680000 
> mark 8
> planner: FAILED srvc /data0 0 [dumps too big, but cannot incremental 
> dump new disk]
> planner: FAILED srvb /data0 0 [dumps too big, but cannot incremental 
> dump new disk]
>  delay: Total size now 68275730.
>
> PROMOTING DUMPS IF NEEDED, total_lev0 68275490, balanced_size 18378017...
> analysis took 0.000 secs
>
> GENERATING SCHEDULE:
> --------
> srvb /data1 11738 0 1970:1:1:0:0:0 35674680 1189156
> srvc /data1 11738 0 1970:1:1:0:0:0 32149300 1071643
> srva /data0 11738 0 1970:1:1:0:0:0 423860 14128
> srva /data1 11738 0 1970:1:1:0:0:0 27650 921  
> 
>-----------------------------------------------------------------------------------------------------------------------------------------------------------------
> 
>
>
> Tape size is DLT1 40/80 btw.
>
> Thanks.
>
>


Reply via email to