Hey drPhil!First of all, have you tested cloud connectivity from the media agent you’re creating the library on using the Cloud Test Tool? → https://documentation.commvault.com/commvault/v11/article?p=9228.htmWith regards to troubleshooting this - are you adding from the Commcell Console (Java GUI) or Command Center?If adding from the Commcell Console, check the EvMgrS.log in the CV Log Files folder on the Commserve itself. If adding via the Command Center check out adminConsole.log - this will help somewhat but you’ll definitely want to check out the following log files on the media agent where you are adding the library to:cvd.logCloudActivity-cvd.logThese logs should get you started at least Let me know how you get on!
Hey Juergen,Would you be kind enough to provide the response output header + content?Also can you confirm your service pack / feature release version?ThanksEdd
Hello Nik14,Can you review the documentation @ https://documentation.commvault.com/commvault/v11_sp20/article?p=7102_1.htm and tell me if this answers your question?In short - 8403 can be used as a tunnel port for everything (data + control traffic) but it really depends on your port / network restrictions to be able to give a definitive answer as you may require one/two way network route if direction of traffic is restricted.RegardsEdd
With regards to the script - it may be the best option to tie you over until FR23 is available and you upgrade to it. There’s a few different ways you could do this and you’ll need to decide if you run the qoperation in asynchronous or synchronous mode which will most likely decide how simple / advanced your script needs to be! Some pseudo code for a script would be: Also to add, it is possible to entirely configure the script from Commvault using workflows without having to log into the target system. In this specific circumstance (PostgreSQL WAL archiving logs backup aka ‘Incremental’ backups in CV) - the backup needs to be triggered from the client to mimic the behavior of TSM as closely as possible. This could trigger a workflow which could be created to achieve what the script does but whatever route is chosen - PostgreSQL will run the ‘archive_command’ whenever a WAL file is archived and expect a return code of 0 or it will keep retrying until it gets 0 - at this po
Hey,Yep automatic schedule is not supported - it will be supported in FR23 which is not out yet The link I referenced was just to explain automatic schedule for log backups in general.FR23 will be out mid March 2021.With regards to the script - it may be the best option to tie you over until FR23 is available and you upgrade to it. There’s a few different ways you could do this and you’ll need to decide if you run the qoperation in asynchronous or synchronous mode which will most likely decide how simple / advanced your script needs to be! Some pseudo code for a script would be:Script executed (from archive_command):Check if a file pid.file exists If pid.file exists get the output of this file and check if that process is running If process is running exit the script If process is not running then create new pid.file with the current running PID If pid.file does not exist then create pid.file with the current running PID Run CV postgresql incremental (log) back
Hello,Welcome to Commvault! I’m sorry to hear we don’t match up with how TSM performs the log backups exactly, and it’s not what you are used to…Currently there is no method to have the archive command initiate a job and pipe the archive logs - however I can advise the following:Short term: Increase the frequency of your log backups based on the average WAL creation time - for example, run them every 5 minutes instead of every hour if required.Long term: Feature Release 11.23 once released will bring support of Automatic Schedule for log backups. This will allow you to specify the amount of logs present or disk spaced used which when met, will automatically trigger a backup. So you could set this to trigger a backup when 1 WAL file existed for example.Final thought: I have worked with a customer previously who created a script which would be called by the archive_command which would spawn a log backup in Commvault using the Commvault qoperation command, IF there was not already one run
No problem!
Hello,You are correct Install a second instance. Think of each installed instance as a separate client, and each client can be registered against the same or different commcell (but no client in a commcell can have the same client name or hostname).For example:MachineAInstance001 registered to Commcell1 (Client name MachineA)Instance002 registered to Commcell2 (Client name MachineA)MachineBInstance001 registered to Commcell2 (Client name MachineB)Instance002 registered to Commcell2 (Client name MachineB_2)It’s always prudent to check that when multi instancing, the agent is supported - Here’s a link to multi instance support for FR20 (Unix)
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.