What’s new in Arcserve UDP v6.5?

2016 saw a lot of growth to functionality of Arcserve, having introduced lots of new exciting features and changes in technology. In this article, I look at the newest added features in Arcserve UDP 6.5. (I left out existing features and performance enhancements so to focus on the newest features only.)

Instant Recovery Of Physical Server P2V IVM

An instant VM restore or IVM is mounting your latest backup point to your Hypervisor host as a temporary data store point and registering that VM into the Virtual infrastructure for immediate accessibility. It’s no longer necessary to wait for your restore to copy points from backup disk into production – with IVM your RTO is seconds to minutes.

UDP has had this feature from version 6.0. UDP can support Instant VM restore Cross-Hypervisor IVM V2V, instantly restore a VMware VM onto Hyper-V and visa versa. UDP also protects physical machines and allows for instant VM recovery of a physical node “ P2V IVM “ to Vmware or HyperV.

Nimble Storage Snapshot Integration

You can lower the additional impact from backup activities on production storage by retrieving VM data from storage snapshots on primary storage and replicated copies on secondary storage.

UDP has expanded on its existing integrations with NetApp, Nimble and Kaminiario and extends its direct Storage Snapshot support to HPE 3PARStoreServ Storage in version 6.5.

Direct Restore to Public Cloud

This enables users to take on-premises workloads and restore or migrate them to public cloud platforms. This can allow for disaster recovery strategy, development scenarios for testing or ease resource constraints on site by migrating workloads to scalable public cloud platforms.

UDP The Arcserve UDP Virtual Standby plan now supports the conversion of the recovery points to virtual machine formats on AWS EC2 with the help of the snapshots to restore your data easily. This feature ensures the highest available capability by using the public cloud and helps in shifting your backup environments on premise to AWS EC2 easily and quickly.

Backup for Microsoft Office 365

The Exchange Online component of Office 365 provides an offering for companies to utilise Exchange Mail services via Microsoft’s public cloud platform on a subscription basis. The challenge here has always been protecting and ensuring the recoverability of this public cloud exchange data in Office 365.

UDP also produces the new feature to help organizations protect the Office 365 emails hosted on Microsoft’s public or private cloud. Using this feature, users can secure and maintain a local backup of their Office 365 email data, eliminating the risk of data loss due to an outage or accidental deletion. Backup administrators can protect individual items such as emails, calendars, contacts, tasks, notes and so on. They can search the protected items and restore them using a wide range of flexible recovery options.

Additionally, by using the smart filter feature, administrators can opt to selectively back up only important folders and exclude others (for sync issues, clutter and so on). The feature reduces the backup window and helps to save the crucial network bandwidth and storage.

Backup Agent for Linux

This is a software agent designed to be installed on physical servers to allow the Linux file system and applications to be backed up. This is not new technology.

UDP: Agents for Linux have been around from the beginning of UDP. Arcserve also uses a single Linux system with an agent installed to orchestrate backups to all other Linux physical servers in the environment. Arcserve can do agent-free backup of Linux physical servers, only requiring one server to hold the Linux agent.

Agent for Windows

This is a software agent designed to be installed on physical servers to allow their Windows file system and applications to be backed up. This is not new technology.

UDP: Arcserve Windows agent for physical servers has been around since the inception of UDP and has support from Microsoft Windows Server 2003 SP1, all the way to the newest Windows Server 2016.

Backup from UNC Paths/Network Shares

This is the capability of protecting and backing SMB (CIFS) shares exported by an operating system or presented by a storage device link NAS.

UDP is now capable of protecting SMB (CIFS) shares exported by Windows, Linux, and NAS devices. As well as using such paths as a backup destination. This is a great feature for SMBs that don’t own file servers or don’t have storage capacity to protect an entire file server, they can rather just the share the path.

Automatic Protection of Newly added VMs to Hosts or Resource Pools

