Highlighted
brastedd
3 Argentium

Updating Avamar Exchange VSS and GLR plugins

Jump to solution

Hi. I've been tasked with updating our Exchange Avamar VSS and GLR plugins tomorrow, and I'm trying to make sure I have all the information I need before I do the uninstall and reinstall.

1) The manual refers to a "WriteCache" folder. Where is the default location for that? Is it the same as the avfscache folder Avamar uses for GLR?

2) Is it safe to run the Backup User Configuration Tool at any time? I don't want to make any changes before tomorrow, and this is a mission-critical Exchange cluster.

3) Is it safe to run the Cluster Configuration Tool at any time?

4) We have a DAG but I cannot see an Avamar DAG client in Avamar Administrator. Does there have to be one set up? We do our database backups separately on each database server in the cluster.

If there is one, where can I find the information I'll need to set it up exactly the same after I finish the update?

Tags (3)
0 Kudos
1 Solution

Accepted Solutions
Amol
3 Argentium

Re: Updating Avamar Exchange VSS and GLR plugins

Jump to solution

1) The manual refers to a "WriteCache" folder. Where is the default location for that? Is it the same as the avfscache folder Avamar uses for GLR?

AP > Yes, the default location is "C:\Program Files\avs\var\avfscache\"

2) Is it safe to run the Backup User Configuration Tool at any time? I don't want to make any changes before tomorrow, and this is a mission-critical Exchange cluster.

AP> Yes, once you run the tool it queries AD and check if user has all the required permission. If the user does not exist it gives and ability to create a user in AD

3) Is it safe to run the Cluster Configuration Tool at any time?

AP> Yes, this tools uses Windows API to check if the current system is a part of  a cluster, it also provides visual representation of all the nodes in the cluster and Avamar plugin configured on it.

4) We have a DAG but I cannot see an Avamar DAG client in Avamar Administrator. Does there have to be one set up? We do our database backups separately on each database server in the cluster.

AP> DAG client is not mandatory but it's a convenient feature and needs to be configured separately using Cluster configuration tool, it is helpful if prefer to backup all the database from single account (DAG client), the benefit of DAG client is that no matter which server has the passive copies of the DB it will always backup from the passive node.

Regards

Amol Powar

3 Replies
Amol
3 Argentium

Re: Updating Avamar Exchange VSS and GLR plugins

Jump to solution

1) The manual refers to a "WriteCache" folder. Where is the default location for that? Is it the same as the avfscache folder Avamar uses for GLR?

AP > Yes, the default location is "C:\Program Files\avs\var\avfscache\"

2) Is it safe to run the Backup User Configuration Tool at any time? I don't want to make any changes before tomorrow, and this is a mission-critical Exchange cluster.

AP> Yes, once you run the tool it queries AD and check if user has all the required permission. If the user does not exist it gives and ability to create a user in AD

3) Is it safe to run the Cluster Configuration Tool at any time?

AP> Yes, this tools uses Windows API to check if the current system is a part of  a cluster, it also provides visual representation of all the nodes in the cluster and Avamar plugin configured on it.

4) We have a DAG but I cannot see an Avamar DAG client in Avamar Administrator. Does there have to be one set up? We do our database backups separately on each database server in the cluster.

AP> DAG client is not mandatory but it's a convenient feature and needs to be configured separately using Cluster configuration tool, it is helpful if prefer to backup all the database from single account (DAG client), the benefit of DAG client is that no matter which server has the passive copies of the DB it will always backup from the passive node.

Regards

Amol Powar

brastedd
3 Argentium

Re: Updating Avamar Exchange VSS and GLR plugins

Jump to solution

Amol,

Thanks for the reply. That's very helpful.

0 Kudos
varaprasaduv
1 Copper

Re: Updating Avamar Exchange VSS and GLR plugins

Jump to solution

Hi Amol,

Your reply is easily understandable.

I have an issue with my Exchange DAG client backup. In my setup, DAG is unable to detect all nodes in the cluster after exchagng DBs migrated from primary to secondary, hence not sending DAG backup sub work orders load to any other nodes and performing all backup jobs causing log truncation not to happen.

