# Backup Server **URL:** \ **Category:** Forum\ **Tags:** Adabas-Natural, Adabas, Adabas-Basics-on-Linux-Unix-Windows, Adabas-on-Windows-UNIX, Adabas-on-Linux\ **Created:** [November 14, 2011, 12:38pm UTC](https://techcommunity.softwareag.com/t/backup-server/98943 "2011-11-14T12:38:18Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [November 14, 2011, 12:38pm UTC](https://techcommunity.softwareag.com/t/backup-server/98943/1 "2011-11-14T12:38:18Z")
We are running Adabas 6.2 and Natural 6.3 on a Windows 2003 Server Enterprise Edition (physical server). We need to deploy a clone of this server on a virtualized platform (Xen) in order to be able to restore Adabas data if the physical server got unavailable. We are taking backups twice daily, at 15:00 and at 00:15. In order to have plogs as fresh as needed, I understand we should perform the command "adaopr db=1 et-sync feof=plog" on a hourly basis, for example. After that, we should copy the latest closed plog to the clone server. In case the clone server were needed, we could restore the last backup and process the hourly plogs. Any ideas, am I missing anything important? Thanks in advance, best regards ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [November 14, 2011, 3:00pm UTC](https://techcommunity.softwareag.com/t/backup-server/98943/2 "2011-11-14T15:00:42Z")
If it works like the online backup (adabck) new transaction cannot start while waiting for all users to come to ET-status. Users may experience this as the system is hanging. You could reduce TT but then the users will not have the ‘normal’ time to end their transactions and can get a TT timeout. ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [November 14, 2011, 7:36pm UTC](https://techcommunity.softwareag.com/t/backup-server/98943/3 "2011-11-14T19:36:51Z")
Thanks for the answer. What about perfoming the command: "adaopr db01 noet\_sync feof=plog? Can I copy the diferrent PLOG extents to the clone server instead of the different PLOG files? In order to reduce the recovery point without freeze the users. Best regards ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [November 15, 2011, 12:21am UTC](https://techcommunity.softwareag.com/t/backup-server/98943/4 "2011-11-15T00:21:47Z")
One thing you need to keep in mind when choosing your log switching strategy, is that the regenerate process is different depending on the use of et-sync for the log switch. When et\_sync is used, the completed protection log is for a full database session (i.e. there are no active transactions pending). This means that each plog file is processed in its own adarec job. When noet\_sync is used the plog files are extents of the same database session and must be regenerated in one adarec job. While a single job initially seems simpler, the handling of the multiple input files needs to be looked at carefully as, by default, for each plog extent the utility pauses and waits for the user to input the name of the next file. See the Using Utilities/Adabas Sequential Files section of the Adabas Administration manual for details. Cheers, Graeme Lane ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [November 15, 2011, 4:21pm UTC](https://techcommunity.softwareag.com/t/backup-server/98943/5 "2011-11-15T16:21:55Z")
I believe you can still apply these several extents (from noet\_sync and belongs to same session) in several ADAREC jobs as long as you do not shut down nucleus. ---
**Author:** ![Matthias1](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@Matthias1](https://techcommunity.softwareag.com/u/Matthias1)\ **Post date:** [November 22, 2011, 8:30am UTC](https://techcommunity.softwareag.com/t/backup-server/98943/6 "2011-11-22T08:30:27Z")
We’re doing a similar thing - using plog for replication. Our adaopr command is: ```auto adaopr db=xx,noet_sync,feof=plog ``` ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [April 2, 2021, 3:01pm UTC](https://techcommunity.softwareag.com/t/backup-server/98943/7 "2021-04-02T15:01:13Z")