In Vmware, Vcentre VMs are sorted and grouped by resource pools. Having the ability to protect a resource pool allows newly created VMs on the Hypervisor to join a current backup job or policy. This reduces the administrative time of adding VMs to backup jobs through backup vendor software. This ensures instant protection.

UDP: In Arcserve’s newest release V6.5 you can protect a single container object (such as a resource pool) in the vSphere hierarchy. This way, new VMs added into the container object are protected automatically.

Recovery Point Testing

This feature will allow backup software to test the recovery point just made of a production server to ensure integrity of the recovery point. This will avoid any complications during a restore process.

UDP has added a new feature called Assured Recovery, which allows you to view the health status of the recovery points. The integrity and recoverability of recovery points are tested on a scheduled basis by automatically creating instant virtual machine copies or instant virtual disk copies. Additional built-in functions can test the file systems of IVM or IVD clones. No pre-set rolee scripts are available, but the option is available to run one’s own custom script against an Assured Recovery test.

SLA Reports for RTO and RPO on Protected Systems

SLA reporting on RTO and RPO allows the backup software to manage and report on protected servers and whether they are meeting RPOs (Backup windows) or RTO (Required Restore times). SLAs would be defined based on required up time and data loss policies for critical systems or applications in an environment.

UDP has added SLA reporting for RTO and RPO to the newest release 6.5. Arcserve UDP’s Service Level Agreement (SLA) report is to help organizations generate compliance reports related to Recovery Point Objective (RPO) and Recovery Time Objective (RTO).

RTO Report: The Arcserve UDP RTO report is a compliance report that displays the comparison of Recovery Time Actual and Recovery Time Objective values for all the executed recovery type of jobs, such as file system restore, VM recovery, BMR, Instant VM, and Assured Recovery. You can further drill down to see node level status filtered by ‘RTO met’, ‘not met’, ‘not tested’, and ‘not defined’ statuses.

RPO Report: The Arcserve UDP RPO report displays the total number of nodes with available recovery points during the specified time period in the bar view, categorized by age of the latest recovery points (15 minutes, last hour, 12 hours, last day, and so on), age of oldest recovery points (30 days and older), and monthly distribution (Jan – Dec). You can further drill-down to see node level statuses for the selected category.

This is all included under the UDP software suite and does not require addition purchase or licensing.

The Big Conclusion

Arcserve’s newest releases are way ahead of all the other competitors in terms of marketing and making waves.

In my opinion Arcserve, because of the physical and virtual portions, allows for the solution to be completely agnostic to customer hardware and Hypervisor choice and is a truly unified solution.

Arcserve also holds the high availability features set that been around for years. This eliminates RPO and RTOs as there is no data loss and no downtime. It’s more than just back up and disaster recovery, it’s business continuity too.

Arcserve provides both physical and virtual, unified and high availability features with enterprise reporting in a single installation, single interface, and a single license.

Arcserve UDP Appliances vs. Company “U”

The purpose-built appliance market has drastically changed in the past year, particularly in the mid-market. Historically, organizations looking to purchase all-in-one backup and recovery appliances only had a few limited choices, and specifically in the sub-100TB segment of source backup data.

The emergence of Arcserve UDP Appliances is changing the game, in particular for existing customers and prospects of Company U. There many reasons to underscore the acceleration of Arcserve UDP Appliances, and the subsequent reversal in market adoption for Company U’s solution.

While I will provide more specific detail below, let me net it out executive summary style:

  • Arcserve UDP Appliances are more cost-effective and provide more features than company U; one reason being their poor deduplication technology.
  • Company U’s reviews and tech support complaints on public community boards are at an all- time high.
  • Arcserve’s business is growing across the board, and our appliances and software have become the natural replacement for the aging and inefficient technologies in many organizations.

The smoking gun

One of the ways to determine marketing claims is to simply take a look at specifications and features. While Company U offers data deduplication – something you need as an end-user – it clearly lacks efficiency compared to the deduplication technology delivered by Arcserve..

