From nobody Sun Apr 17 06:32:24 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 54299CFF71C for ; Sun, 17 Apr 2022 06:32:24 +0000 (UTC) (envelope-from pstef@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Kh0br1zDfz3r41; Sun, 17 Apr 2022 06:32:24 +0000 (UTC) (envelope-from pstef@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650177144; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=kiP5vH+Gm5j0hxSuXbZYb/gtoc5OZ9RAPxq9yJaL4HE=; b=pATouP++Pf8uhQpjZUuwuZkl6TAnsTaxg2OYZKzAkGj1seA1AfBlLgzgEIAGlNyQ8djPCm BEs3fROqH+f9DFDvK3qDuk+GSE6qYfIy6/UORoIkQvCFI6Xz7LvOJjC1gGjGE6eSc67feh faThXpD9QWltBJ38cuG+NERvmvzsUrt7ehsnbc5ZNu+UxRbnj6mt79QXClsKVSCJnJagKE YL2hdWxOpxCU1sFVuXfuqxkuy4NzcyLQWOiTcz2Jqw3FEzRjI+5OAvOsKgOv/f2/Et5KTq p9z44EufbDjRJgEarsmd74elP8fN+uUp0jgZj7J3QyPAx38UlnlEY94VuNeI7A== Received: by freefall.freebsd.org (Postfix, from userid 1403) id 2BFDE19C17; Sun, 17 Apr 2022 06:32:24 +0000 (UTC) Date: Sun, 17 Apr 2022 06:32:24 +0000 From: "Piotr P. Stefaniak" To: Peter Jeremy Cc: Sami Halabi , FreeBSD Current Subject: Re: recover deleted file Message-ID: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1650177144; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=kiP5vH+Gm5j0hxSuXbZYb/gtoc5OZ9RAPxq9yJaL4HE=; b=HZ7ODchShoUWLlDhzKDf5X2SAaB4P9/YcNGgFOU3C3vCBCNlKHx+9KzgTky98O5a1o6kjP w4C2PklvAArbAtoH4na9pZ+DZuGt+ImwfCyyNy1ehnQbwebaBNpT0s8IktU9HwTojeZoPZ EhjXoX0agoLhkn/u/mavAwLgV0wjHwukntYtpM7ovQcOt8SbDER8JqsR160rFnx8ugN9GE MVXn8nloXlkDXKIrJkmN6Av/dQCEsgiMOJC4gieJ0tcdwE+wf5vGNulvjPAMmfSdJ6/KL8 GVc01ZxMFDCsS3eXR4pPwd0x4rSm7Xibfy/J/eIvLLoLwtoiPaiOv6QEsijshg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1650177144; a=rsa-sha256; cv=none; b=LXy566n1xGY2lOhhnDiVp/7SPDFfaiSvxPzphU0aRy5xeDzv4MNxl1vi3o0t1hsNR4aqHl riC4AT4P7JJfgAwum9JZnZZtg5KRcVDyKN9jfzpIOBZAG3L9JR6bUp7kCWZdYoeP1dNHlR nlhxq9akOba2YaA9RGPs+W4t4kFRcJBDnHtxgSDrEdziiQhpIH713x06uR8gmLy47L9L8n pHh85ZmWaE1VvxDz3kWIKMi3j6F49IOBw0n8kaXFBNl9OAbWc0fiNCiqoSPQLc8Na4MYEa Ky/LsPy9TWoyu3cC8VfGhDc9dE50T5KbSf+f2z7pVG6CETn5oSMg4SH1ciWShQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 2022-04-17 14:13:07, Peter Jeremy wrote: >If the information is very critical (you mentioned legal consequences) >then you might like to consider real-time replication of the MySQL redo >logs to another systems - though that won't necessarily protect you >from someone accidently doing a "DELETE FROM xxx;" or "DROP TABLE xxx;" It won't, but if it's a delayed replica, you have some time to recover the data. Piotr