# Backup/Restore Bugs

**URL:** <https://forums.interworx.com/t/backup-restore-bugs/10965>\
**Category:** Bugs\
**Created:** [June 23, 2006, 8:13am UTC](https://forums.interworx.com/t/backup-restore-bugs/10965 "2006-06-23T08:13:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://forums.interworx.com/uploads/default/original/2X/4/40ab17cc34b792a0172b48ad1333b9ba9299a9a1.png) [@system](https://forums.interworx.com/u/system)\
**Post date:** [June 23, 2006, 8:13am UTC](https://forums.interworx.com/t/backup-restore-bugs/10965/1 "2006-06-23T08:13:38Z")

</div>

I did a domain backup from within Nodeworx and found the following:

It’s fast  
I like the ability to download the backup files  
It has problems…  
First, any customizations that have been done to mydomain.com.conf get blown away  
Second, and more importantly is that DNS records are reset to a ‘factory install’ state and all DNS record customizations are lost…

I believe a backup/restore should do exactly that… restore things to the way they were at the time of the backup, not at the time of the domain creation. I would consider the current backup/restore functionality broken.

Also, building in a COMPLETE site/server backup would be a very, very nice feature to have… I know Plesk has an Acronis True Image module that works very nicely… but of course Plesk isn’t as nice as Interworx 🙂

Cliff.

---

<div class="post-metadata">

**Author:** ![system](https://forums.interworx.com/uploads/default/original/2X/4/40ab17cc34b792a0172b48ad1333b9ba9299a9a1.png) [@system](https://forums.interworx.com/u/system)\
**Post date:** [June 25, 2006, 9:54am UTC](https://forums.interworx.com/t/backup-restore-bugs/10965/2 "2006-06-25T09:54:16Z")

</div>

Thank you for the feedback.

> [@chelsel](#):
>
> First, any customizations that have been done to mydomain.com.conf get blown away  
> Second, and more importantly is that DNS records are reset to a ‘factory install’ state and all DNS record customizations are lost…

This is normal behavior and we know it’s not ideal. I did put in a “bug report” on it a second ago and maybe we can do something about it eventually.

When Socheat gets back from vacation he can explain the specifics but I don’t believe this is as easy to fix as it sounds otherwise it would have been by now. 😉

> 

Also, building in a COMPLETE site/server backup would be a very, very nice feature to have… I know Plesk has an Acronis True Image module that works very nicely… but of course Plesk isn’t as nice as Interworx 🙂

No Plesk is deff not Iworx 😉

And a backup of NodeWorx settings is planned eventually.

Thanks again 🙂

---

<div class="post-metadata">

**Author:** ![IWorx-Socheat](https://forums.interworx.com/letter_avatar_proxy/v4/letter/i/ed655f/32.png) [@IWorx-Socheat](https://forums.interworx.com/u/IWorx-Socheat)\
**Post date:** [July 3, 2006, 10:31am UTC](https://forums.interworx.com/t/backup-restore-bugs/10965/3 "2006-07-03T10:31:20Z")

</div>

> [@chelsel](#):
>
> First, any customizations that have been done to mydomain.com.conf get blown away  
> Second, and more importantly is that DNS records are reset to a ‘factory install’ state and all DNS record customizations are lost…

To put it simply, both issues will be addressed in the next release of InterWorx. First, your mydomain.com.conf will _not_ automatically get restored, but it will be stored in the backup file so you can easily copy it back over and make any necessary changes. Second, DNS records will be backed up, and it will attempt to restore them intelligently.

Socheat

---

<div class="post-metadata">

**Author:** ![kipper3d](https://forums.interworx.com/letter_avatar_proxy/v4/letter/k/3be4f8/32.png) [@kipper3d](https://forums.interworx.com/u/kipper3d)\
**Post date:** [July 8, 2006, 9:30am UTC](https://forums.interworx.com/t/backup-restore-bugs/10965/4 "2006-07-08T09:30:55Z")

</div>

Also,

I noticed the interworx backups don’t include ftp accounts that go to seperate directories such as /home/username/ftpfolder non of that gets backed up.

SoCheat - I like the idea of putting the conf file in backup file instead of restoring it.