How do you check? It’s simple: Take a look at the recommended configurations to see what model you’d need (how much on board-storage) to protect the amount of backup data (source data) you have in your environment, given some retention parameters.

But be careful, because Company U will tell you that its 120TB raw storage system can backup 80TB of data. (As a side note, in talking to customers in the field we believe it’s actually closer to 50TB – but let’s go with 80TB.) Conversely, Arcserve recommends a 30TB raw storage system for protecting roughly 90TB of source data. Note the difference here; needing 120TB vs 30TB to backup roughly the same amount of source data. In addition, it takes a 4U rack for Company U whereas the Arcserve UDP Appliance only requires a 2U rack.

Why does this matter? Read on to learn more about key differences in features and capabilities.

More features – that work


Arcserve’s deduplication technology is global source-based deduplication. This means that the deduplication is shared across all appliances and/or software/server deployments, and allows us to deliver extremely high levels of storage space savings (please see what our customers said here).

On the other hand, Company U uses a combination of host backup deduplication and inline deduplication, which means there’s always going to be some post-processing of the data. Further, it’s only central to that one appliance – so if you have five Company U appliances, they can’t share the deduplication store.

Recently, Company U added “inline” deduplication – a departure from the initial post processing. However, it’s only file, VMs, Exchange and SQL data. This means data that isn’t inline is still post-processed, such as Oracle data and bare metal file system backup data. In this scenario, you still need a landing a zone and the backup data store needs a lot of storage – hence the specifications discussed above.

Deduplication meets replication – or not:

Arcserve UDP delivers replication across appliances or software RPS servers (UDP’s “brains”) and is a key differentiator. Not only can you do can do restores from these instances, but it’s also great for scalability.

In contrast, Company U doesn’t scale well for the enterprise – each appliance has its own engine, and you have to manage them individually (you can connect from one and see all of them, but there is no global deduplication).

Further, Company U can only do many to one, or one to one – meaning that one appliance can only go to one target of replication. In the words of one customer, “if you have over five appliances, it’s unusable.” There have been many reports of replications issues, where their customers claim “It stops. It’s not working – the replication is cued up and not keeping up.” Alternatively, Arcserve allows you to do many to one, one to many or pretty much any permutation that makes sense for your environment.


Bottom line: Company U doesn’t offer cross-hypervisor capabilities. To be fair, they can do Physical to Virtual for Windows machines however to do so, they have to put an agent on the Windows machine and back that up. You can put that image in VMware or HyperV, and on the physical appliance you can run Windows physical backups on their Linux appliance – Windows Instant Recovery. But you would still need an agent on the virtual machines.

In comparison, Arcserve UDP software and appliances support cross-hypervisor recoveries or migrations and agentless backup without limitations. Just what you would expect from a three-time Best of VMworld award winner

User Interface:

Company U debuted a new (much nicer) interface it its 9.0 version. I seem to remember older versions still mentioning OS/2 Warp as OS options, so it was time for a face lift. Nicely done. Except that not everything can be done through it, and you still have to go back to the old interface (that’s what we’ve heard anyway). Oh well.

Cloud: Nebulous:

Company U can go to Cloud, but only directly. While this sounds interesting, you can’t do appliance disk to appliance disk to cloud – or multi-hop, if you will. This is a huge operational limitation, and given the poor deduplication ratios, you likely need to watch you bandwidth closely.

Tape: What?

Check out Arcserve’s impressive support for tape capabilities. Company U offers no support for multiple tape drives, just one drive at a time, and 99% of the vendors are not on the compatibility matrix (I may be exaggerating, but it’s very limited).

Money Talks

Using publicly available list prices, it’s easy to plot a comparison of the cost of protecting 1TB of source data by vendor, based on the publicly recommended specifications. In other words, how much will it cost you to backup 1TB of data with Company U vs. Arcserve. Below are the results with three-year maintenance included (apples-to-apples comparison).

