TAC Assisted Command Line Options
Previous Topic  Next Topic 

DiRT backup and restore supports a few command line options that can be useful to TAC engineers who are trying to run down issues with a system or investigate problems with a backup and/or restore procedure.  These command line options should only be used when working on a system with a TAC engineer.  These are not supported for general field use.

 

DiRT Backup:

 

/SkipSara - This option will skip the checks for Send As/Receive As rights of the currently logged in user if the option to backup messages is selected.  Note that skipping this check may (and probably will) cause ExMerge to fail logging into one or more mailboxes whn backing up messages.  This option is there only if TAC suspects the SA/RA check is returning a bogus result, which is a very rare case.

 

/DirtyBackup - This option will allow a backup of a Unity server that is not running.  Note that this is used by TAC as a quick mechanism to get the database and registry settings off a down system.  This will not allow you to restore this backup to a running system - if Unity is down, the backup will almost always be invalid and the restored system you apply the data to will also not come up.  This should only be used in very rare cases where TAC want's to get a closer look at data off a down Unity server.

 

DiRT Restore:

 

/PauseAfterSQLRestore - This option will cause a dialog box to pop up and wait for input after the backed up SQL database is restored but before DiRT restore does any updates to the data or calls a directory synch.  This can be useful if TAC wants to look at the data prior to updating to be sure the backed up system was clean or the like.  This does not affect the restore process other than to pause it in the middle after the SQL restore is complete.

 

/SkipVersionCheck - This causes DiRT restore to not check the version of the backed up system against the version on the local box.  Note that this will very likely cause a unpredictable system if you are restoring across versions.  This is not supported unless closely supervised by TAC and will almost never result in a completely clean restore because of differences in the database and registry between versions of Unity.

 

/DirtyRestore - This option allows the DiRT restore to proceed even if the local system is not a clean, new installation.  The restore is itself is not affected - the checks for a new installation are to be sure sites do not accidentally wipe out a production system they did not intend to.  Again, this option should be used if TAC is working with you - DiRT will wipe out all Unity specific data on a running system if you use this option, please use with caution.