CORRECTION at 11:37 discussing the 4 eyes peer review, 100% a burning the midnight oil brain fog moment. I said that it wasn't a great example and then proceeded to explain something totally different to what Jason said, and got my states muddled up. Their example is actually fine, you would want a 4 eyes check on moving something from Released > WIP > Released. For some reason I thought I heard WIP > Released > WIP. My error, and apologies. Also apologies for the low audio levels in this one, the compressor was turned off for some reason so I lowered the whole thing down a bit. Hopefully removed most if not all of the loudness spikes.
Thanks for the video! Company I work has the filestore on a separate disk which is backed up weekly as a disk image instead of separate files. Same happens with SQL servers as well. When we need to do backup manually for example during a update or server maintenance. There has been a detour to only backup the database snapshot by renaming the actual filestore and creating an empty one with correct name. Then just run the backup. This method had the downside that IIS had to be stopped in order to rename the filestore. I’m quite happy with this update. This will make my life easier by making database backup much easier and finally makes it possible to properly manage design data and styles properly
Hey in 2024.2 they introduced "distributed views". Thunderdome was so much more straightforward. And how about Inventor's export/import configuration? So now we have distributed views, but I'm struggling to understand the workflow and logic behind the workflow. In particular I want to be able to distribute the grid states for the Edit Properties dialog - I can "save as distributed search", but it doesn't "go" anywhere that I can find. It's all a bit of a muddle to me. Can you do a video that includes how to make use of this long-overdue and long-awaited feature?
21:15... We've got Vault setup on 3x separate Azure servers: SQL / Database / Filestore. That's why the database only back-up would be useful. I think you'd still have issues with trying to do a restore because if you don't have your filestore and database aren't synchronized, then Vault kills all your permissions to everything; found that out the fun way.
That's exactly my point, I understand people split the resources off to different servers but only backing up 1 part is mind boggling me... I said this in another comment but if you restore the DBs from a week ago then you've got a data consistency mismatch hooking into a newer filestore, or vice versa, I still can't grasp why someone would choose to do this over just backing up literally everything as per usual
@@Neil3D You would hope the gap of backup would never be as large as a week. However, cloud VM's where you are taking a daily backup of the whole image anyway, the db only works fine. A mismatch still restores. If there is a certain version of a file missing worst case, you get notified and then need to fix that, usually that's not a problem, if it was a replicated environment that has almost no down time you may choose a different strategy. I have not seen what @dsl145 is describing with "Vault kills all your permissions" because of a mismatch with a DB and FS.
Thanks for review. There are so engineers like me rely on content available on TH-cam to enhance their skills. It's sound good that you have good knowledge of tubing and piping also. But I didn't find any videos of tubing and piping on your TH-cam channel. Please also make videos on tubing and piping. Because, I like to watch your videos to learn something new. Waiting for that...
Nice video Neil! I think you can could isolate those costly jobs to a separate job processor today. In the job processor config, there is a list of job types that can be processed - just disable the costly job on every other job processor, and enable only that job on your dedicated processor.
Thanks Paul - at that point I wasn't sure if the jobs would be listed as separate triggers i.e. a separate call for PDFs and a different call for STP files, or if they'd be lumped into the same combined job. Good though, thanks for letting me know
In the Thin Client is there a way for a user to change their own password? Also do you have any videos on dealing with reports in Vault 2023, I am trying to create my own reports but they aren't coming out great..
Thanks Neil for great Vault video! Template folders is a big one for me finally it can be stored in Vault. I hope one day we can store ilogic external rules in Vault too with no issue being read only and it would be nice if we could managed rules lifecycle thru Inventor Vault add-in.!
I wish that vault unique file naming would behave differently. We would like to enter own file names and add a uinque identifier number as a prefix, but we have trouble to use this in some circumstances. For example if we use a custom bolt we would like inventor to save the bolt with the name it has from content center and add the unique identifier after. But as i experience i have to chose either a random number or skip to use own text. I can´t get it to take the text and add the unique identifier as a prefix automatically? Can we set it up differently? I don't want just a random number on the files, i also want the names. Has there been improvements hos this work in 2024?
15:50... the thing is; they took to long to have this functionality in place that likely a lot of firms have already developed their own systems to do the same thing... we sure have.
Some of the backup options were for people using multiple servers. I have had a setup where I had a server with ADMS, a separate SQL server, and a File Store server. Very overcomplicated.
Yea I guess, although just creating a backup of only the DB info... in the event of a restore, whether you're restoring just the DBs or just the Filestore, there's gonna be a data consistency mismatch? Say the DB died, so you restore the DBs from 1 week ago, you now have a 1 week old set of DBs but a current filestore, or vice versa, I'm still not getting it...! The AVFS console can't do backups either? If you can describe how this would be used in reality that would be awesome!
Well if this is a niche within a niche I must be a niche within a niche within niche as a non (currently!) Inventor or Valult user and watching this at 1.5x speed! 😳😀 Thanks for keeping us informed (for when I get to move of flipping Rhino back to a propper drafting package! 🤞🤞)
Being in a nested niche is the bain of my life tbh! It's work stuff on TH-cam, that's a niche, then spefically engineering, niche, Autodesk software, niche, then stuff like this which 99% of Autodesks customers dont ever touch! Niche to the power of a bazzilion
I think the 4 eyes check is not implemented correctly and Autodesk conclusion how people work is wrong. I could prevent from one single person to release his own file for the last 10 years with the security options in transitions. On the other hand, if I could pick a person (and automate that pick) while changing state and that person will get an email that a file needs reviewed then that will be a REAL 4 eyes check. What we got now is nowhere near what actually people are asking.
Hi Neil, Hope your well, some of your previous videos have Password protected downloadable tutorial files, but there isnt the option to "join" anymore, can you send me the password if i gave you a "super Thanks" or do you have another option, kind regards James
CORRECTION at 11:37 discussing the 4 eyes peer review, 100% a burning the midnight oil brain fog moment. I said that it wasn't a great example and then proceeded to explain something totally different to what Jason said, and got my states muddled up. Their example is actually fine, you would want a 4 eyes check on moving something from Released > WIP > Released. For some reason I thought I heard WIP > Released > WIP. My error, and apologies.
Also apologies for the low audio levels in this one, the compressor was turned off for some reason so I lowered the whole thing down a bit. Hopefully removed most if not all of the loudness spikes.
Thanks for the video!
Company I work has the filestore on a separate disk which is backed up weekly as a disk image instead of separate files. Same happens with SQL servers as well.
When we need to do backup manually for example during a update or server maintenance. There has been a detour to only backup the database snapshot by renaming the actual filestore and creating an empty one with correct name. Then just run the backup. This method had the downside that IIS had to be stopped in order to rename the filestore.
I’m quite happy with this update. This will make my life easier by making database backup much easier and finally makes it possible to properly manage design data and styles properly
Hey in 2024.2 they introduced "distributed views". Thunderdome was so much more straightforward. And how about Inventor's export/import configuration? So now we have distributed views, but I'm struggling to understand the workflow and logic behind the workflow. In particular I want to be able to distribute the grid states for the Edit Properties dialog - I can "save as distributed search", but it doesn't "go" anywhere that I can find. It's all a bit of a muddle to me. Can you do a video that includes how to make use of this long-overdue and long-awaited feature?
21:15... We've got Vault setup on 3x separate Azure servers: SQL / Database / Filestore. That's why the database only back-up would be useful. I think you'd still have issues with trying to do a restore because if you don't have your filestore and database aren't synchronized, then Vault kills all your permissions to everything; found that out the fun way.
That's exactly my point, I understand people split the resources off to different servers but only backing up 1 part is mind boggling me... I said this in another comment but if you restore the DBs from a week ago then you've got a data consistency mismatch hooking into a newer filestore, or vice versa, I still can't grasp why someone would choose to do this over just backing up literally everything as per usual
@@Neil3D You would hope the gap of backup would never be as large as a week. However, cloud VM's where you are taking a daily backup of the whole image anyway, the db only works fine. A mismatch still restores. If there is a certain version of a file missing worst case, you get notified and then need to fix that, usually that's not a problem, if it was a replicated environment that has almost no down time you may choose a different strategy. I have not seen what @dsl145 is describing with "Vault kills all your permissions" because of a mismatch with a DB and FS.
Would step file creation not be managed by the product lifec ycle? If the part/assy requires step creation you have a seperate lifecycle that doe is?
Thanks for review.
There are so engineers like me rely on content available on TH-cam to enhance their skills.
It's sound good that you have good knowledge of tubing and piping also.
But I didn't find any videos of tubing and piping on your TH-cam channel.
Please also make videos on tubing and piping.
Because, I like to watch your videos to learn something new.
Waiting for that...
Nice video Neil! I think you can could isolate those costly jobs to a separate job processor today. In the job processor config, there is a list of job types that can be processed - just disable the costly job on every other job processor, and enable only that job on your dedicated processor.
Thanks Paul - at that point I wasn't sure if the jobs would be listed as separate triggers i.e. a separate call for PDFs and a different call for STP files, or if they'd be lumped into the same combined job. Good though, thanks for letting me know
In the Thin Client is there a way for a user to change their own password?
Also do you have any videos on dealing with reports in Vault 2023, I am trying to create my own reports but they aren't coming out great..
Thanks Neil for great Vault video! Template folders is a big one for me finally it can be stored in Vault. I hope one day we can store ilogic external rules in Vault too with no issue being read only and it would be nice if we could managed rules lifecycle thru Inventor Vault add-in.!
I appreciate your vault videos very much. Keep them coming.
I wish that vault unique file naming would behave differently. We would like to enter own file names and add a uinque identifier number as a prefix, but we have trouble to use this in some circumstances. For example if we use a custom bolt we would like inventor to save the bolt with the name it has from content center and add the unique identifier after. But as i experience i have to chose either a random number or skip to use own text. I can´t get it to take the text and add the unique identifier as a prefix automatically? Can we set it up differently? I don't want just a random number on the files, i also want the names. Has there been improvements hos this work in 2024?
15:50... the thing is; they took to long to have this functionality in place that likely a lot of firms have already developed their own systems to do the same thing... we sure have.
All I need is a simple, fast project copy and "rename" feature. Design Assistant is a ball ache.
Some of the backup options were for people using multiple servers. I have had a setup where I had a server with ADMS, a separate SQL server, and a File Store server. Very overcomplicated.
Yea I guess, although just creating a backup of only the DB info... in the event of a restore, whether you're restoring just the DBs or just the Filestore, there's gonna be a data consistency mismatch? Say the DB died, so you restore the DBs from 1 week ago, you now have a 1 week old set of DBs but a current filestore, or vice versa, I'm still not getting it...! The AVFS console can't do backups either? If you can describe how this would be used in reality that would be awesome!
I work on the similar setup. We have ADMS and Filestore on one server, SQL on another. And have a dedicated server for Job Processor.
Well if this is a niche within a niche I must be a niche within a niche within niche as a non (currently!) Inventor or Valult user and watching this at 1.5x speed! 😳😀 Thanks for keeping us informed (for when I get to move of flipping Rhino back to a propper drafting package! 🤞🤞)
Being in a nested niche is the bain of my life tbh! It's work stuff on TH-cam, that's a niche, then spefically engineering, niche, Autodesk software, niche, then stuff like this which 99% of Autodesks customers dont ever touch! Niche to the power of a bazzilion
@@Neil3D nested niche! 😂👍
I think the 4 eyes check is not implemented correctly and Autodesk conclusion how people work is wrong.
I could prevent from one single person to release his own file for the last 10 years with the security options in transitions.
On the other hand, if I could pick a person (and automate that pick) while changing state and that person will get an email that a file needs reviewed then that will be a REAL 4 eyes check. What we got now is nowhere near what actually people are asking.
This reminded how AD gave us symmetry in Inventor constraints. Nobody understands it
Nice too know.
Let´s tyalk about Plasticity Mr. Cross...It´s a relativly new 3D Program on the Horizon come up ;)
Hi Neil, Hope your well, some of your previous videos have Password protected downloadable tutorial files, but there isnt the option to "join" anymore, can you send me the password if i gave you a "super Thanks" or do you have another option, kind regards James