Cost per Source TB

Arcserve also offers a series of models that come with Virtual Standby capabilities. To be complete, here’s what the picture looks like if we compare these models:

Cost per source TB 2
Need we say more?

Arcserve UDP vs. Company Vm – Part 2

In this second and final post comparing Arcserve UDP and Company Vm, we will focus on some very important differences in our respective backup and recovery technology. Let’s first remember that Company Vm focuses only on data protection for virtual environments, and by definition, creates serious gaps in their ability to support hybrid environments.

Support for physical systems is a built-in capability with Arcserve UDP. While many production environments may be highly virtualized, not everyone is 100% virtualized yet, nor do industry analysts seem to believe it will ever be the case. This underscores a very real need to offer support that protects physical systems in addition to virtual servers, or customers have no choice but to run multiple solutions, which is counter-productive and doesn’t deliver coherent restores across the environment.   Arcserve UDP supports both physical and virtual sources, and rrestores to physical and virtual destinations.

In terms of flexible recovery options, Bare Metal Recovery (BMR) is a “must-have” in a data protection solution, and allows you to quickly recover when a complete system fails. Customers often resort to “adding on” other BMR products when their “virtual system only” product does not offer this capability. With Arcserve UDP, customers get instant BMR to support local and remote bare metal recovery of Linux physical machines. Instant BMR provides better restore capability and an improved end-user experience by enabling instant access to a target machine prior to the entire recovery process being finished. This feature empowers users to instantly regain access into a failed physical Linux node, and is a first of its kind.

Let’s talk about tape. Tape is not a primary backup medium anymore as most end-users today have adopted disk to disk strategies (i.e. backing up to disk vs. tape). However, there are still many reasons to use tape as a secondary backup medium for long term retention or archival requirements. Company Vm’s V9 technology introducedadvanced” tape support, including parallel processing, concurrent copy sessions and GFS Rotation schemes (Grand Father, Father, Son). However, you can’t “improvise” tape support; it takes years to master it – and Company Vm’s support is very basic. In contrast, Arcserve UDP offers actual advanced tape features, such as: multiplexing (2-32 jobs), multi-streaming, device group and media pool, GFS rotation and synthetic backup, append media, media maximization, media pool manager, tape library option and auto library detection and configuration, bar code support, auto inventory, auto eject media, monitor blank media quantity, tape management and tape vaulting, auto tape cleaning and configurable block size for tape. We could go on, but hopefully you see the stark differences in our tape support.

As far as remote office protection, it’s important to protect business data no matter where your employees are located, and to protect those data nodes in an efficient fashion. Company Vm’s solution requires a separately installed WAN Optimization service (and that’s for their Enterprise edition only). In comparison, Arcserve UDP’s Recovery Point Replication is included in all the versions of our solution, and our Gateway feature provides fast WAN Transfer that makes it highly efficient.

There are also differences in how Arcserve approaches cloud backup and replication, compared to Company Vm. Cloud backup and replication allows for the backup product console to connect to a cloud-based service provider. This lets you replicate VM copies or backup points offsite into the cloud as a disaster recovery solution.

With Arcserve, the target Hypervisor is cross-compatible, and the source and target Hypervisor can differ in this instance. Also, Arcserve supports this on physical servers at the source which allows for physical to virtual (P2V) to the service provider. With company Vm, one of the limitations is if you’re replicating from Hyper-V, your service provider must provide Hyper-V. Not very flexible, is it?

Finally, in contrast to Company Vm’s software and cloud partnership only, Arcserve UDP is available as a software solution but also as an appliance, in addition to the Arcserve Cloud.

How to Take Hypervisor Snapshot of Lotus Domino VM with Unix/Linux Guest

I previously published a post Online Backup of Lotus Domino with Arcserve UDP, which used custom scripts so that DB’s consistency was guaranteed during the Arcserve snapshot of a virtual Windows Lotus Domino server.

