go to post Ambrogio De Lorenzo · Feb 16 It seems that NAME is defined as 40 char but you are inserting a string with 47 chars. In fact your string is 45 chars that is out of space defined for the column. In order to check the escaping logic you should try with a shorter strings.
go to post Ambrogio De Lorenzo · Feb 9 Hi Kurro, this could work but the cost in terms of hw resources is high compared to $RANDOM.
go to post Ambrogio De Lorenzo · Feb 9 Hi Enrico, the problem is that $r(4) returns number between 0 and 3.If you add 1 you will have numbers 1 2 3 4 but not 5.You can correct your code with $r(5)+1
go to post Ambrogio De Lorenzo · Feb 1 You can use also a Storage Based replication method. If your environment support it, you can: Freeze instance Replicate data Thaw instance If replica time is short enough this could be a very usefull method. If you have enough free space and you use Linux LVM, you can also use the LVM Snapshot.
go to post Ambrogio De Lorenzo · Feb 1 I agree with your comment, even if I didn't mentioned it. Maybe he is using a VM so CommVault can be configured to take a snap on VMFS and copy it. The bad is the logic in scripts, cause Commvault will not be notified of freeze is ok and to start the backup.
go to post Ambrogio De Lorenzo · Jan 30 Yes, but only if it really fails. Commvault should know of the backup cause it's do a backup.The pre-script is used to configure the DB in freeze mode, so you can take a snapshot or a backup. If the pre-script is ok it should return 0 so commvault can start the backup process. After the backup completes commvault will launch the post-script, so the DB can return in normal way (thaw). If the post-script is ok it must return 0 so commvault can understand that the process is completed. I think you should reengineer your entire backup process with those steps in mind.
go to post Ambrogio De Lorenzo · Jan 30 Your scripts are a bit complex but the backup pre-post command should return 0 if completed correctly. So backup software can understand if the pre-command (preparation for backup) is completed ok.If return code is 0 the backup can start saving data.When backup completes commvault will start the post command. Also the post command should return 0 if completed correctly. In your script maybe it's better you should specify exit 0 when needed.
go to post Ambrogio De Lorenzo · Jan 29 Hi Eyal, I can't figuring how the system can now that a backup is started without the pre-post script on commvault.Can you provide the pre-post script to understand what you would like to do?
go to post Ambrogio De Lorenzo · Jan 22 As mentioned by @Brett Saviano the XFS is recommended on Ubuntu, but ext3 and ext4 are supported.Read notes to choose the better. LVM is also solid and in large environment, even if it introduce a little overread, it can be usefull in changing disks layout. You can add space or move data without service disruption. With FS on whole disks you must copy data files and this must be done with services down.
go to post Ambrogio De Lorenzo · Jan 18 Hello, to better understand what is appening you can start with debbugging the ssh communication. You can point to this doc to see if it helps: https://community.intersystems.com/post/using-and-debugging-netsshsession-ssh-connections
go to post Ambrogio De Lorenzo · Jan 18 Very interesting starting point to understand how to collect performance informations.
go to post Ambrogio De Lorenzo · Jan 15 Hello, it's not so clear, but if you try to convert date to HL7 you can use this: d.toISOString().replace(/[-:]/g, '').split('.')[0] This should generate a string with d in HL7 format.
go to post Ambrogio De Lorenzo · Jan 12 Good, so the folder test under tmp is not writable by all. If your script runs under different user and goup (not r00028881) the file could be read and seen but not removed. You can try to chmod 777 /tmp/test in order to understand if this is the problem. If you can remove the file after the chmod you must understand who is creating the test folder under /tmp or who is running the script that is unable to remove the file. Regards Ambrogio
go to post Ambrogio De Lorenzo · Jan 12 Hello Token, this cannot be the output for your environment. You are asking (with ls /tmp/test.txt -lh) to show the file or directory named test.txt in the /tmp folder.As the result is-rwxrwxrwx 1 r00028881 r00028881 8 Jan 11 09:56 /tmp/test/test1.txtit cannot be the answer for the previous command. So, you should execute those commands: ls -lad /tmp/test/test1.txtls -lad /tmp/testls -lad /tmp Copy and paste the output so we can understand better the folders content. Regards Ambrogio
go to post Ambrogio De Lorenzo · Jan 11 Hello Token, are you sure file exists and you have right permission to remove the file?Tipically err 13 on Unix is related to bad permissions
