fbackup sceduled w/ sam - multiple tapes ... no timeout

[Omar Alvi_1]

Hi,

Basically this is what we want to accomplish

We're having scheduled backups using sam. However, the backup will need more than one tape.

Now, I want the backup to prompt me for my second tape, and not timeout.

I've used the chgvol option but it timesout in 3 hours ... also the prompt shouldn't be released by "just any key".

Presntly, I get the following errors.

Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=baan))
The command completed successfully
oracle listener stopped
fbackup(1004): session begins on Tue Mar 15 00:06:10 2005
fbackup(3203): volume 1 has been used 9 time(s)
fbackup(3024): writing volume 1 to the output file /dev/rmt/1m
1: / 6
2: /app 8
3: /app/oradata 8
4: /app/oradata/baandatpace01.dbf 2048016
5: /app/oradata/baandatpace02.dbf 4096016
6: /app/oradata/baanidxspace02.dbf 1638416
7: /app/oradata/dat204space01.dbf 409616
8: /app/oradata/dat420space03.dbf 2048016
9: /app/oradata/dat552space02.dbf 614416
10: /app/oradata/idx200space14.dbf 1024016
11: /app/oradata/idx201space.dbf 1024016
12: /app/oradata/idx202space.dbf 3072016
13: /app/oradata/idx202space01.dbf 2048016
14: /app/oradata/idx203space.dbf 1024016
15: /app/oradata/idx204space01.dbf 102416
16: /app/oradata/idx420space03.dbf 1024016
17: /app/oradata/idx552space02.dbf 1024016
18: /app/oradata/idx552space03.dbf 1024016
19: /arc1 1
20: /arc1/oradata 8
21: /arc1/oradata/IDX552SPACE01.dbf 1024016
22: /arc1/oradata/baanrbs01.dbf 1024016
23: /arc1/oradata/baanrbs02.dbf 1024016
24: /arc1/oradata/baanrbs03.dbf 204816
25: /arc1/oradata/baantemp01.dbf 102416
26: /arc1/oradata/brb02.dbf 1024016
27: /arc1/oradata/brbs.dbf 307216
28: /arc1/oradata/dat200space03.dbf 5324816
29: /arc1/oradata/dat200space11.dbf 4096016
30: /arc1/oradata/dat200space12.dbf 3072016
31: /arc1/oradata/dat420space02.dbf 4096016
32: /arc1/oradata/idx200space06.dbf 4096016
33: /arc1/oradata/idx200space09.dbf 2048016
34: /arc1/oradata/idx200space10.dbf 4096016
35: /arc1/oradata/idx200space16.dbf 1024016
36: /arc1/oradata/idx201space.dbf 1228816
37: /arc1/oradata/idx420space04.dbf 614416
38: /arc1/oradata/user_01.dbf 102416
39: /ora1 8
40: /ora1/oradata 8
41: /ora1/oradata/baandatpace03.dbf 1474736
42: /ora1/oradata/baantemp02.dbf 9379856
43: /ora1/oradata/contbaan801.ctl 2416
44: /ora1/oradata/dat200space02.dbf 4096016
45: /ora1/oradata/dat200space04.dbf 2048016
46: /ora1/oradata/dat200space05.dbf 2048016
47: /ora1/oradata/dat200space06.dbf 4096016
48: /ora1/oradata/dat200space07.dbf 2048016
49: /ora1/oradata/idx200space13.dbf 2048016
50: /ora1/oradata/idx202space02.dbf 2048016
51: /ora1/oradata/logbaan01.dbf 409602
52: /ora1/oradata/sysbaan01.dbf 2478096
53: /ora1/oradata/sysbaan02.dbf 702128
54: /ora2 1
55: /ora2/oradata 8
56: /ora2/oradata/DAT552SPACE01.dbf 1024016
57: /ora2/oradata/baanidxspace01.dbf 2097168
58: /ora2/oradata/contbaan802.ctl 2416
59: /ora2/oradata/dat420space01.dbf 4096016
60: /ora2/oradata/idx200space04.dbf 12984336
61: /ora2/oradata/idx200space05.dbf 4096016
62: /ora2/oradata/idx420space01.dbf 4096016
63: /ora2/oradata/idx420space02.dbf 4096016
64: /ora2/oradata/logbaan02.dbf 409602
65: /ora3 1
66: /ora3/oradata 8
67: /ora3/oradata/contbaan803.ctl 2416
68: /ora3/oradata/idx200space01.dbf 10240016
69: /ora3/oradata/idx200space02.dbf 5120016
70: /ora3/oradata/idx200space03.dbf 7372816
71: /ora3/oradata/idx200space07.dbf 5120016
72: /ora3/oradata/idx200space11.dbf 4096016
73: /ora3/oradata/logbaan03.dbf 409602
74: /ora4 1
75: /ora4/oradata 8
76: /ora4/oradata/dat200space01.dbf 10649616
77: /ora4/oradata/dat200space08.dbf 3686416
78: /ora4/oradata/dat200space09.dbf 2048016
79: /ora4/oradata/dat200space10.dbf 4096016
80: /ora4/oradata/dat201space01.dbf 1024016
81: /ora4/oradata/dat201space03.dbf 1024016
82: /ora4/oradata/dat202space01.dbf 2048016
83: /ora4/oradata/dat202space02.dbf 2048016
84: /ora4/oradata/dat202space03.dbf 1024016
85: /ora4/oradata/dat203space01.dbf 2048016
86: /ora4/oradata/idx200space12.dbf 4096016
87: /ora5 8
88: /ora5/oradata 8
89: /ora5/oradata/baandatpace04.dbf 1024016
90: /ora5/oradata/baanidxspace03.dbf 1024016
91: /ora5/oradata/dat200space13.dbf 4096016
92: /ora5/oradata/dat200space14.dbf 2048016
93: /ora5/oradata/dat200space15.dbf 2048016
94: /ora5/oradata/dat200space16.dbf 2048016
95: /ora5/oradata/dat200space17.dbf 2048016
96: /ora5/oradata/dat201space02.dbf 614416
97: /ora5/oradata/dat552space03.dbf 1024016
98: /ora5/oradata/dat552space04.dbf 1024016
99: /ora5/oradata/idx200space08.dbf 2097168
100: /ora5/oradata/idx200space15.dbf 4096016
101: /ora5/oradata/idx200space17.dbf 1024016
102: /ora5/oradata/idx200space18.dbf 2048016
103: /ora5/oradata/idx200space19.dbf 2048016
104: /ora5/oradata/idx201space03.dbf 1024016
105: /ora5/oradata/idx202space03.dbf 2048016
106: /ora5/oradata/idx203space01.dbf 1433616
107: /ora5/oradata/logbaan04.dbd f 409602
108: /ora6 8
109: /ora6/oradata 8
110: /ora6/oradata/dat200space18.dbf 6144016
111: /ora6/oradata/dat200space19.dbf 6144016
112: /ora6/oradata/dat202space04.dbf 3072016
113: /ora6/oradata/idx200space20.dbf 6144016
114: /ora6/oradata/idx200space21.dbf 6144016
115: /ora6/oradata/idx201space04.dbf 1024016
116: /ora6/oradata/idx202space04.dbf 2048016
117: /ora6/oradata/idx202space05.dbf 2048016
118: /ora7 8
119: /ora7/oradata 8
120: /ora7/oradata/dat200space20.dbf 6144016
121: /ora7/oradata/dat200space21.dbf 6144016
122: /ora7/oradata/dat200space22.dbf 2457616
123: /ora7/oradata/idx200space22.dbf 6144016
124: /ora7/oradata/idx200space23.dbf 5120016
fbackup(3003): normal EOT
fbackup(3310): enter '^[yY]' when volume 2 is ready on /dev/rmt/1m,
or '^[nN]' to discontinue:
fbackup(3004): writer aborting
fbackup(1002): Backup did not complete : Reader or Writer process exit
running oracle start script....
ttytype: couldn't open /dev/tty for reading
stty: : Not a typewriter

Thanks and Regards,

-Alvi

[Steven E. Protter]

I would suggest the backup call a script that invokes fbackup from the command line. Make sure that script sets environment variables to write to say the console.

The error message clearly shows that TERM and other basic environment variables are not set. The script needs to make up for this. Doing it with SAM apparently doesn't give it anywhere to write that "new tape please" prompt.

Also consider: Its downing an Oracle database, or at least impacting it. How long do you want it to sit in limbo?

SEP

[Leif Halvarsson_2]

Hi,
Scheduled using SAM ? I belive SAM uses cron for scheduling and cron jobs is not interactive.

I would recommend you to have a look at a "real" backup application, for example Data Protector.

[Omar Alvi_1]

Thanks for your replies,

If I use a script I can make fbackup interactive, right ... is chgvol the only option, and what are its limitations?

But if cron or at are not interactive, then I can't have a scheduled backup using my script.

Main issue is the need to have it interactive, as wrell as for it not to timeout even if it waits the entire weekend.

Any other workarounds, or is it simply not supported?

Thanks and Regards,

-Alvi