This was, however, only compatible with Domino on Windows guest. I have since collaborated with Daniel Nashed from Nash!Com in Germany to come up with a creative solution to run an Arcserve Hypervisor snapshot of Domino Virtual Machine running on a Unix/Linux Guest.

Interested? Read on…

Daniel Nashed developed a script for Unix/Linux that would stop domino server. Utilising this script will allow Arcserve to take a DB consistent snapshot through the preferred Hypervisor. The script Bundle is available here. (Please note: the use of blogged scripts are at one’s own risk and should be tested with sandbox or lab copy of your production VMs). There is certain risk in shutting down Domino Server services at every backup, however, a shutdown is the only real solution for ensuring consistency of all databases during backup Snapshot pass.

Using virtualized Lotus Domino as a corporate messaging system on a Unix/Linux guest, the database’s consistency is guaranteed during backup by running custom script Rc_domino_script.

Once you have downloaded the script bundle from Nash!Com the bundle should look like this:




To start, the VM guest requires the relevant Hypervisor tools to be installed e.g. VMware tools or Host Integration tools. This will allow Arcserve to pass commands through the Hypervisor to the VM guest and initiate the script pre-snapshot and post-snapshot.

Next, the above files need to be copied to their relevant locations:

Rc_domino_script is the main script logic. It needs to be copied to the Unix/Linux guest location: /opt/ibm/domio

Rc_domino is the main entry point file for the service. It needs to be copied to the Unix/Linux guest location: /etc/init.d

Rc_domino_config_notes is the configuration file used. It needs to be copied to the Unix/Linux guest location: /etc/sysconfig

These three files all reference one another and are required for pre/post-snapshot.
If you are required to make changes, such as a different username for Domino, you will need to make changes to the config. file and modify the settings in the Rc_domino script. For more detail, refer to Read me or NashCom.

Once the script has been copied, we can now create an agentless plan in Arcserve UDP under plan > setting. In the Advanced tab, add the following commands to reference scripts:

/etc/init.d/rd_domino stop


/etc/init.d/rd_domino start


With the above, we are able to successfully snapshot Domino DB on Unix/Linux without an agent and provide application consistency.

Many thanks to Daniel for his Domino expertise!


Arcserve UDP Windows Remote BMR with WDS


With the new release UDP6, so comes the functionality of instant Linux BMR (Bare Metal Restore) which allows you to recover physical hardware remotely and instantly. This feature would be also be great for Windows environments not yet available.

A great solution for the remote recovery of physical Windows servers is to use Windows Deployment Service (WDS) integrating Arcserve UDP 6 Restore Capabilities with WDS, allowing for remote physical restore. It is no longer a requirement to have an engineer standing in front of your data centre rack to run system state recoveries on your physical system.

In this post I explain how I have created such an implementation and tested it!

The prerequisites are a Windows server and DHCP server (I used Virtual Servers in my testing but it applies to physical servers too).

The process would be to access your physical server through remote BIOS (e.g. ILO, IPMI or IDRAC or similar) and setting the server to network boot, at which point the server will PXE boot the Arcserve Windows BMR ISO files.

I used one server for the implementation: Server 2012 R2, running Arcserve UDP Console and RPS roles. I added Windows roles WDS and DHCP.

Installation guidance for WDS and DHCP:

How to install and configure Windows WDS

Installing and configuring DHCP


This one server had an Arcserve agent, so I created a BMR ISO for X86 and X64 compatible with ADK 8.1. You can create both Windows 8 and Windows 7 compatible boot kit ISOs for Server 2008 and 2012 physical server spreads in your environment.

*One important thing to note: if you run WDS and DHCP on the same server then some properties need to be altered on WDS as they both listen on the same port.


Once your BMR ISOs are created, browse to their location and mount ISOs.

