I moved this to the Server Administration areas where it is more likely to get a response from the other Server Admins in the community. I am also bringing this to the attention of a few of our support team members to see if they might have an idea.
Can you please explain some more?
Also, why do you think the custom views would change?
Custom views belong to the user that saved it. They are non-modifiable except by the person that created it. If many of the dropdowns are changing based on the reorg, then can you go and create a new set of custom views or ask the owners to change the ones that they originally created.
It might be better asking it this way:
Is there a way to back up the custom views that have been created in the event that the server is replaced or shutdown etc so that you could restore the custom views on the new server if the data hasn't changed?
Thanks for the reply but it's not feasilbe for the custom views to be restored manually as there have been a large number of them created. I'm really looking for a way to "save/import" the custom views so that they can be restored if there's an incident on the server and everything needs to be setup on a new server.
Given your reply to Jeff as well as mine I would say a Tableau Server backup. Of course this would backup the entire Server; you cannot back up individual objects.
There is one POSSIBLE option if your custom views are in just one Site: tabadmin importsite. I haven't tried this and, honestly, it is too much work to just "simply test". I have a rambling blog post about this function in April 2015: Toby Erkson's Blog Start at the bottom and work your way up OR start at the first one and then click the next arrow to move to the next:
Hi Robert. Typical incident handling is by one of three methods.
1. tabadmin backup / restore. We run a backup on a nightly basis and this acts as our checkpoint to fall back on in case of a disaster
2. Establish a high availability cluster. This essentially means that there is a minimum of I think 3 nodes within your platform (or maybe its 2 nodes + a primary) and there is redundancy baked into the solution as the repository and data extracts are kept in sync in multiple spots (I think the filestore does this). You can find more info here: High Availability The custom views are embedded in a few different places within the repository and even if you were able to backup and restore one of the objects, there's a high degree of risk of being out of sync.
3. importsite / exportsite which I didn't really think about until Toby mentioned it.