Another question on Error 152
Hi, =20 we use on-bar for our backups through Data Protector (aka OmniBack) on our SAP/Informix servers. For some of the QA systems we don't need to have the logs, so the parameter LTAPEDEV has been set to /dev/null =20 Of course we get error 152, we don't mind (at that moment) =20 Now at the end of the month we run a report that reflects the quality of our backups and there we get a figure that's reflecting these "failed" backups. =20 Any ideas how we could work around this 152 error and yet not have to make backups of our logs? =20 kind regards, Luc van Gastel =20
You may want to create a fake device pointing to /dev/null. To do so create a soft link pointing to /dev/null. We did that to avoid this error in the Omni back backup report. Regards Diane Lavoie -----Original Message----- From: van Gastel,.... [mailto:luc.van-gastel@hp.com] Sent: Thursday, December 09, 2004 11:34 AM To: ids@iiug.org Subject: Another question on Error 152 [3860] Hi, =20 we use on-bar for our backups through Data Protector (aka OmniBack) on our SAP/Informix servers. For some of the QA systems we don't need to have the logs, so the parameter LTAPEDEV has been set to /dev/null =20 Of course we get error 152, we don't mind (at that moment) =20 Now at the end of the month we run a report that reflects the quality of our backups and there we get a figure that's reflecting these "failed" backups. =20 Any ideas how we could work around this 152 error and yet not have to make backups of our logs? =20 kind regards, Luc van Gastel =20
Hi Diane, I was thinking of such a solution indeed. Have you had any experience with restoring from backups after having setup such a construction? Kind regards, Luc -----Original Message----- From: Lavoie, Diane [mailto:diane.lavoie@domtar.com] Sent: Thursday, December 09, 2004 7:06 PM To: van Gastel, Luc (HPWest SAP-UNIX team); ids@iiug.org Subject: RE: Another question on Error 152 [3860] You may want to create a fake device pointing to /dev/null. To do so create a soft link pointing to /dev/null. We did that to avoid this error in the Omni back backup report. Regards Diane Lavoie -----Original Message----- From: van Gastel,.... [mailto:luc.van-gastel@hp.com] Sent: Thursday, December 09, 2004 11:34 AM To: ids@iiug.org Subject: Another question on Error 152 [3860] Hi, =20 we use on-bar for our backups through Data Protector (aka OmniBack) on our SAP/Informix servers. For some of the QA systems we don't need to have the logs, so the parameter LTAPEDEV has been set to /dev/null =20 Of course we get error 152, we don't mind (at that moment) =20 Now at the end of the month we run a report that reflects the quality of our backups and there we get a figure that's reflecting these "failed" backups. =20 Any ideas how we could work around this 152 error and yet not have to make backups of our logs? =20 kind regards, Luc van Gastel =20
Hi Luc, Yes we did some restores after setting this up. Basically, you have no choice then doing a sequential backup/restore which there is no need for logs. Regards Diane Lavoie -----Original Message----- From: van Gastel, Luc (HPWest SAP-UNIX team) [mailto:luc.van-gastel@hp.com] Sent: Friday, December 10, 2004 4:19 AM To: Lavoie, Diane; ids@iiug.org Subject: RE: Another question on Error 152 [3860] Hi Diane, I was thinking of such a solution indeed. Have you had any experience with restoring from backups after having setup such a construction? Kind regards, Luc -----Original Message----- From: Lavoie, Diane [mailto:diane.lavoie@domtar.com] Sent: Thursday, December 09, 2004 7:06 PM To: van Gastel, Luc (HPWest SAP-UNIX team); ids@iiug.org Subject: RE: Another question on Error 152 [3860] You may want to create a fake device pointing to /dev/null. To do so create a soft link pointing to /dev/null. We did that to avoid this error in the Omni back backup report. Regards Diane Lavoie -----Original Message----- From: van Gastel,.... [mailto:luc.van-gastel@hp.com] Sent: Thursday, December 09, 2004 11:34 AM To: ids@iiug.org Subject: Another question on Error 152 [3860] Hi, =20 we use on-bar for our backups through Data Protector (aka OmniBack) on our SAP/Informix servers. For some of the QA systems we don't need to have the logs, so the parameter LTAPEDEV has been set to /dev/null =20 Of course we get error 152, we don't mind (at that moment) =20 Now at the end of the month we run a report that reflects the quality of our backups and there we get a figure that's reflecting these "failed" backups. =20 Any ideas how we could work around this 152 error and yet not have to make backups of our logs? =20 kind regards, Luc van Gastel =20