Education & Training
Services & Support
CA Automic Community
CA Automic Workload Automation
to create and rate content, and to follow, bookmark, and share content with other members.
How to Backup a UC4 Client
Discussion created by
on Apr 19, 2017
on Apr 27, 2017 by AlainMoisy
Show 0 Likes
How to Backup a UC4 client?
What are the step or procedure?
This content has been marked as final.
Show 4 comments
(Required, will not be published)
Apr 19, 2017 3:34 PM
You could use the "Client Copy" or a "Transport Case" both have their pro/con and depending on what you want to backup + where you want to save your "backup" client at.
If you just want a whole client backup (all object, message/statistics/reports etc..) and put it onto another or same database/system, the simplest would be the client copy.
See reference material:
Whitepaper explaining pro/con
community post explanation
Client Copy from the Manual
Transport Case from the Manual
Show 0 Likes
Apr 19, 2017 5:51 PM
We have a JAVA API Solution that creates an XML file per AE object.
Another possibility is the unload Utility with -BTRANSPORTALL - thats great for doing object backups on a daily basis without statistics.
Show 1 Like
Apr 26, 2017 12:01 PM
I agree with Wolfgangs attempt to solve the issue.
While a ClientCopy of course might work and copy your client (excluding the activities of course) 1:1 to another client, this might be sufficient if you do this only once. if you want to do this on a regular base, this might soon reach its limits since you might have then 10 or more clients containing kind of the same content just for backup reasons,
I think a combination of both, transport case as wolfgang advises, and a "playground" client as luu stats might be a good solution. You do the transport using the unload utility, and if you need a specified object, you load the transport case of the time you need the object from, to the playground client, and then move the object from there.
Alternatively you can also check version management which also keeps up the latest versions of the objects for backup reasons. Maybe this is also already sufficient for you.
Show 1 Like
Apr 27, 2017 12:53 PM
Basically you have two types of backups :
Full client backup : you can use the ucybdbun utility program to do it and schedule a job to do it on a regular basis like at every daily maintenance cycle i.e. This will backup all definitions in a transport format file that you can compress to save space. Reload it into an empty client to access individual objects or use it to rebuild a full client.
Object detail backup : you can use the EXPORT script function to do it with a loop and an input list of all the objects of the client using an SQLI variable to list them i.e. You will get an xml file per object so you can select what object individually you want to restore or reload in another client.
The use of the Client Copy utility program is more appropriate if you want to have a full copy of a client including the statistics and reports. But then it is taking a long time to complete if you have thousands and thousands of objects and a long retention period. Plus it will require another DB with enough space or will impact a bit your DB access if you do it in the same DB (but then why call this a backup ?).
Hope this can clarify a bit the multiple options you have to do a "backup" of a client from all the suggestions in the previous comments.
Show 0 Likes
Retrieving data ...
Command to get all jobs from multiple instances.
Wildfly 8.x (JBOSS EAP 7) Unicast & File Replication "Chain" Clustering
Database High Performance
Order of Jobs in a box