Current DAG backup log:

2016-08-04 20:00:24 avexvss Info <12963>: Adding 'XXXXXDB02' with IP 'XXXXXDB02' and subworkorder ID '100' to the remote clients list.

2016-08-04 20:00:24 avexvss Info <12964>: Number of remote clients: [1]

2016-08-04 20:00:24 avexvss Info <13807>: Forwarding [snapup] request to: XXXXXDB02 port:28002

2016-08-04 20:00:25 avexvss Info <12976>: Remote client: XXXXXDB02,XXXXXDB02, Status: SENT_SUBWORKORDER

2016-08-04 20:00:25 avexvss Info <13088>: Waiting for back-end clients to start sub-workorders ...

2016-08-04 20:01:01 avexvss Info <12961>: ...appending IP address xxxx::xxxx:xxxx:xxxx:xxxxx.

2016-08-04 20:01:01 avexvss Info <12961>: ...appending IP address xxxx::xxxx:xxxx:xxxx:xxxxx.

2016-08-04 20:01:01 avexvss Info <12961>: ...appending IP address xxxx::xxxx:xxxx:xxxx:xxxxx.


Previous DAG client log:  (When log truncation used to happen)

2016-07-21 20:00:41 avexvss Info <13085>: Adding database 'Oxxxxxx (C-D)' with remote target 'xxxxxxx03' to federated backup target list.

2016-07-21 20:00:42 avexvss Info <13085>: Adding database 'Oxxxxxx (K-L)' with remote target 'xxxxxxx03' to federated backup target list.

2016-07-21 20:00:42 avexvss Info <13085>: Adding database 'Oxxxxxx5 (LAW)' with remote target 'xxxxxxx02' to federated backup target list.

2016-07-21 20:00:43 avexvss Info <13085>: Adding database 'xxxxxx0 (S-T)' with remote target 'xxxxxxx01' to federated backup target list.

2016-07-21 20:00:43 avexvss Info <13085>: Adding database 'xxxxxx (A-B)' with remote target 'xxxxxxx03' to federated backup target list.

2016-07-21 20:00:44 avexvss Info <13085>: Adding database 'xxxxxx (I-J)' with remote target 'xxxxxxx03' to federated backup target list.

2016-07-21 20:00:45 avexvss Info <13085>: Adding database 'Oxxxxxx (E-F)' with remote target 'xxxxxxx03' to federated backup target list.

2016-07-21 20:00:45 avexvss Info <13085>: Adding database 'xxxxxx (W-X)' with remote target 'xxxxxxx02' to federated backup target list.

2016-07-21 20:00:46 avexvss Info <13085>: Adding database 'xxxxxx (U-V)' with remote target 'xxxxxxx02' to federated backup target list.

2016-07-21 20:00:47 avexvss Info <13085>: Adding database 'xxxxxx (Y-Z)' with remote target 'xxxxxxx02' to federated backup target list.

2016-07-21 20:00:47 avexvss Info <13085>: Adding database 'xxxxxx' with remote target 'xxxxxxx03' to federated backup target list.

2016-07-21 20:00:48 avexvss Info <13085>: Adding database 'xxxxxx (O-P)' with remote target 'xxxxxxx01' to federated backup target list.

2016-07-21 20:00:49 avexvss Info <13085>: Adding database 'xxxxxx (Q-R)' with remote target 'xxxxxxx01' to federated backup target list.

2016-07-21 20:00:49 avexvss Info <13085>: Adding database 'xxxxx (IREA)' with remote target 'xxxxxxx02' to federated backup target list.

2016-07-21 20:00:50 avexvss Info <13085>: Adding database 'xxxxx (Legal Hold)' with remote target 'xxxxxxx01' to federated backup target list.

2016-07-21 20:00:51 avexvss Info <13085>: Adding database 'xxxx (M-N)' with remote target 'xxxxxxx01' to federated backup target list.

2016-07-21 20:00:51 avexvss Info <13085>: Adding database 'xxxxx (G-H)' with remote target 'xxxxxxx03' to federated backup target list.