Then open WDS MMC through Server Manager: under “Boot Images” browse, select add boot image and follow the wizard.

How to add boot images


Unfortunately WDS can’t use ISO format boot images and requires .WIM.

Browse Image location to:



Name your images as this will be displayed at your boot screen.

Add Image

Once the image has been created and stored, you can begin a network boot. (Log into server remote BIOS interface, initiate boot from network device.)

DHCP will assign an IP address and discover PXE proxy “WDS Server”.

Press F12 to Boot into PXE.


You can now see available images to boot from.



After boot select you will then see the Arcserve Bare Metal Recovery screen.

This is great for large workstation environments and multiple remote sites.


CTRL Z your life

After a busy day of writing emails, copying and pasting into spreadsheets and tweaking objects in this and that presentation; I was finishing up the last of it… tapping away on my laptop at the kitchen table when my right hand suddenly slipped and the mouse went “Saturday Night Fever” on me across the tabletop only to knock a glass of water off the side.

As the glass fell in slow motion, my left hand – still resting on the keyboard, jumped into action and out of pure reflex hit CTRL Z. To paint the picture for those of you who do not use keyboard shortcuts, I tried to stop a real life glass of water from breaking on my kitchen floor by using a computer’s “Undo” command. And… smash.control_z

This immediately provided my Mrs. with a new entry for her long catalogue of ‘silly things Louis has done’, the source material for her best jokes at my expense. It was one morning as I melodramatically writhed in pain following a stubbed little toe that she suggested satirically “Why don’t you just hit CTRL Z?” Funny…I’m told. But it got me thinking about it again and you know what? I need CTRL Z in my life.

This is the stuff science fiction is made of! Oh to imagine what it would be like to live in a virtual world where you can pick the rules, read the dark warnings of William Gibson’s Burning Chrome or enjoy the pop asceticism of The Matrix. However, as we spend even more time online, our lives routinely uploaded there, perhaps the future is closer than we think.

What commands would you want in your virtual world? I am just a Backup and Disaster Recovery guy so please forgive my lack of imagination for this bucket list of Louis’ Must Have Commands For His Virtual World:

1. Save a Recovery Point from when I was 21 so I can go back and have hair again any time I want.

2. Replicate myself on holiday. After deduplicating and compressing myself so that I could travel on even a modest connection, I would encrypt myself and then, either real time or scheduled, replicate myself to a datacenter in Barbados. NICE!

3. Use Virtual Standby to create a lookalike of me. Not feeling like work today? I would spin up a Virtual Machine copy of myself fully equipped with all the relevant data; applications and send the poor chap into work instead.

4. Archive my fashion mistakes to the cloud. This is pretty much all the way from 1995 till present day with only a few exceptions like weddings and one or two fancy dress parties. I would take Granular Restore with that just in-case I am ever feeling nostalgic and want to have a laugh at one or two badly dressed memories without having to remember the whole lot.

5. Make everything much easier to do than it currently is. I’m thinking of absolutely everything here; but specific examples include: baking a decent macaron, DARPA’s math challenge and Morris dancing.

6. Deduplicate plastic bags. If only we could delete all the unnecessary plastic bags in the World! Well this is my virtual world and we just did it! Of course we’ll keep one plastic bag to put in a museum somewhere…

7. SSD my brain. Daft Punk have already had this upgrade.

8.Intuitively know exactly what to do and when to do it. In my virtual world I’m not asking to be smarter, I’m just asking that everything else is simpler.

9. Truncate my logs before I go to bed.

There is probably a far more controversial version of this list available to anyone who uses Adobe Photoshop extensively; but all of the above mentioned Backup and Disaster Recovery capabilities are available at this very moment with Arcserve UDP in both software and appliance options. And for those of us left wanting CTRL Z right now and in the real world, Virtual Reality exists via our smartphones and we still have the power to untag bad photos of ourselves on the likes of Twitter and other social media platforms. Things are looking up – we’re getting there!

