![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Hello Malc, --> I know we can, using -w. I'm asking if the -f version allows the same, --> or can we only restore to the point where space 3 was backed up? --> Simple as that. No you can not. The onbar -b -w -L 0 does backup the content of your logical logs too simular as an ontape would do. So the restore can do a fast recovery after a physical restore. onbar -b -L 0 does not backup the content of your logs; (believe me i have been there you need your trx log to restore which means that you can not restore to the point in time the archive starts. this you can only do with an archive taken before and using trx logs.) |
|
You could try and tune a bit in *upping BAR_NB_XPORT_COUNT make sure BAR_XFER_BUF_SIZE is 31 make a not if you change BAR_XFER_BUF_SIZE because you may not be able to restore an older archive taken with a different BAR_XFER_BUF_SIZE size. |
#12
| |||
| |||
|
|
On Nov 10, 10:32*am, Superboer <superbo... (AT) t-online (DOT) de> wrote: Hello Malc, --> I know we can, using -w. I'm asking if the -f version allows the same, --> or can we only restore to the point where space 3 was backed up? --> Simple as that. No you can not. The onbar -b -w -L 0 does backup the content of your logical logs too simular as an ontape would do. So the restore can do a fast recovery after a physical restore. onbar -b -L 0 does not backup the content of your logs; (believe me i have been there you need your trx log to restore which means that you can not restore to the point in time the archive starts. this you can only do with an archive taken before and using trx logs.) Ta. Shame the manuals and training material don't state this explicitly. The impression from the training manual is that this is in fact possible. You could try and tune a bit in *upping BAR_NB_XPORT_COUNT make sure BAR_XFER_BUF_SIZE is 31 make a not if you change BAR_XFER_BUF_SIZE because you may not be able to restore an older archive taken with a different BAR_XFER_BUF_SIZE size. BAR_NB_EXPORT_COUNT is 10, BUF_SIZE 31 already. |
#13
| |||
| |||
|
|
On Nov 10, 10:32 am, Superboer <superbo... (AT) t-online (DOT) de> wrote: Hello Malc, --> I know we can, using -w. I'm asking if the -f version allows the same, --> or can we only restore to the point where space 3 was backed up? --> Simple as that. No you can not. The onbar -b -w -L 0 does backup the content of your logical logs too simular as an ontape would do. So the restore can do a fast recovery after a physical restore. onbar -b -L 0 does not backup the content of your logs; (believe me i have been there you need your trx log to restore which means that you can not restore to the point in time the archive starts. this you can only do with an archive taken before and using trx logs.) Ta. Shame the manuals and training material don't state this explicitly. The impression from the training manual is that this is in fact possible. You could try and tune a bit in upping BAR_NB_XPORT_COUNT make sure BAR_XFER_BUF_SIZE is 31 make a not if you change BAR_XFER_BUF_SIZE because you may not be able to restore an older archive taken with a different BAR_XFER_BUF_SIZE size. BAR_NB_EXPORT_COUNT is 10, BUF_SIZE 31 already. _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
![]() |
| Thread Tools | |
| Display Modes | |
| |