starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Backup and Restore #8734

New Issue
Closed
opened 2025-12-29 20:40:35 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:40:35 +01:00
Owner
Copy Link

Originally created by @RenatoPereira91 on GitHub (Oct 11, 2023).

NetBox version

v3.6.3

Feature type

New functionality

Proposed functionality

Via GUI a way to config external backup and restore, generate the backup and send to other server, if will get the server problem we can restore via GUI.

Use case

Easy restore of NETBOX if get crash of server

Database changes

No response

External dependencies

No response

Originally created by @RenatoPereira91 on GitHub (Oct 11, 2023). ### NetBox version v3.6.3 ### Feature type New functionality ### Proposed functionality Via GUI a way to config external backup and restore, generate the backup and send to other server, if will get the server problem we can restore via GUI. ### Use case Easy restore of NETBOX if get crash of server ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:40:35 +01:00
adam closed this issue 2025-12-29 20:40:35 +01:00
adam commented 2025-12-29 20:40:36 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Oct 11, 2023):

Thank you for submitting your idea. Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.

@DanSheps commented on GitHub (Oct 11, 2023): Thank you for submitting your idea. Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8734
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?