Online Backup of Lotus Domino with Arcserve UDP

Since Lotus Domino is an application non-VSS aware, the database’s consistency must be guaranteed during the Arcserve Snapshot of Lotus Domino process.

Using Lotus Domino as corporate messaging system, the database’s consistency is guaranteed running custom quiescing scripts (pre-freeze and post-thaw or Cache Flush) stored in C:\Windows in the Domino Server during the backup job.

See below; Option 1

Create 1 Batch File

This will Drop all connected users & Drop Cache.

Run the following Pre backup Script

“C:\Program Files\IBM\Lotus\Domino\nserver.exe” -c “drop all”

timeout /t 5 /nobreak

“C:\Program Files\IBM\Lotus\Domino\nserver.exe” -c “dbcache flush”

timeout /t 5 /nobreak

Net Time \\%computername% >> C:\Arcservebackup.log

Save As .bat

On the backup plan, add this:

backup plan

See below; Option 2

This will stop Domino Services get the DB to a consistent state and then run Snapshot.

After the Snapshot Process it will then start service once again.

You can Add Option 1 to Pre Freeze to speed up the Process.

Create 2 Batch Files

See below Create 2 Batch Files

Run one Pre backup and the other Post backup
Net Time \%computername% >> C:scripts\logs\freeze.log
rem ***************************************
rem creates and inventory of all running Domino processes
rem ***************************************
pslist | findstr /I /C:”nadminp” >>C:scriptslogspid.lst
pslist | findstr /I /C:”naldaemn” >>C:scriptslogspid.lst
pslist | findstr /I /C:”namgr” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ncalconn” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ncatalog” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nchronos” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ncollect” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ncompact” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nconvert” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ndesign” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ndircat” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ndrt” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ndsmgr” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nevent” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nfixup” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nhttp” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nhttpcgi” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nimap” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nimsgcnv” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nisesctl” >>C:scriptslogspid.lst
pslist | findstr /I /C:”niseshlr” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nldap” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nlivecs” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nlnotes” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nlogin” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nmtc” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nnntp” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nnsadmin” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nnotesmm” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nobject” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nomsgcnv” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nosesctl” >>C:scriptslogspid.lst
pslist | findstr /I /C:”noseshlr” >>C:scriptslogspid.lst
pslist | findstr /I /C:”notes” >>C:scriptslogspid.lst
pslist | findstr /I /C:”npop3c” >>C:scriptslogspid.lst
pslist | findstr /I /C:”npop3″ >>C:scriptslogspid.lst
pslist | findstr /I /C:”nreport” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nrouter” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nreplica” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nsapdmn” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nsmtpmta” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nsmtp” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nstatlog” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nstaddin” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nstats” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nsched” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nservice” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nserver” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ntaskldr” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ntsvinst” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nupdate” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nupdall” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nwrdaemn” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nweb” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nxpcdmn” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccmta” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ncctctl” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccmctl” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccttcp” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccbctl” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccmin” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccmout” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccdctl” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccdin” >>C:scriptslogspid.lst
pslist | findstr /I /C:”nccdout” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ngdsscan” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ngsscan” >>C:scriptslogspid.lst
pslist | findstr /I /C:”ngstmgr” >>C:scriptslogspid.lst
rem ***************************************
rem Stops Dominio daemon in a controller fashion
rem ***************************************
net stop “Lotus Domino Server (LotusDominoData)”
rem ***************************************
rem Wait a fair amount of time for processes to stop
rem ***************************************
Sleep 300
rem ***************************************
rem If some Domino processes are hanged, it kills all of them
rem ***************************************
for /f “tokens=2” %%I in (C:scriptslogspid.lst ) do pskill %%I
Net Time \%computername% >> C:scriptslogsfreeze.log
net start “Lotus Domino Server (LotusDominodata)”

On the backup plan, add this:

backup plan2