2016-07-21 20:00:52 avexvss Info <13085>: Adding database 'PilotDB' with remote target 'xxxxxxx02' to federated backup target list.

2016-07-21 20:00:52 avexvss Info <13087>: Creating the inter-agent manager for federated backup.

2016-07-21 20:00:53 avexvss Info <12962>: Master plugin runs on: '127.0.0.1'

2016-07-21 20:00:53 avexvss Info <12982>: Resolved host: 'xxxxxxx03' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:00:53 avexvss Info <12963>: Adding 'xxxxxxx03' with IP 'xx.xx.xx.xx' and subworkorder ID '100' to the remote clients list.

2016-07-21 20:00:54 avexvss Info <12982>: Resolved host: 'xxxxxxx03' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:00:54 avexvss Info <12982>: Resolved host: 'xxxxxxx02' to IP: 'xx.xx.xx.xx.xx.xx.xx'.

2016-07-21 20:00:55 avexvss Info <12963>: Adding 'xxxxxxx02' with IP 'xx.xx.xx.xx.xx.xx.xx' and subworkorder ID '200' to the remote clients list.

2016-07-21 20:00:56 avexvss Info <12982>: Resolved host: 'xxxxxxx01' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:00:56 avexvss Info <12963>: Adding 'xxxxxxx01' with IP 'xx.xx.xx.xx' and subworkorder ID '300' to the remote clients list.

2016-07-21 20:00:56 avexvss Info <12982>: Resolved host: 'xxxxxxx03' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:00:57 avexvss Info <12982>: Resolved host: 'xxxxxxx03' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:00:57 avexvss Info <12982>: Resolved host: 'xxxxxxx03' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:00:58 avexvss Info <12982>: Resolved host: 'xxxxxxx02' to IP: 'xx.xx.xx.xx.xx.xx.xx'.

2016-07-21 20:00:58 avexvss Info <12982>: Resolved host: 'xxxxxxx02' to IP: 'xx.xx.xx.xx.xx.xx.xx'.

2016-07-21 20:00:58 avexvss Info <12982>: Resolved host: 'xxxxxxx02' to IP: 'xx.xx.xx.xx.xx.xx.xx'.

2016-07-21 20:00:59 avexvss Info <12982>: Resolved host: 'xxxxxxx03' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:00:59 avexvss Info <12982>: Resolved host: 'xxxxxxx01' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:01:00 avexvss Info <12982>: Resolved host: 'xxxxxxx01' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:01:00 avexvss Info <12982>: Resolved host: 'xxxxxxx02' to IP: 'xx.xx.xx.xx.xx.xx.xx'.

2016-07-21 20:01:01 avexvss Info <12982>: Resolved host: 'xxxxxxx01' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:01:01 avexvss Info <12982>: Resolved host: 'xxxxxxx01' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:01:01 avexvss Info <12982>: Resolved host: 'xxxxxxx03' to IP: 'xx.xx.xx.xx'.

2016-07-21 20:01:02 avexvss Info <12982>: Resolved host: 'xxxxxxx02' to IP: 'xx.xx.xx.xx.xx.xx.xx'.

2016-07-21 20:01:02 avexvss Info <12964>: Number of remote clients: [3]

2016-07-21 20:01:03 avexvss Info <13807>: Forwarding [snapup] request to: xx.xx.xx.xx.xx.xx port:28002

2016-07-21 20:01:03 avexvss Info <12976>: Remote client: server02,xx.xx:xx:xx.xx.xx.xx.xx.xx, Status: SENT_SUBWORKORDER

2016-07-21 20:01:04 avexvss Info <13807>: Forwarding [snapup] request to: xx.xx.xx.xx port:28002

2016-07-21 20:01:05 avexvss Info <12976>: Remote client: server01,xx.xx.xx.xx.xx, Status: SENT_SUBWORKORDER

2016-07-21 20:01:06 avexvss Info <13807>: Forwarding [snapup] request to: xx.xx.xx.xx port:28002

2016-07-21 20:01:07 avexvss Info <12976>: Remote client: server03,xx.xx.xx.xx, Status: SENT_SUBWORKORDER


Any help ???


Varaprasad P.v.

0 Kudos