# Unable to use a restore from NodeChef

**URL:** <https://meta.discourse.org/t/unable-to-use-a-restore-from-nodechef/162444>\
**Category:** Product Support\
**Tags:** unsupported-install\
**Created:** [August 30, 2020, 2:54am UTC](https://meta.discourse.org/t/unable-to-use-a-restore-from-nodechef/162444 "2020-08-30T02:54:09Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [August 30, 2020, 11:03pm UTC](https://meta.discourse.org/t/unable-to-use-a-restore-from-nodechef/162444/9 "2020-08-30T23:03:00Z")

</div>

> [@b481](#):
>
> Also, how does one replace the dump.sql inside the tar.gz file with the modified one?

```
# gzip dump and put it in the same directory as the backup 
gzip dump.sql

# copy backup file to fixed-* , replace this with your own backup file name
cp backupfilename-2020-08-30-123456-v20200830123456.tar.gz fixed-backupfilename-2020-08-30-123456-v20200830123456.tar.gz

# decompress
gzip -d fixed-backupfilename-2020-08-30-123456-v20200830123456.tar.gz

# remove original dump.sql.gz from the archive. 
# Note that the backup filename does not contain .gz in this step.
tar f fixed-backupfilename-2020-08-30-123456-v20200830123456.tar --delete dump.sql.gz

# add new dump.sql.gz. Note that the backup filename does not contain .gz in this step.
tar fr fixed-backupfilename-2020-08-30-123456-v20200830123456.tar dump.sql.gz

# compress it again. Note that the backup filename does not contain .gz in this step.
gzip fixed-backupfilename-2020-08-30-123456-v20200830123456.tar

```

---

_[View the full topic](https://meta.discourse.org/t/unable-to-use-a-restore-from-nodechef/162444)._